Install
$ agentstack add skill-synthesisengineering-synthesis-skills-synthesis-response-merger ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Response Merger
Merge multiple LLM responses into a single, comprehensive, unified document that preserves all detail from every input.
Input
A document containing one or more prompts and their corresponding responses from one or more LLM engines. This is referred to as the prompt-response document.
Process
Step 1: Read thoroughly
Read the entire prompt-response document. Identify each distinct prompt and every response generated for it.
Step 2: Plan the merge
Before writing, produce a plan:
- How will key points from each response be integrated?
- Where does useful context or framing from the original prompts belong?
- What organizational structure best serves the combined content?
- Where do responses overlap, and where do they contribute unique material?
Step 3: Write the unified document
Follow the plan and produce the unified output.
Critical rules:
- Do NOT simplify, shorten, or reduce any level of detail. This is a merge, not a summary.
- Do NOT omit minor details from any individual response. Every detail matters.
- The unified document must be significantly longer and more detailed than even the longest single input response.
- No section of the output should have less detail than the corresponding section in any input response.
- Incorporate relevant context and framing from the original prompts where it aids understanding.
- Format for readability: use headings, lists, and structure appropriate to the content.
Output structure
- Plan -- the integration plan (brief, for transparency)
- Unified document -- the comprehensive merged result
Related
Part of the synthesis writing craft — the writer writes, the AI assists.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: synthesisengineering
- Source: synthesisengineering/synthesis-skills
- License: Apache-2.0
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.