Orchestrates multi-step workflows where output from one agent feeds into the next.
Install
mkdir -p .claude/skills/stream-chain && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/1995" && unzip -o skill.zip -d .claude/skills/stream-chain && rm skill.zipInstalls to .claude/skills/stream-chain
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflowsKey capabilities
- →Execute custom prompt sequences
- →Run predefined development pipelines
- →Chain multi-agent outputs
- →Configure custom pipeline definitions
How it works
Each step in the chain receives the complete output from the previous step, allowing data to flow sequentially through multiple agents.
Inputs & outputs
When to use stream-chain
- →Building multi-step AI workflows
- →Chaining data transformation agents
- →Automating sequential task pipelines
About this skill
Stream-Chain Skill
Execute sophisticated multi-step workflows where each agent's output flows into the next, enabling complex data transformations and sequential processing pipelines.
Overview
Stream-Chain provides two powerful modes for orchestrating multi-agent workflows:
- Custom Chains (
run): Execute custom prompt sequences with full control - Predefined Pipelines (
pipeline): Use battle-tested workflows for common tasks
Each step in a chain receives the complete output from the previous step, enabling sophisticated multi-agent coordination through streaming data flow.
Quick Start
Run a Custom Chain
claude-flow stream-chain run \
"Analyze codebase structure" \
"Identify improvement areas" \
"Generate action plan"
Execute a Pipeline
claude-flow stream-chain pipeline analysis
Custom Chains (run)
Execute custom stream chains with your own prompts for maximum flexibility.
Syntax
claude-flow stream-chain run <prompt1> <prompt2> [...] [options]
Requirements:
- Minimum 2 prompts required
- Each prompt becomes a step in the chain
- Output flows sequentially through all steps
Options
| Option | Description | Default |
|---|---|---|
--verbose | Show detailed execution information | false |
--timeout <seconds> | Timeout per step | 30 |
--debug | Enable debug mode with full logging | false |
How Context Flows
Each step receives the previous output as context:
Step 1: "Write a sorting function"
Output: [function implementation]
Step 2 receives:
"Previous step output:
[function implementation]
Next task: Add comprehensive tests"
Step 3 receives:
"Previous steps output:
[function + tests]
Next task: Optimize performance"
Examples
Basic Development Chain
claude-flow stream-chain run \
"Write a user authentication function" \
"Add input validation and error handling" \
"Create unit tests with edge cases"
Security Audit Workflow
claude-flow stream-chain run \
"Analyze authentication system for vulnerabilities" \
"Identify and categorize security issues by severity" \
"Propose fixes with implementation priority" \
"Generate security test cases" \
--timeout 45 \
--verbose
Code Refactoring Chain
claude-flow stream-chain run \
"Identify code smells in src/ directory" \
"Create refactoring plan with specific changes" \
"Apply refactoring to top 3 priority items" \
"Verify refactored code maintains behavior" \
--debug
Data Processing Pipeline
claude-flow stream-chain run \
"Extract data from API responses" \
"Transform data into normalized format" \
"Validate data against schema" \
"Generate data quality report"
Predefined Pipelines (pipeline)
Execute battle-tested workflows optimized for common development tasks.
Syntax
claude-flow stream-chain pipeline <type> [options]
Available Pipelines
1. Analysis Pipeline
Comprehensive codebase analysis and improvement identification.
claude-flow stream-chain pipeline analysis
Workflow Steps:
- Structure Analysis: Map directory structure and identify components
- Issue Detection: Find potential improvements and problems
- Recommendations: Generate actionable improvement report
Use Cases:
- New codebase onboarding
- Technical debt assessment
- Architecture review
- Code quality audits
2. Refactor Pipeline
Systematic code refactoring with prioritization.
claude-flow stream-chain pipeline refactor
Workflow Steps:
- Candidate Identification: Find code needing refactoring
- Prioritization: Create ranked refactoring plan
- Implementation: Provide refactored code for top priorities
Use Cases:
- Technical debt reduction
- Code quality improvement
- Legacy code modernization
- Design pattern implementation
3. Test Pipeline
Comprehensive test generation with coverage analysis.
claude-flow stream-chain pipeline test
Workflow Steps:
- Coverage Analysis: Identify areas lacking tests
- Test Design: Create test cases for critical functions
- Implementation: Generate unit tests with assertions
Use Cases:
- Increasing test coverage
- TDD workflow support
- Regression test creation
- Quality assurance
4. Optimize Pipeline
Performance optimization with profiling and implementation.
claude-flow stream-chain pipeline optimize
Workflow Steps:
- Profiling: Identify performance bottlenecks
- Strategy: Analyze and suggest optimization approaches
- Implementation: Provide optimized code
Use Cases:
- Performance improvement
- Resource optimization
- Scalability enhancement
- Latency reduction
Pipeline Options
| Option | Description | Default |
|---|---|---|
--verbose | Show detailed execution | false |
--timeout <seconds> | Timeout per step | 30 |
--debug | Enable debug mode | false |
Pipeline Examples
Quick Analysis
claude-flow stream-chain pipeline analysis
Extended Refactoring
claude-flow stream-chain pipeline refactor --timeout 60 --verbose
Debug Test Generation
claude-flow stream-chain pipeline test --debug
Comprehensive Optimization
claude-flow stream-chain pipeline optimize --timeout 90 --verbose
Pipeline Output
Each pipeline execution provides:
- Progress: Step-by-step execution status
- Results: Success$failure per step
- Timing: Total and per-step execution time
- Summary: Consolidated results and recommendations
Custom Pipeline Definitions
Define reusable pipelines in .claude-flow$config.json:
Configuration Format
{
"streamChain": {
"pipelines": {
"security": {
"name": "Security Audit Pipeline",
"description": "Comprehensive security analysis",
"prompts": [
"Scan codebase for security vulnerabilities",
"Categorize issues by severity (critical$high$medium$low)",
"Generate fixes with priority and implementation steps",
"Create security test suite"
],
"timeout": 45
},
"documentation": {
"name": "Documentation Generation Pipeline",
"prompts": [
"Analyze code structure and identify undocumented areas",
"Generate API documentation with examples",
"Create usage guides and tutorials",
"Build architecture diagrams and flow charts"
]
}
}
}
}
Execute Custom Pipeline
claude-flow stream-chain pipeline security
claude-flow stream-chain pipeline documentation
Advanced Use Cases
Multi-Agent Coordination
Chain different agent types for complex workflows:
claude-flow stream-chain run \
"Research best practices for API design" \
"Design REST API with discovered patterns" \
"Implement API endpoints with validation" \
"Generate OpenAPI specification" \
"Create integration tests" \
"Write deployment documentation"
Data Transformation Pipeline
Process and transform data through multiple stages:
claude-flow stream-chain run \
"Extract user data from CSV files" \
"Normalize and validate data format" \
"Enrich data with external API calls" \
"Generate analytics report" \
"Create visualization code"
Code Migration Workflow
Systematic code migration with validation:
claude-flow stream-chain run \
"Analyze legacy codebase dependencies" \
"Create migration plan with risk assessment" \
"Generate modernized code for high-priority modules" \
"Create migration tests" \
"Document migration steps and rollback procedures"
Quality Assurance Chain
Comprehensive code quality workflow:
claude-flow stream-chain pipeline analysis
claude-flow stream-chain pipeline refactor
claude-flow stream-chain pipeline test
claude-flow stream-chain pipeline optimize
Best Practices
1. Clear and Specific Prompts
Good:
"Analyze authentication.js for SQL injection vulnerabilities"
Avoid:
"Check security"
2. Logical Progression
Order prompts to build on previous outputs:
1. "Identify the problem"
2. "Analyze root causes"
3. "Design solution"
4. "Implement solution"
5. "Verify implementation"
3. Appropriate Timeouts
- Simple tasks: 30 seconds (default)
- Analysis tasks: 45-60 seconds
- Implementation tasks: 60-90 seconds
- Complex workflows: 90-120 seconds
4. Verification Steps
Include validation in your chains:
claude-flow stream-chain run \
"Implement feature X" \
"Write tests for feature X" \
"Verify tests pass and cover edge cases"
5. Iterative Refinement
Use chains for iterative improvement:
claude-flow stream-chain run \
"Generate initial implementation" \
"Review and identify issues" \
"Refine based on issues found" \
"Final quality check"
Integration with Claude Flow
Combine with Swarm Coordination
# Initialize swarm for coordination
claude-flow swarm init --topology mesh
# Execute stream chain with swarm agents
claude-flow stream-chain run \
"Agent 1: Research task" \
"Agent 2: Implement solution" \
"Agent 3: Test implementation" \
"Agent 4: Review and refine"
Memory Integration
Stream chains automatically store context in memory for cross-session persistence:
# Execute chain with memory
claude-flow stream-chain run \
"Analyze requirements" \
"Design architecture" \
--verbose
# Results stored in .claude-flow$memory$stream-chain/
Neural Pattern Training
Successful chains train neural patterns for improved performance:
# Enable neural training
claude-flow stream-chain pipel
---
*Content truncated.*
When not to use it
- →Single-step tasks not requiring sequential context
Prerequisites
Limitations
- →Maximum 100K tokens per step
- →Throughput varies by task complexity
How it compares
It automates multi-agent coordination by managing context flow between steps, whereas manual approaches require individual prompt handling.
Compared to similar skills
stream-chain side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| stream-chain (this skill) | 2 | 6mo | Review | Intermediate |
| opencode-cli | 14 | 7mo | Review | Advanced |
| claude-automation-recommender | 47 | 2mo | Review | Beginner |
| mcp-integration | 21 | 9mo | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by ruvnet
View all by ruvnet →You might also like
opencode-cli
SpillwaveSolutions
This skill should be used when configuring or using the OpenCode CLI for headless LLM automation. Use when the user asks to "configure opencode", "use opencode cli", "set up opencode", "opencode run command", "opencode model selection", "opencode providers", "opencode vertex ai", "opencode mcp servers", "opencode ollama", "opencode local models", "opencode deepseek", "opencode kimi", "opencode mistral", "fallback cli tool", or "headless llm cli". Covers command syntax, provider configuration, Vertex AI setup, MCP servers, local models, cloud providers, and subprocess integration patterns.
claude-automation-recommender
anthropics
Analyze a codebase and recommend Claude Code automations (hooks, subagents, skills, plugins, MCP servers). Use when user asks for automation recommendations, wants to optimize their Claude Code setup, mentions improving Claude Code workflows, asks how to first set up Claude Code for a project, or wants to know what Claude Code features they should use.
mcp-integration
anthropics
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Context Protocol", "connect external service", mentions "${CLAUDE_PLUGIN_ROOT} with MCP", or discusses MCP server types (SSE, stdio, HTTP, WebSocket). Provides comprehensive guidance for integrating Model Context Protocol servers into Claude Code plugins for external tool and service integration.
hook-development
anthropics
This skill should be used when the user asks to "create a hook", "add a PreToolUse/PostToolUse/Stop hook", "validate tool use", "implement prompt-based hooks", "use ${CLAUDE_PLUGIN_ROOT}", "set up event-driven automation", "block dangerous commands", or mentions hook events (PreToolUse, PostToolUse, Stop, SubagentStop, SessionStart, SessionEnd, UserPromptSubmit, PreCompact, Notification). Provides comprehensive guidance for creating and implementing Claude Code plugin hooks with focus on advanced prompt-based hooks API.
agent-factory
alirezarezvani
Claude Code agent generation system that creates custom agents and sub-agents with enhanced YAML frontmatter, tool access patterns, and MCP integration support following proven production patterns
swarm-advanced
ruvnet
Advanced swarm orchestration patterns for research, development, testing, and complex distributed workflows