Pipeline Builder
Break a big, multi-part task into a clean pipeline where each step's output feeds the next, with context carried forward. Use when one prompt is trying to do too much and the result drowns. Works for any multi-stage task in any field.
Install
npx skills add DylXBT/claude-orchestrator-skills --skill pipeline-buildergit clone --depth 1 https://github.com/DylXBT/claude-orchestrator-skills.git /tmp/claude-orchestrator-skills
mkdir -p ~/.claude/skills
cp -r /tmp/claude-orchestrator-skills/pipeline-builder ~/.claude/skills/pipeline-builderPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Pipeline Builder Big asks fail when research, making, and adapting get crammed into one prompt. The fix is a **pipeline**: each step does one job, and its output becomes the next step's input. This skill designs that pipeline with the user. Role-agnostic. "Research → draft → repurpose" is one example shape; a hiring loop, a design review, or a financial close are others. Ask. ## Step 1 — Interview 1. **What's the big task?** The whole thing they're trying to do in one go. 2. **What are the natural stages?** Help them name 2–4 steps where each produces something the next one needs. If they can't, propose stages from the task and confirm. 3. **What context must carry forward?** The facts, brief, or source-of-truth that every stage has to respect so nothing drifts. ## Step 2 — Design the pipeline Write it out as ordered stages. For each stage: ``` STAGE n — <name> Input: <what it receives (incl. carried context)> Does: <the one job> Output: <the artifact it hands to the next stage> ``` Keep stages single-purpose. The first stage's output is usually *not* a draft — it's the brief/analysis the making stage needs. Carry the original brief into every stage so the work stays on-message. ## Step 3 — Run it as steps, not one prompt Have the user run each stage as its own prompt (or sub-agent), passing the prior output + carried context forward. Check the hand-off between stages — that's where drift hides. ## Step 4 — Save the shape
Details
- Skill name
pipeline-builder- Repository
- DylXBT/claude-orchestrator-skills
- Path
pipeline-builder/SKILL.md- License
- MIT
- Repo updated
- 2 June 2026
FAQ
What does the Pipeline Builder skill do?
Break a big, multi-part task into a clean pipeline where each step's output feeds the next, with context carried forward. Use when one prompt is trying to do too much and the result drowns. Works for any multi-stage task in any field.
How do I install the Pipeline Builder skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add DylXBT/claude-orchestrator-skills --skill pipeline-builder. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Pipeline Builder popular?
It lives in DylXBT/claude-orchestrator-skills, which has 114 GitHub stars and 1 forks.
Related skills
Connector Setup
114DylXBT/claude-orchestrator-skills
Plan a safe, least-privilege way to connect the user's real tools (Drive, Slack, a task board, a calendar, etc.) to Claude so it works from live data instead of copy-paste. Use when wiring up connectors/MCP. Works for any stack and any role.
Context Brain
114DylXBT/claude-orchestrator-skills
Build a reusable context pack (a "brain") so Claude reasons from the user's role, audience, voice, and standards every time, instead of generic output. Use when setting up a Project/workspace, or when output is on-topic but off-voice. Works for any role or domain.
Orchestrator
114DylXBT/claude-orchestrator-skills
Assemble the user's context brain, skills, connectors, and pipelines into one system they actually run end-to-end — and document it so a teammate could run it too. The capstone meta-skill. Works for any role.
Dream
75sneg55/agent-starter
Memory consolidation - review, merge, prune, and index memory files. Run periodically to keep memories organized and up-to-date.
Remember
75sneg55/agent-starter
Review auto-memory entries and propose promotions to CLAUDE.md, CLAUDE.local.md, or shared memory. Also detects outdated, conflicting, and duplicate entries across memory layers.
Zettel Note
200lyndonkl/claude
The note-writing discipline for this vault's evergreen knowledge graph, modeled on a Zettelkasten reading companion and governed by the vault conventions. Enforces declarative-claim titles, one claim per note (atomicity), own-words prose with no block quotes, the piped [[slug|Title]] link form, the labeled link-relationship vocabulary (Confirms/Contradicts/Extends/Context/Prerequisite/Builds-on/Applies/Example-of/Contrasts-with), 3-6 links per note, and search-before-create deduplication. Use when capturing a claim as an evergreen note, refactoring a sprawling note into atomic ones, or wiring
Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.