Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
borghei avatar

Agenthub

  • 68 installs
  • 451 repo stars
  • Updated July 21, 2026
  • borghei/claude-skills

agenthub is a Claude skill that orchestrates multiple AI agents as a directed acyclic graph with dependency management and output merging.

About

agenthub is a Claude skill for orchestrating multiple AI agents as a directed acyclic graph. A developer uses it to decompose a complex task into sub-tasks, assign each to a specialized agent, define dependencies between them, and merge their outputs. It ships seven sub-skills (init, run, spawn, board, eval, merge, status) plus Python scripts for DAG analysis, board management, and result ranking.

  • Orchestrates multiple AI agents as a directed acyclic graph (DAG) with typed dependencies
  • Compound sub-skill architecture: init, run, spawn, board, eval, merge, status
  • DAG analyzer validates for cycles, unreachable nodes, and bottlenecks

Agenthub by the numbers

  • 68 all-time installs (skills.sh)
  • Ranked #5,858 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

agenthub capabilities & compatibility

Free; local Python scripts, no API keys stated.

Capabilities
agent workflow designer · agent protocol · dag analyzer
Use cases
orchestration · planning
Pricing
Free
From the docs

What agenthub says it does

Multi-agent DAG orchestration framework. Design, execute, and manage workflows
SKILL.md
AgentHub provides patterns and tools for orchestrating multiple AI agents as a directed acyclic graph (DAG).
SKILL.md
complex tasks decompose better than they scale
SKILL.md
npx skills add https://github.com/borghei/claude-skills --skill agenthub

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs68
repo stars451
Last updatedJuly 21, 2026
Repositoryborghei/claude-skills

What it does

Design and run multi-agent DAG workflows where specialized agents collaborate on sub-tasks and their outputs are merged.

Who is it for?

Developers building multi-agent systems that need parallel specialized agents with defined dependencies and a merge step.

Skip if: Simple single-agent tasks that fit in one context window.

When should I use this skill?

When a task requires multiple specialized agents working in concert, or when you need to parallelize AI work across sub-tasks.

What you get

A validated DAG of specialized agents that run in parallel where possible and merge into a coherent result.

  • validated workflow DAG
  • agent status board
  • merged final result

By the numbers

  • 7 sub-skills in skills/ directory
  • 4 Python scripts (dag_analyzer, board_manager, result_ranker, session_manager)
  • 7 agent states (PENDING, READY, RUNNING, COMPLETED, FAILED, SKIPPED, EVALUATING)

Files

SKILL.mdMarkdownGitHub ↗

AgentHub - Multi-Agent DAG Orchestration

Category: Engineering / AI Agents Maintainer: Claude Skills Team

Overview

AgentHub provides patterns and tools for orchestrating multiple AI agents as a directed acyclic graph (DAG). Instead of one agent doing everything sequentially, AgentHub lets you decompose complex tasks into sub-tasks, assign each to a specialized agent, define dependencies between them, and merge their outputs into a coherent result.

The core insight: complex tasks decompose better than they scale. A 10-step sequential task run by one agent hits context limits and quality degradation. Five parallel agents with clear scopes and a merge step produce better results faster.

Sub-Skills

This skill uses compound sub-skill architecture. Each sub-skill in skills/ handles a stage of the orchestration lifecycle:

Sub-SkillFilePurpose
Initskills/init.mdInitialize a multi-agent workflow definition
Runskills/run.mdExecute a defined workflow end-to-end
Spawnskills/spawn.mdSpawn individual agents within a workflow
Boardskills/board.mdDashboard showing agent status and progress
Evalskills/eval.mdEvaluate agent outputs for quality and consistency
Mergeskills/merge.mdMerge outputs from multiple agents into final result
Statusskills/status.mdShow workflow execution status and health

Sub-Skill Flow

Init ──> Run ──> Spawn (parallel) ──> Eval ──> Merge
                      │                            │
                    Board ◄──── Status ◄───────────┘

Lifecycle: Init defines the workflow DAG, Run orchestrates execution, Spawn creates individual agents, Board provides real-time visibility, Eval checks output quality, Merge combines results, and Status reports overall health.

Scripts

ScriptPurpose
scripts/dag_analyzer.pyAnalyze DAG definitions for cycles, unreachable nodes, and bottlenecks
scripts/board_manager.pyManage agent task boards with status tracking
scripts/result_ranker.pyRank and merge outputs from multiple agents
scripts/session_manager.pyManage orchestration sessions and state

Core Concepts

Workflow DAG

A workflow is a directed acyclic graph where:

  • Nodes are agent tasks with a defined scope, inputs, and expected outputs
  • Edges are dependencies: agent B cannot start until agent A completes
  • Root nodes have no dependencies and start immediately
  • Terminal nodes have no dependents and feed into the merge step
┌──────────┐     ┌──────────┐     ┌──────────┐
│ Research  │────>│ Analysis │────>│  Merge   │
│  Agent    │     │  Agent   │     │  Agent   │
└──────────┘     └──────────┘     └──────────┘
                       ▲
┌──────────┐           │
│ Data      │──────────┘
│ Agent     │
└──────────┘

Workflow Definition Format

{
  "name": "market-analysis",
  "description": "Comprehensive market analysis for product launch",
  "agents": {
    "researcher": {
      "task": "Research competitor landscape and market size",
      "inputs": ["product_description"],
      "outputs": ["competitor_list", "market_size"],
      "dependencies": []
    },
    "data_collector": {
      "task": "Collect pricing and feature data from competitors",
      "inputs": ["competitor_list"],
      "outputs": ["pricing_data", "feature_matrix"],
      "dependencies": ["researcher"]
    },
    "analyst": {
      "task": "Analyze positioning opportunities and pricing strategy",
      "inputs": ["pricing_data", "feature_matrix", "market_size"],
      "outputs": ["positioning_report", "pricing_recommendation"],
      "dependencies": ["data_collector", "researcher"]
    },
    "writer": {
      "task": "Write executive summary combining all findings",
      "inputs": ["positioning_report", "pricing_recommendation"],
      "outputs": ["executive_summary"],
      "dependencies": ["analyst"]
    }
  },
  "config": {
    "max_parallel": 3,
    "timeout_per_agent": 300,
    "retry_on_failure": true,
    "quality_threshold": 0.7
  }
}

Agent States

StateDescription
PENDINGWaiting for dependencies to complete
READYAll dependencies met, queued for execution
RUNNINGCurrently executing
COMPLETEDFinished successfully
FAILEDFailed after all retries
SKIPPEDSkipped due to upstream failure
EVALUATINGOutput being evaluated for quality

Execution Strategy

1. Topological sort the DAG to determine execution order 2. Identify parallel groups: nodes with no inter-dependencies run simultaneously 3. Execute root nodes first (no dependencies) 4. Chain results: completed node outputs become inputs for dependents 5. Evaluate outputs at quality gates 6. Merge terminal outputs into final result

Workflows

Workflow 1: Define and Validate

1. Define agents with tasks, inputs, outputs, dependencies
2. Run dag_analyzer.py to validate:
   - No cycles in the dependency graph
   - All referenced inputs are produced by upstream agents
   - No unreachable nodes
   - Critical path length is acceptable
3. Estimate execution time based on agent count and dependencies

Workflow 2: Execute Orchestration

1. Load workflow definition
2. Initialize session (session_manager.py)
3. Topological sort to determine execution order
4. For each parallel group:
   a. Spawn agents (up to max_parallel)
   b. Monitor progress on board
   c. Collect outputs on completion
   d. Evaluate outputs against quality threshold
5. Pass outputs to downstream agents as inputs
6. Merge final outputs
7. Generate execution report

Workflow 3: Evaluate and Iterate

1. Collect all agent outputs
2. Run quality evaluation (eval sub-skill)
3. Rank outputs by quality score (result_ranker.py)
4. If any output below threshold:
   a. Retry the agent with adjusted instructions
   b. Or flag for human review
5. Merge passing outputs into final result

Common Patterns

Fan-Out / Fan-In

Multiple independent agents work in parallel, then a single agent merges results:

