Automated summary
Combines multiple pipe-format blocks from context into one unified output, with deduplication and source attribution.
Strengths
- Intelligent deduplication based on title and content
- Preserves and combines source attributions
- Confidence upgrade when multiple sources confirm
- Optional topic filtering
Limitations
- Requires blocks to be in the specific pipe format
- Can clutter context if too many blocks are merged
- Similarity detection is title-based, not deep semantic
Use this skill after collecting information via multiple /gather calls or other primitives to get a consolidated view.
Avoid using it when you need to keep results separate for individual processing, or when blocks do not follow the expected format.
Security analysis
SafeThe skill only reads and processes text from the conversation context; it does not execute any system commands or external interactions, using only safe tools (Read, Grep, Glob). No destructive or risky actions are instructed.
No concerns found
How this analysis is madeExamples
/merge/merge performance issuesCombine the pipe-format blocks from the last two /gather calls into one unified list.name: merge description: "Combine multiple pipe-format blocks from context into one unified output. Handles dedup, source attribution, and confidence upgrade. Keywords: merge, combine, unify, join, consolidate, union." argument-hint: "[optional: topic filter]" allowed-tools: Read, Grep, Glob
Merge: Combine Multiple Pipe-Format Outputs
You are running the merge primitive — combining multiple pipe-format blocks from conversation context into one unified output. Filter: $ARGUMENTS
When to Use
- After running /gather multiple times on different topics
- After running parallel primitives and wanting to combine results
- When you have scattered findings across conversation and want one unified view
- During consolidate or fractal workflows to merge parallel investigation results
Process
1. Detect All Pipe-Format Blocks
Scan conversation context for ALL blocks matching the pipe-format pattern (the **Source**: /... marker). Collect every one, not just the most recent. Note the source skill and **Pipeline** field for each block.
2. Parse Items
Extract items from each block into a unified working list. Preserve all attributes: title, detail, source, confidence (if present).
3. Deduplicate
- Items with the same title are duplicates
- Items with substantially the same content (>80% overlap in detail) are duplicates
- When merging duplicates:
- Keep the item with richer detail
- Combine source attributions (preserve all sources)
- Upgrade confidence: if 2+ sources confirm the same finding → CONFIRMED, if mixed → highest confidence level present
4. Filter (Optional)
If $ARGUMENTS specifies a topic filter, keep only items matching that topic. If no filter provided, keep all deduplicated items.
5. Renumber
Reset item numbering to sequential (1, 2, 3...) for the final output.
6. Add Merge Summary Section
Between Items and Summary, add a Merge Details section showing:
- Number of input blocks merged (list source skills)
- Item count before dedup
- Item count after dedup
- Number of confidence upgrades applied
- Topic filter used (if any)
7. Construct Pipeline Provenance
Build the **Pipeline** field by combining the pipeline chains from all input blocks. Use + to show merged branches (e.g., /gather (8 items) + /gather (6 items) -> /merge (10 items)).
8. Emit Unified Output
Output in pipe format with header, metadata (including **Pipeline**), deduplicated items as numbered list, Merge Details section, and final summary.
Guidelines
- If no pipe-format blocks are found in context, emit an error message and stop
- When combining sources, use format:
source: file:line, file:line, URL(comma-separated) - Confidence upgrade logic: CONFIRMED if 2+ sources confirm, LIKELY if sources mixed between LIKELY and POSSIBLE, POSSIBLE if all sources POSSIBLE
- Preserve original item detail when deduplicating — merge into the richer description
- If $ARGUMENTS is empty, merge ALL items from ALL blocks (no filtering)
- If merging results in zero items (all filtered out), emit empty Items section and explain in summary
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/merge-pipe-format-blocks-mm8o5260/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/merge-pipe-format-blocks-mm8o5260' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/merge-pipe-format-blocks-mm8o5260/download' --output '.skill-downloads/merge-pipe-format-blocks-mm8o5260/SKILL.md.part' && mv '.skill-downloads/merge-pipe-format-blocks-mm8o5260/SKILL.md.part' '.skill-downloads/merge-pipe-format-blocks-mm8o5260/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
Tools declared by the author (check availability in your agent): Read, Grep, Glob
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/merge-pipe-format-blocks-mm8o5260/SKILL.md' && test -s '.skill-downloads/merge-pipe-format-blocks-mm8o5260/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/merge' && cp -R '.skill-downloads/merge-pipe-format-blocks-mm8o5260' '.claude/skills/merge'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/merge-pipe-format-blocks-mm8o5260'openskills read 'merge-pipe-format-blocks-mm8o5260'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/merge-pipe-format-blocks-mm8o5260/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.