borghei/Claude-Skills / engineering/agenthub
agenthub
VerifiedRuns a multi-agent job as a dependency graph: validates the DAG, tracks each agent's state on a board, then ranks and merges their outputs. Use when spawning parallel agents, monitoring a run, or merging results.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 9.8 KB |
| assets/sample_session.json | config | 4.5 KB |
| assets/sample_workflow.json | config | 1.5 KB |
| references/multi-agent-patterns.md | markdown | 5.6 KB |
| references/operations-and-quality.md | markdown | 2.9 KB |
| references/orchestration-core.md | markdown | 4.9 KB |
| scripts/board_manager.py | script | 10.9 KB |
| scripts/dag_analyzer.py | script | 13.5 KB |
| scripts/result_ranker.py | script | 11.0 KB |
| scripts/session_manager.py | script | 12.7 KB |
| skills/board.md | markdown | 2.2 KB |
| skills/eval.md | markdown | 2.2 KB |
| skills/init.md | markdown | 2.0 KB |
| skills/merge.md | markdown | 2.3 KB |
| skills/run.md | markdown | 2.1 KB |
| skills/spawn.md | markdown | 1.9 KB |
| skills/status.md | markdown | 2.1 KB |
skills/merge.md
View on GitHub# Sub-Skill: Merge Outputs
**Parent:** agenthub
**Trigger:** "merge agent outputs", "combine results", "synthesize findings"
## Purpose
Merge outputs from multiple agents into a coherent final deliverable. Handles different merge strategies depending on whether outputs are complementary (different aspects) or competing (same aspect, multiple attempts).
## Workflow
### Step 1: Identify Merge Strategy
| Pattern | Strategy | Description |
|---------|----------|-------------|
| Fan-in | **Synthesize** | Each agent covers different aspect; weave together |
| Reducer | **Rank and select** | Multiple agents did same task; pick best |
| Pipeline | **Chain** | Each agent transforms previous output; use final |
| Validator | **Conditional** | Use output only if validation passed |
### Step 2: Collect Terminal Outputs
Gather all outputs from terminal nodes (agents with no dependents):
```bash
python scripts/result_ranker.py --session <session-id> --list-outputs
```
### Step 3: Apply Merge
**Synthesize (fan-in):**
- Organize outputs by topic/section
- Identify overlaps and contradictions
- Create a unified document with proper transitions
- Cite which agent produced each section
**Rank and select (reducer):**
- Score each output using eval criteria
- Select the highest-scoring output
- Optionally incorporate unique good ideas from runner-ups
**Chain (pipeline):**
- The last agent's output is the final result
- Verify it incorporates all upstream transformations
### Step 4: Quality Check
Run a final eval on the merged output:
- Does it address the original objective?
- Is it internally consistent?
- Does it incorporate key findings from all agents?
### Step 5: Format Final Output
Produce the deliverable in the requested format:
- Structured JSON for programmatic consumption
- Markdown document for human reading
- Summary + detailed sections for executive review
## Inputs
| Input | Required | Description |
|-------|----------|-------------|
| Terminal outputs | Yes | Outputs from all terminal agents |
| Merge strategy | No | Auto-detected from DAG pattern |
| Output format | No | JSON, markdown, or structured (default: markdown) |
## Outputs
- Merged final deliverable
- Merge report (what was combined, any conflicts resolved)
- Attribution (which agent contributed which section)
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |