human-merge

Merge multiple agent or analyst reports into one decision-ready surface with traced figures.

14|1|Updated Jun 14, 2026
One-click install
npx skills add https://github.com/allemaar/open-skills --skill human-merge-allemaar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: human-merge
Source: https://github.com/allemaar/open-skills/tree/main/skills/human-merge
Command: npx skills add https://github.com/allemaar/open-skills --skill human-merge-allemaar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? When several agents, analysts, or documents each return a separate report, the pile becomes undecidable: readers cannot tell which claims are corroborated, which rest on one source wearing several hats, and which reports quietly contradict each other. This Skill collapses correlated reports into their true sources, classifies conflicts instead of averaging them, and pools coverage so gaps no single report saw become visible. ## Core Features & Use Cases - Source independence analysis: Applies a five-key test per claim to detect when reports share a document, brief, corpus, or parent agent, capping confidence labels accordingly. - Conflict classification and supersession tracking: Distinguishes contradictions from scope, vintage, definitional, and claim-type mismatches, and flags when a live decision rests on a superseded figure. - Ledger and numeral trace: Produces an audit ledger with per-claim source counts and a trace mapping every number in the output back to a frozen input, plus a bundled checker script for mechanical style rules. - Use Case: After dispatching four sub-agents to research a vendor decision, run the merge to discover that two agents quoted the same source, one figure is outdated but still cited in a live budget, and a key cost was never investigated by anyone. ## Quick Start Ask the agent to merge these reports into one decision-ready summary using /human-merge, listing every input with its author, date, and stated basis for each claim.

Frequently Asked Questions about human-merge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I combine reports from multiple AI agents into one summary?

Inventory each report with its author, date, and stated basis, then dedupe claims, count independent sources rather than reports, classify conflicts, and pool coverage gaps. The output is a verdict, a ledger with per-claim source counts, and a numeral trace back to the inputs.

How do I tell if two agent reports are independent sources?

Run the five-key test per claim: same document quoted, same person interviewed, same brief or corpus inherited, one read the other, or sibling agents over shared context. If either report could not have been wrong while the other stayed right, count them as one source.

What should I do when two reports give conflicting numbers?

Classify the conflict first: contradiction, scope mismatch, vintage, claim-type mismatch, confidence-only, or definitional. Never average the numbers or drop the outlier; keep both values, name the resolving check, and put live conflicts in the verdict sentence.

Can reports that do not combine still produce a valid output?

Yes, a merge with zero combined claims is a legitimate deliverable. State the refusal first, give one named reason per parked item, say what would make each combinable, then present each finding in full with its own verdict and grade.

What are the limitations of automated report merging checks?

The bundled checker script only grades mechanical rules like figure width, bar proportionality, and sentence length. It cannot verify independence, honest conflict classification, or whether a number traces to a real source, so a manual numeral-by-numeral comparison against frozen inputs is required.