Compare commits

..

1 Commits

Author SHA1 Message Date
Hermes Pipeline a2433251cd Add Skill: conditional-request-routing-workflow
Extracted from: https://github.com/jwwelbor/AgentMap.git
Score: 1.0
2026-08-08 22:55:19 +00:00
9 changed files with 170 additions and 148 deletions
@@ -0,0 +1,81 @@
---
name: conditional-request-routing-workflow
version: 1.0.0
description: Collect a request, classify it via branching logic, and route to an approval
or rejection handler to produce a final result
inputs:
- name: request
type: string
description: The input text or request to be evaluated and routed
steps:
- node: Start
agent_type: input
description: Prompt user and capture the request into state field 'request'
next: Classify
- node: Classify
agent_type: branching
description: Evaluate the request and set 'decision' field, routing to Approve on
success or Reject on failure
input_fields:
- request
output_field: decision
next_node: Approve
on_failure: Reject
- node: Approve
agent_type: default
description: Format and output an approval message containing the request
input_fields:
- request
output_field: result
prompt: 'Request approved: {request}'
- node: Reject
agent_type: default
description: Format and output a rejection message containing the request
input_fields:
- request
output_field: result
prompt: 'Request rejected: {request}'
outputs:
- name: result
type: string
description: Final formatted message indicating the outcome (approved or rejected)
- name: decision
type: string
description: Routing decision produced by the branching node
tags: []
metadata:
source_repo: https://github.com/jwwelbor/AgentMap.git
extracted_at: ''
confidence: 0.92
---
# conditional-request-routing-workflow
Collect a request, classify it via branching logic, and route to an approval or rejection handler to produce a final result
## Steps
1. {'node': 'Start', 'agent_type': 'input', 'description': "Prompt user and capture the request into state field 'request'", 'next': 'Classify'}
2. {'node': 'Classify', 'agent_type': 'branching', 'description': "Evaluate the request and set 'decision' field, routing to Approve on success or Reject on failure", 'input_fields': ['request'], 'output_field': 'decision', 'next_node': 'Approve', 'on_failure': 'Reject'}
3. {'node': 'Approve', 'agent_type': 'default', 'description': 'Format and output an approval message containing the request', 'input_fields': ['request'], 'output_field': 'result', 'prompt': 'Request approved: {request}'}
4. {'node': 'Reject', 'agent_type': 'default', 'description': 'Format and output a rejection message containing the request', 'input_fields': ['request'], 'output_field': 'result', 'prompt': 'Request rejected: {request}'}
## Inputs
- {'name': 'request', 'type': 'string', 'description': 'The input text or request to be evaluated and routed'}
## Outputs
- {'name': 'result', 'type': 'string', 'description': 'Final formatted message indicating the outcome (approved or rejected)'}
- {'name': 'decision', 'type': 'string', 'description': 'Routing decision produced by the branching node'}
## Failure Modes
- Empty or missing request input prevents meaningful classification
- Branching node fails to resolve a valid route and defaults to rejection path
- Prompt template variable missing causes malformed output
## Source
Extracted from: [https://github.com/jwwelbor/AgentMap.git](https://github.com/jwwelbor/AgentMap.git)
Confidence: 0.92
@@ -0,0 +1,6 @@
# Commands: conditional-request-routing-workflow
## Available Commands
- `/skill conditional-request-routing-workflow` — Load this skill
- `/run conditional-request-routing-workflow` — Execute workflow
@@ -0,0 +1,10 @@
# Examples: conditional-request-routing-workflow
## Usage Example
```python
# How to use this skill
# Inputs: {'name': 'request', 'type': 'string', 'description': 'The input text or request to be evaluated and routed'}
# Process: {'node': 'Start', 'agent_type': 'input', 'description': "Prompt user and capture the request into state field 'request'", 'next': 'Classify'} → {'node': 'Classify', 'agent_type': 'branching', 'description': "Evaluate the request and set 'decision' field, routing to Approve on success or Reject on failure", 'input_fields': ['request'], 'output_field': 'decision', 'next_node': 'Approve', 'on_failure': 'Reject'} → {'node': 'Approve', 'agent_type': 'default', 'description': 'Format and output an approval message containing the request', 'input_fields': ['request'], 'output_field': 'result', 'prompt': 'Request approved: {request}'}
# Outputs: {'name': 'result', 'type': 'string', 'description': 'Final formatted message indicating the outcome (approved or rejected)'}, {'name': 'decision', 'type': 'string', 'description': 'Routing decision produced by the branching node'}
```
@@ -0,0 +1,72 @@
{
"name": "conditional-request-routing-workflow",
"version": "1.0.0",
"goal": "Collect a request, classify it via branching logic, and route to an approval or rejection handler to produce a final result",
"inputs": [
{
"name": "request",
"type": "string",
"description": "The input text or request to be evaluated and routed"
}
],
"steps": [
{
"node": "Start",
"agent_type": "input",
"description": "Prompt user and capture the request into state field 'request'",
"next": "Classify"
},
{
"node": "Classify",
"agent_type": "branching",
"description": "Evaluate the request and set 'decision' field, routing to Approve on success or Reject on failure",
"input_fields": [
"request"
],
"output_field": "decision",
"next_node": "Approve",
"on_failure": "Reject"
},
{
"node": "Approve",
"agent_type": "default",
"description": "Format and output an approval message containing the request",
"input_fields": [
"request"
],
"output_field": "result",
"prompt": "Request approved: {request}"
},
{
"node": "Reject",
"agent_type": "default",
"description": "Format and output a rejection message containing the request",
"input_fields": [
"request"
],
"output_field": "result",
"prompt": "Request rejected: {request}"
}
],
"outputs": [
{
"name": "result",
"type": "string",
"description": "Final formatted message indicating the outcome (approved or rejected)"
},
{
"name": "decision",
"type": "string",
"description": "Routing decision produced by the branching node"
}
],
"failure_modes": [
"Empty or missing request input prevents meaningful classification",
"Branching node fails to resolve a valid route and defaults to rejection path",
"Prompt template variable missing causes malformed output"
],
"confidence": 0.92,
"explanation": "Extracted from the ReviewFlow CSV example in the AgentMap README. This is a declarative, CSV-defined LangGraph workflow demonstrating the reusable pattern of input -> branching classification -> conditional handling paths. It can be generalized for ticket triage, content moderation, or any route-by-condition use case.",
"source_repo": "https://github.com/jwwelbor/AgentMap.git",
"score": 1.0
}
@@ -1,4 +1,4 @@
# Tests: graph-based-node-workflow
# Tests: conditional-request-routing-workflow
## Test Checklist
-100
View File
@@ -1,100 +0,0 @@
---
name: graph-based-node-workflow
version: 1.0.0
description: Create and execute typed node graphs for AI/robotics workflows by defining
nodes with inputs/outputs and connecting them with edges, then cooking the graph
to run the workflow.
inputs:
- bn.Graph() - the graph container for the workflow
- Node definitions (Literal, Text, LLMAgent, Concat, Output, etc.) with specified
inputs and outputs
- Edge connections mapping from_port to to_port between nodes
steps:
- 'Step 1: Initialize a bn.Graph() instance to serve as the workflow container'
- 'Step 2: Define individual nodes with their required inputs and outputs (e.g., Literal
for data, LLMAgent for inference, Concat for combining, Output for final results)'
- 'Step 3: Create edges connecting nodes by specifying source from_port and destination
to_port for each data flow'
- 'Step 4: Execute the graph by calling g.cook() to process the defined workflow and
produce results'
outputs:
- Executed workflow results stored in the graph's output nodes
- Cooked graph ready for inspection, replay, or deployment
- Potential error states if node dependencies are missing or ports don't match
tags: []
metadata:
source_repo: https://github.com/temiroff/Blacknode.git
extracted_at: ''
confidence: 0.95
---
# graph-based-node-workflow
Create and execute typed node graphs for AI/robotics workflows by defining nodes with inputs/outputs and connecting them with edges, then cooking the graph to run the workflow.
## Setup
**Dependencies:**
```text
pip install blacknode (core Python package) anthropic, openai, docker, petgraph (dependencies) Rust extensions in blacknode-core, blacknode-runtime (optional)
```
**Setup steps:**
1. Install blacknode with Python 3.11+ and required dependencies
1. Clone repository and navigate to project directory
1. Run examples/converted_text_pipeline.py to see basic graph execution
1. Modify node definitions and edges to create custom workflows
## Key Files
- `examples/converted_text_pipeline.py - basic pipeline pattern`
- `examples/hello_agent.py - LLM agent workflow pattern`
- `examples/research_pipeline.py - multi-node research workflow`
- `blacknode.py - main CLI entry point`
## Steps
1. Step 1: Initialize a bn.Graph() instance to serve as the workflow container
2. Step 2: Define individual nodes with their required inputs and outputs (e.g., Literal for data, LLMAgent for inference, Concat for combining, Output for final results)
3. Step 3: Create edges connecting nodes by specifying source from_port and destination to_port for each data flow
4. Step 4: Execute the graph by calling g.cook() to process the defined workflow and produce results
## Implementation Details
```python
g = bn.Graph()
```
```python
g._edges = [{"from": "model", "from_port": "value", "to": "agent", "to_port": "model"}]
```
```python
result = g.cook(output, "value")
```
## Inputs
- bn.Graph() - the graph container for the workflow
- Node definitions (Literal, Text, LLMAgent, Concat, Output, etc.) with specified inputs and outputs
- Edge connections mapping from_port to to_port between nodes
## Outputs
- Executed workflow results stored in the graph's output nodes
- Cooked graph ready for inspection, replay, or deployment
- Potential error states if node dependencies are missing or ports don't match
## Failure Modes
- Missing node dependencies causing undefined variable errors
- Port mismatch in edge connections leading to no data flow
- Incomplete graph definition causing cook() to fail
- Model API key missing or invalid for LLMAgent nodes
## Source
Extracted from: [https://github.com/temiroff/Blacknode.git](https://github.com/temiroff/Blacknode.git)
Confidence: 0.95
@@ -1,6 +0,0 @@
# Commands: graph-based-node-workflow
## Available Commands
- `/skill graph-based-node-workflow` — Load this skill
- `/run graph-based-node-workflow` — Execute workflow
@@ -1,10 +0,0 @@
# Examples: graph-based-node-workflow
## Usage Example
```python
# How to use this skill
# Inputs: bn.Graph() - the graph container for the workflow, Node definitions (Literal, Text, LLMAgent, Concat, Output, etc.) with specified inputs and outputs, Edge connections mapping from_port to to_port between nodes
# Process: Step 1: Initialize a bn.Graph() instance to serve as the workflow container → Step 2: Define individual nodes with their required inputs and outputs (e.g., Literal for data, LLMAgent for inference, Concat for combining, Output for final results) → Step 3: Create edges connecting nodes by specifying source from_port and destination to_port for each data flow
# Outputs: Executed workflow results stored in the graph's output nodes, Cooked graph ready for inspection, replay, or deployment, Potential error states if node dependencies are missing or ports don't match
```
@@ -1,31 +0,0 @@
{
"name": "graph-based-node-workflow",
"version": "1.0.0",
"goal": "Create and execute typed node graphs for AI/robotics workflows by defining nodes with inputs/outputs and connecting them with edges, then cooking the graph to run the workflow.",
"inputs": [
"bn.Graph() - the graph container for the workflow",
"Node definitions (Literal, Text, LLMAgent, Concat, Output, etc.) with specified inputs and outputs",
"Edge connections mapping from_port to to_port between nodes"
],
"steps": [
"Step 1: Initialize a bn.Graph() instance to serve as the workflow container",
"Step 2: Define individual nodes with their required inputs and outputs (e.g., Literal for data, LLMAgent for inference, Concat for combining, Output for final results)",
"Step 3: Create edges connecting nodes by specifying source from_port and destination to_port for each data flow",
"Step 4: Execute the graph by calling g.cook() to process the defined workflow and produce results"
],
"outputs": [
"Executed workflow results stored in the graph's output nodes",
"Cooked graph ready for inspection, replay, or deployment",
"Potential error states if node dependencies are missing or ports don't match"
],
"failure_modes": [
"Missing node dependencies causing undefined variable errors",
"Port mismatch in edge connections leading to no data flow",
"Incomplete graph definition causing cook() to fail",
"Model API key missing or invalid for LLMAgent nodes"
],
"confidence": 0.95,
"explanation": "This workflow pattern is reusable across different AI/robotics applications because it provides a standardized way to compose complex pipelines from typed nodes. The pattern can be adapted to various use cases like research pipelines, agent workflows, or robotics control graphs by simply adding/removing nodes and edges while maintaining the same graph-cooking execution model.",
"source_repo": "https://github.com/temiroff/Blacknode.git",
"score": 1.0
}