Compare commits

..

1 Commits

Author SHA1 Message Date
Hermes Pipeline 3bea1c3d2b Add Skill: branching-agent-pattern
Extracted from: https://github.com/jwwelbor/AgentMap.git
Score: 1.0
2026-08-06 14:38:54 +00:00
9 changed files with 149 additions and 97 deletions
+101
View File
@@ -0,0 +1,101 @@
---
name: branching-agent-pattern
version: 1.0.0
description: Define and execute AI agent workflows using CSV-based declarative definitions
with configurable branching logic
inputs:
- 'CSV workflow files defining agent graphs with columns: graph_name, node_name, agent_type,
next_node, on_failure, prompt, input_fields, output_field'
- LLM provider configuration (OpenAI, Anthropic, Google) in agentmap_config.yaml
- Storage backend configuration in agentmap_config_storage.yaml
steps:
- Define workflow graph in CSV with nodes representing agent steps and their connections
(next_node, on_failure)
- Configure BranchingAgent with customizable success/failure values and fallback fields
in the context dictionary
- Initialize the agent runtime with ensure_initialized() and configure execution tracking
and state adapter services
- Execute the workflow using agentmap run with appropriate inputs and monitor the
execution trace
outputs:
- Executed workflow with results stored in the specified output_field
- Detailed execution trace showing success/failure decisions at each branching point
- Updated workflow state persisted in the configured storage backend
tags: []
metadata:
source_repo: https://github.com/jwwelbor/AgentMap.git
extracted_at: ''
confidence: 0.95
---
# branching-agent-pattern
Define and execute AI agent workflows using CSV-based declarative definitions with configurable branching logic
## Setup
**Dependencies:**
```text
pip install langgraph>=1.0.0 langchain-core>=0.3.0 pyyaml>=6.0.0 fastapi>=0.111.0 uvicorn>=0.34.3
```
**Setup steps:**
1. Install AgentMap: pip install agentmap[all]
1. Configure llm providers in agentmap_config.yaml (OpenAI, Anthropic, Google models)
1. Create CSV workflow files with graph definitions
1. Initialize runtime with ensure_initialized()
1. Run workflow with agentmap run <csv_file> --pretty
## Key Files
- `agentmap_config.yaml - Main configuration with LLM and storage settings`
- `agentmap_config_storage.yaml - Storage backend configuration`
- `hello_world.csv - Sample workflow demonstrating basic agent chain`
- `examples/host_integration/custom_agents.py - Custom agent implementations with host service integration`
## Steps
1. Define workflow graph in CSV with nodes representing agent steps and their connections (next_node, on_failure)
2. Configure BranchingAgent with customizable success/failure values and fallback fields in the context dictionary
3. Initialize the agent runtime with ensure_initialized() and configure execution tracking and state adapter services
4. Execute the workflow using agentmap run with appropriate inputs and monitor the execution trace
## Implementation Details
```python
CSV format: graph_name,node_name,agent_type,next_node,on_failure,prompt,input_fields,output_field
```
```python
BranchingAgent context example: {'input_fields': ['success'], 'output_field': 'result', 'success_values': ['PASSED', 'COMPLETED']}
```
```python
Execution command: agentmap run hello_world.csv --pretty
```
## Inputs
- CSV workflow files defining agent graphs with columns: graph_name, node_name, agent_type, next_node, on_failure, prompt, input_fields, output_field
- LLM provider configuration (OpenAI, Anthropic, Google) in agentmap_config.yaml
- Storage backend configuration in agentmap_config_storage.yaml
## Outputs
- Executed workflow with results stored in the specified output_field
- Detailed execution trace showing success/failure decisions at each branching point
- Updated workflow state persisted in the configured storage backend
## Failure Modes
- Invalid CSV format causing parsing errors during workflow loading
- Missing or misconfigured LLM provider settings leading to execution failures
- Storage backend unavailable or misconfigured preventing workflow persistence
- Agent execution timeout due to long-running operations or infinite loops
## Source
Extracted from: [https://github.com/jwwelbor/AgentMap.git](https://github.com/jwwelbor/AgentMap.git)
Confidence: 0.95
@@ -0,0 +1,6 @@
# Commands: branching-agent-pattern
## Available Commands
- `/skill branching-agent-pattern` — Load this skill
- `/run branching-agent-pattern` — Execute workflow
@@ -0,0 +1,10 @@
# Examples: branching-agent-pattern
## Usage Example
```python
# How to use this skill
# Inputs: CSV workflow files defining agent graphs with columns: graph_name, node_name, agent_type, next_node, on_failure, prompt, input_fields, output_field, LLM provider configuration (OpenAI, Anthropic, Google) in agentmap_config.yaml, Storage backend configuration in agentmap_config_storage.yaml
# Process: Define workflow graph in CSV with nodes representing agent steps and their connections (next_node, on_failure) → Configure BranchingAgent with customizable success/failure values and fallback fields in the context dictionary → Initialize the agent runtime with ensure_initialized() and configure execution tracking and state adapter services
# Outputs: Executed workflow with results stored in the specified output_field, Detailed execution trace showing success/failure decisions at each branching point, Updated workflow state persisted in the configured storage backend
```
@@ -0,0 +1,31 @@
{
"name": "branching-agent-pattern",
"version": "1.0.0",
"goal": "Define and execute AI agent workflows using CSV-based declarative definitions with configurable branching logic",
"inputs": [
"CSV workflow files defining agent graphs with columns: graph_name, node_name, agent_type, next_node, on_failure, prompt, input_fields, output_field",
"LLM provider configuration (OpenAI, Anthropic, Google) in agentmap_config.yaml",
"Storage backend configuration in agentmap_config_storage.yaml"
],
"steps": [
"Define workflow graph in CSV with nodes representing agent steps and their connections (next_node, on_failure)",
"Configure BranchingAgent with customizable success/failure values and fallback fields in the context dictionary",
"Initialize the agent runtime with ensure_initialized() and configure execution tracking and state adapter services",
"Execute the workflow using agentmap run with appropriate inputs and monitor the execution trace"
],
"outputs": [
"Executed workflow with results stored in the specified output_field",
"Detailed execution trace showing success/failure decisions at each branching point",
"Updated workflow state persisted in the configured storage backend"
],
"failure_modes": [
"Invalid CSV format causing parsing errors during workflow loading",
"Missing or misconfigured LLM provider settings leading to execution failures",
"Storage backend unavailable or misconfigured preventing workflow persistence",
"Agent execution timeout due to long-running operations or infinite loops"
],
"confidence": 0.95,
"explanation": "The BranchingAgent pattern provides a reusable framework for creating conditional AI workflows. The CSV-based workflow definition allows defining complex agent graphs declaratively, while the BranchingAgent handles dynamic branching based on success/failure conditions with customizable value sets. This pattern can be adapted to various use cases including task routing, error handling, and conditional execution paths across different domains.",
"source_repo": "https://github.com/jwwelbor/AgentMap.git",
"score": 1.0
}
@@ -1,4 +1,4 @@
# Tests: conditional-request-routing # Tests: branching-agent-pattern
## Test Checklist ## Test Checklist
@@ -1,54 +0,0 @@
---
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
@@ -1,6 +0,0 @@
# Commands: conditional-request-routing
## Available Commands
- `/skill conditional-request-routing` — Load this skill
- `/run conditional-request-routing` — Execute workflow
@@ -1,10 +0,0 @@
# 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
```
@@ -1,26 +0,0 @@
{
"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
}