Task A ──┐
Task B ──┼──> Merge
Task C ──┘

Pipeline

Sequential agents where each transforms the previous output:

Extract ──> Transform ──> Load ──> Validate

Reducer

Multiple agents produce competing outputs, ranked and best one selected:

Agent 1 ──┐
Agent 2 ──┼──> Rank ──> Best Output
Agent 3 ──┘

Validator Chain

Each agent validates the previous agent's work:

Generate ──> Review ──> Fix ──> Approve

Best Practices

1. Small, focused agent scopes -- each agent should have a single clear objective 2. Explicit inputs/outputs -- never rely on implicit shared state between agents 3. Quality gates between stages -- evaluate before passing outputs downstream 4. Timeout per agent -- prevent runaway agents from blocking the workflow 5. Retry with context -- when retrying a failed agent, include the failure reason 6. Merge strategy documented -- how competing or complementary outputs combine 7. Critical path awareness -- optimize the longest dependency chain first 8. Idempotent agents -- agents should produce the same output given the same input

Common Pitfalls

PitfallWhy It HappensFix
Cycle in DAGAgent A depends on B which depends on ARun dag_analyzer.py before execution
Output format mismatchAgent B expects JSON, Agent A produces markdownDefine explicit output schemas per agent
Single bottleneck agentOne agent depends on everythingRestructure DAG to parallelize dependencies
Lost context between agentsOutputs too terse for downstream useRequire structured output with context preservation
Quality degradation in mergeNaive concatenation loses coherenceUse a dedicated merge agent with synthesis instructions
Runaway execution timeNo timeouts, retry loopsSet timeout_per_agent and max retries

Troubleshooting

ProblemCauseSolution
Workflow hangs at agent NDependency not met or agent timeoutCheck board for PENDING agents; verify upstream completed; check timeout config
Merged output is incoherentNo merge strategy definedUse the merge sub-skill with explicit synthesis instructions
Agent produces wrong formatInput/output contract unclearDefine JSON schemas for agent inputs and outputs
DAG validation fails with cycleCircular dependency in definitionUse dag_analyzer.py to identify the cycle; restructure the dependency chain
Quality eval fails everythingThreshold too strict for task complexityLower threshold or add a revision step before eval

Success Criteria

  • DAG validation passes on every workflow definition before execution
  • Parallel execution utilization above 60% -- agents running in parallel most of the time
  • Quality gate pass rate above 80% -- agent outputs meet threshold on first attempt
  • End-to-end execution time within 2x critical path -- parallelization delivers real speedup
  • Zero lost outputs -- every agent's output is captured and available for merge/review
  • Merge coherence score above 0.7 -- final merged output reads as a unified deliverable

Scope and Limitations

This skill covers:

  • Multi-agent workflow design with DAG dependency graphs
  • Agent spawning, monitoring, and lifecycle management
  • Output quality evaluation and ranking
  • Result merging strategies for coherent final deliverables

This skill does NOT cover:

  • Individual agent design or prompt engineering (see agent-designer)
  • Agent memory and self-improvement (see self-improving-agent)
  • Infrastructure for running agents (compute, scheduling, deployment)
  • Real-time streaming communication between agents

Integration Points

SkillIntegrationData Flow
agent-designerDefines individual agent capabilities that become DAG nodesAgent specs flow in; execution results flow back for agent tuning
self-improving-agentEach agent can use self-improvement patterns to get betterSession feedback from orchestration feeds into agent learning loops
prompt-engineer-toolkitAgent task prompts benefit from prompt engineeringOptimized prompts improve individual agent quality within the DAG
context-engineManages what context each agent seesContext retrieval provides relevant inputs to each spawned agent
observability-designerMonitors workflow execution and agent healthAgent state transitions and timing metrics feed into dashboards

Related skills

FAQ

What are agenthub's sub-skills?

Init, Run, Spawn, Board, Eval, Merge, and Status, each handling one stage of the orchestration lifecycle.

How does it validate a workflow?

dag_analyzer.py checks the dependency graph for cycles, unreachable nodes, missing inputs, and critical-path length.

AI & Agent Buildingagentsautomationllm

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.