Compare commits

..

1 Commits

Author SHA1 Message Date
Hermes Pipeline 362bf8d810 Add Skill: conditional-request-routing
Extracted from: https://github.com/jwwelbor/AgentMap.git
Score: 1.0
2026-08-08 23:05:54 +00:00
9 changed files with 97 additions and 99 deletions
@@ -0,0 +1,54 @@
---
name: conditional-request-routing
version: 1.0.0
description: Classify an input request and route it to either an approval or rejection
path, producing a corresponding result
inputs:
- 'request: the input request or content to be reviewed and routed'
steps:
- 'Collect input: Use an input agent to capture the user''s request into state field
''request'''
- 'Branch: Use a branching agent to evaluate ''request'' and route to ''Approve''
node on success or ''Reject'' node on failure'
- 'Approve path: Use a default agent to format and output an approval message with
the request'
- 'Reject path: Use a default agent to format and output a rejection message with
the request'
outputs:
- 'result: the approval or rejection message containing the original request'
tags: []
metadata:
source_repo: https://github.com/jwwelbor/AgentMap.git
extracted_at: ''
confidence: 0.85
---
# conditional-request-routing
Classify an input request and route it to either an approval or rejection path, producing a corresponding result
## Steps
1. Collect input: Use an input agent to capture the user's request into state field 'request'
2. Branch: Use a branching agent to evaluate 'request' and route to 'Approve' node on success or 'Reject' node on failure
3. Approve path: Use a default agent to format and output an approval message with the request
4. Reject path: Use a default agent to format and output a rejection message with the request
## Inputs
- request: the input request or content to be reviewed and routed
## Outputs
- result: the approval or rejection message containing the original request
## Failure Modes
- Branching agent cannot evaluate request and neither path is taken
- Missing or empty input request
- Prompt misconfiguration causing incorrect routing
## Source
Extracted from: [https://github.com/jwwelbor/AgentMap.git](https://github.com/jwwelbor/AgentMap.git)
Confidence: 0.85
@@ -0,0 +1,6 @@
# Commands: conditional-request-routing
## Available Commands
- `/skill conditional-request-routing` — Load this skill
- `/run conditional-request-routing` — Execute workflow
@@ -0,0 +1,10 @@
# Examples: conditional-request-routing
## Usage Example
```python
# How to use this skill
# Inputs: request: the input request or content to be reviewed and routed
# Process: Collect input: Use an input agent to capture the user's request into state field 'request' → Branch: Use a branching agent to evaluate 'request' and route to 'Approve' node on success or 'Reject' node on failure → Approve path: Use a default agent to format and output an approval message with the request
# Outputs: result: the approval or rejection message containing the original request
```
@@ -0,0 +1,26 @@
{
"name": "conditional-request-routing",
"version": "1.0.0",
"goal": "Classify an input request and route it to either an approval or rejection path, producing a corresponding result",
"inputs": [
"request: the input request or content to be reviewed and routed"
],
"steps": [
"Collect input: Use an input agent to capture the user's request into state field 'request'",
"Branch: Use a branching agent to evaluate 'request' and route to 'Approve' node on success or 'Reject' node on failure",
"Approve path: Use a default agent to format and output an approval message with the request",
"Reject path: Use a default agent to format and output a rejection message with the request"
],
"outputs": [
"result: the approval or rejection message containing the original request"
],
"failure_modes": [
"Branching agent cannot evaluate request and neither path is taken",
"Missing or empty input request",
"Prompt misconfiguration causing incorrect routing"
],
"confidence": 0.85,
"explanation": "Extracted from AgentMap's README example 'ReviewFlow' CSV workflow. This is a declarative LangGraph pattern using AgentMap's CSV format that implements conditional branching - a universally reusable pattern for request triage, content moderation, approval gates, or any two-path decision flow. It can be adapted by changing agent types (e.g., using LLM agents instead of default) and prompts.",
"source_repo": "https://github.com/jwwelbor/AgentMap.git",
"score": 1.0
}
@@ -1,4 +1,4 @@
# Tests: conditional-review-workflow
# Tests: conditional-request-routing
## Test Checklist
@@ -1,56 +0,0 @@
---
name: conditional-review-workflow
version: 1.0.0
description: Process a user request through branching logic to approve or reject it,
producing a routed decision result
inputs:
- 'request: string - The user''s request or input collected at runtime via the input
agent'
steps:
- 'Start: Input agent collects the user request and stores it in the ''request'' state
field, then routes to Classify node'
- 'Classify: Branching agent evaluates the ''request'' field and routes to Approve
node on success or Reject node on failure (on_failure)'
- 'Approve: Default agent formats an approval message using the request and stores
it in the ''result'' output field'
- 'Reject: Default agent formats a rejection message using the request and stores
it in the ''result'' output field'
outputs:
- 'result: string - Final message indicating whether the request was approved or rejected,
containing the original request'
tags: []
metadata:
source_repo: https://github.com/jwwelbor/AgentMap.git
extracted_at: ''
confidence: 0.85
---
# conditional-review-workflow
Process a user request through branching logic to approve or reject it, producing a routed decision result
## Steps
1. Start: Input agent collects the user request and stores it in the 'request' state field, then routes to Classify node
2. Classify: Branching agent evaluates the 'request' field and routes to Approve node on success or Reject node on failure (on_failure)
3. Approve: Default agent formats an approval message using the request and stores it in the 'result' output field
4. Reject: Default agent formats a rejection message using the request and stores it in the 'result' output field
## Inputs
- request: string - The user's request or input collected at runtime via the input agent
## Outputs
- result: string - Final message indicating whether the request was approved or rejected, containing the original request
## Failure Modes
- Input collection failure - user provides no or invalid input (no explicit on_failure defined for Start node in example)
- Branching classification failure - if branching agent cannot evaluate, it routes to Reject via on_failure configuration
- LLM provider unavailability - if branching or agents rely on LLM backends that are misconfigured or offline
## Source
Extracted from: [https://github.com/jwwelbor/AgentMap.git](https://github.com/jwwelbor/AgentMap.git)
Confidence: 0.85
@@ -1,6 +0,0 @@
# Commands: conditional-review-workflow
## Available Commands
- `/skill conditional-review-workflow` — Load this skill
- `/run conditional-review-workflow` — Execute workflow
@@ -1,10 +0,0 @@
# Examples: conditional-review-workflow
## Usage Example
```python
# How to use this skill
# Inputs: request: string - The user's request or input collected at runtime via the input agent
# Process: Start: Input agent collects the user request and stores it in the 'request' state field, then routes to Classify node → Classify: Branching agent evaluates the 'request' field and routes to Approve node on success or Reject node on failure (on_failure) → Approve: Default agent formats an approval message using the request and stores it in the 'result' output field
# Outputs: result: string - Final message indicating whether the request was approved or rejected, containing the original request
```
@@ -1,26 +0,0 @@
{
"name": "conditional-review-workflow",
"version": "1.0.0",
"goal": "Process a user request through branching logic to approve or reject it, producing a routed decision result",
"inputs": [
"request: string - The user's request or input collected at runtime via the input agent"
],
"steps": [
"Start: Input agent collects the user request and stores it in the 'request' state field, then routes to Classify node",
"Classify: Branching agent evaluates the 'request' field and routes to Approve node on success or Reject node on failure (on_failure)",
"Approve: Default agent formats an approval message using the request and stores it in the 'result' output field",
"Reject: Default agent formats a rejection message using the request and stores it in the 'result' output field"
],
"outputs": [
"result: string - Final message indicating whether the request was approved or rejected, containing the original request"
],
"failure_modes": [
"Input collection failure - user provides no or invalid input (no explicit on_failure defined for Start node in example)",
"Branching classification failure - if branching agent cannot evaluate, it routes to Reject via on_failure configuration",
"LLM provider unavailability - if branching or agents rely on LLM backends that are misconfigured or offline"
],
"confidence": 0.85,
"explanation": "Extracted from AgentMap's documented CSV workflow example (ReviewFlow). This is a reusable conditional routing pattern that can be adapted for any approval/rejection, triage, or binary-decision scenario by modifying the branching prompt and agent types. The CSV-based declarative format makes it portable across the AgentMap framework.",
"source_repo": "https://github.com/jwwelbor/AgentMap.git",
"score": 1.0
}