New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Adapting Claude Pipeline

by aaddrick in aaddrick/claude-pipeline

A skill your agent uses when adapting the generic .claude pipeline folder to a specific codebase - adjusting skills, agents, hooks, scripts, prompts, and settings for the target project's tech stack…

MITAuto-check passedAgent Workflows

Install Adapting Claude Pipeline

skills CLI
$ npx skills add aaddrick/claude-pipeline --skill adapting-claude-pipeline -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install aaddrick/claude-pipeline adapting-claude-pipeline --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/aaddrick/claude-pipeline.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/adapting-claude-pipeline .claude/skills/adapting-claude-pipeline && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
adapting-claude-pipeline
GitHub stars
130
Token cost
~2.8k tokens
SKILL.md length
1,037 words
Files
1
Skills in repo
12
Repo updated
First seen
Licence
MIT

At a glance

A skill your agent uses when adapting the generic .claude pipeline folder to a specific codebase - adjusting skills, agents, hooks, scripts, prompts, and settings for the target project's tech stack…

  • Works in 6 steps: Brainstorm → Research Domain Patterns → Audit Existing Inventory → …
  • Adapting the generic .claude pipeline folder to a specific codebase - adjusting skills
  • SKILL.md covers Overview, When to Use, The Process and Common Adaptation Patterns, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Adapting Claude Pipeline is an agent skill from aaddrick/claude-pipeline. Use when adapting the generic .claude pipeline folder to a specific codebase - adjusting skills, agents, hooks, scripts, prompts, and settings for the target project's tech stack and workflows

Its SKILL.md is about 2.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Agent Workflows. The repository describes itself as: Portable Claude Code multi-agent pipeline - skills, agents, hooks, orchestration scripts, and quality gates. The licence is MIT.

When your agent uses it

  • Adapting the generic .claude pipeline folder to a specific codebase - adjusting skills
  • Settings for the target projects tech stack and workflows

Example prompts

  • “/adapting-claude-pipeline”

Requirements

  • Python 3

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Brainstorm
  2. Research Domain Patterns
  3. Audit Existing Inventory
  4. Write the Plan
  5. Execute with Subagents
  6. Verify

What it can do on your machine

Read from SKILL.md and the folder at commit 402eac7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md (its code samples are dot).

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Adapting Claude Pipeline loads about 2.8k tokens when it runs. Until then it costs about 54 tokens; SKILL.md has 1,037 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~54
When it runs · the whole SKILL.md, loaded when a task matches
~2.8k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from aaddrick/claude-pipeline at commit 402eac7, republished under its MIT licence (© aaddrick). 1,037 words, ~2,797 tokens.

Download SKILL.mdSave it as .claude/skills/adapting-claude-pipeline/SKILL.md (or your agent's skills folder).
name
adapting-claude-pipeline
description
Use when adapting the generic .claude pipeline folder to a specific codebase - adjusting skills, agents, hooks, scripts, prompts, and settings for the target project's tech stack and workflows

Adapting Claude Pipeline to a Codebase

Overview

Adapt the generic .claude/ pipeline folder to a specific project's tech stack, domain, and workflows. This means modifying, replacing, or removing every skill, agent, hook, script, prompt, and setting so they serve the target codebase — not the original Laravel/web template.

Core principle: Every file in .claude/ must earn its place. If it doesn't serve the target project, delete it. If it needs modification, modify it. If new capabilities are needed, create them.

When to Use

  • Cloning the claude-pipeline repo into a new project
  • Onboarding an existing codebase with the generic .claude/ folder
  • Switching tech stacks (e.g., Laravel to Python, web to CLI, monolith to microservices)

The Process

dot
digraph adaptation {
    rankdir=TB;

    "1. Brainstorm with user" [shape=box style=filled fillcolor=lightyellow];
    "2. Research domain patterns" [shape=box];
    "3. Audit existing .claude/ inventory" [shape=box];
    "4. Write adaptation plan" [shape=box];
    "5. Execute plan with subagents" [shape=box style=filled fillcolor=lightblue];
    "6. Verify adapted pipeline" [shape=box style=filled fillcolor=lightgreen];

    "1. Brainstorm with user" -> "2. Research domain patterns";
    "2. Research domain patterns" -> "3. Audit existing .claude/ inventory";
    "3. Audit existing .claude/ inventory" -> "4. Write adaptation plan";
    "4. Write adaptation plan" -> "5. Execute plan with subagents";
    "5. Execute plan with subagents" -> "6. Verify adapted pipeline";
}
Phase 1: Brainstorm

REQUIRED: Use the brainstorming skill to explore the target project.

Focus questions on:

  • Tech stack: Language, framework, database, infrastructure
  • Project type: Web app, CLI tool, library, API, microservice, data pipeline, etc.
  • Team workflows: CI/CD, code review, deployment, testing patterns
  • Pain points: What does the team struggle with that agents could help?
  • Existing tooling: Linters, formatters, test runners, build systems
  • Scope: Full adaptation or partial (e.g., keep orchestration, replace agents)?

Key decisions to reach:

  1. Which existing skills/agents/hooks are relevant (keep/modify)?
  2. Which are irrelevant (delete)?
  3. What new capabilities does the project need?
  4. What domain-specific best practices should agents follow?
Phase 2: Research Domain Patterns

Use WebSearch to investigate the target project's domain. This feeds directly into agent definitions and skill content.

Search for:

"[language/framework] best practices [current year]"
"[language/framework] anti-patterns"
"[language/framework] code review checklist"
"[language/framework] common mistakes"
"[language/framework] testing best practices"
"[language/framework] security considerations"
"[language/framework] project structure conventions"
"[tool/framework] CI/CD pipeline best practices"

Capture findings as notes — they will be incorporated into:

  • Agent anti-patterns sections
  • Skill content (technique skills)
  • Hook logic (formatting, linting)
  • Orchestration script stages
Phase 3: Audit Existing Inventory

Categorize every .claude/ file into one of four buckets:

BucketActionExample
Keep as-isUniversal process skillsbrainstorming, writing-plans, TDD, systematic-debugging
ModifyAdapt to new tech stackimplement-issue (change test commands), agents (change domain)
ReplaceSame purpose, different implementationlaravel-backend-developer → python-backend-developer
DeleteIrrelevant to target projectbulletproof-frontend (for a CLI tool), write-docblocks (non-PHP)
Inventory Checklist

Skills (19 in template):

SkillCategoryTypical Decision
brainstormingProcessKeep as-is
bulletproof-frontendDomain (web/CSS)Delete if not web
dispatching-parallel-agentsProcessKeep as-is
executing-plansProcessKeep as-is
handle-issuesWorkflow (GitHub)Keep if using GitHub Issues
implement-issueWorkflow (GitHub)Keep if using GitHub Issues
investigating-codebase-for-user-storiesProcessKeep as-is
process-prWorkflow (GitHub)Keep if using GitHub PRs
review-uiDomain (web/CSS)Delete if not web
subagent-driven-developmentProcessKeep as-is
systematic-debuggingProcessKeep as-is
test-driven-developmentProcessKeep as-is
ui-design-fundamentalsDomain (web/CSS)Delete if not web
using-git-worktreesProcessKeep as-is
using-skillsMetaKeep as-is
write-docblocksDomain (PHP)Replace with language-specific docblock skill
writing-agentsMetaKeep as-is
writing-plansProcessKeep as-is
writing-skillsMetaKeep as-is

Agents (10 in template):

AgentCategoryTypical Decision
bash-script-craftsmanDomain (bash)Keep if project uses bash
bats-test-validatorDomain (bash)Keep if project uses bash
bulletproof-frontend-developerDomain (web)Delete or replace
cc-orchestration-writerMetaKeep as-is
code-reviewerProcessModify (update tech stack refs)
code-simplifierDomain (PHP)Replace with language-specific
laravel-backend-developerDomain (Laravel)Replace with project-specific
phpdoc-writerDomain (PHP)Replace or delete
php-test-validatorDomain (PHP)Replace with language-specific
spec-reviewerProcessKeep as-is (tech-agnostic)

Hooks:

HookTypical Decision
session-start.shKeep as-is (loads using-skills)
post-pr-simplify.shModify (change PHP references) or delete

Settings (settings.json):

SettingTypical Decision
PHP formatter (Pint)Replace with project's formatter
Sensitive file protectionModify patterns for project
Production deploy protectionModify command for project
Desktop notificationsKeep as-is

Scripts:

ScriptTypical Decision
implement-issue-orchestrator.shModify (test commands, agents)
batch-orchestrator.shModify (agent references)
JSON schemasModify if stages change
BATS testsModify to match script changes

Prompts:

PromptTypical Decision
frontend audit/refactorDelete if not web, replace if different frontend
Phase 4: Write the Plan

REQUIRED: Use the writing-plans skill.

The plan should be organized into parallel workstreams where possible:

Workstream A: Delete irrelevant files (quick, no dependencies)
Workstream B: Modify existing files (parallel per file)
Workstream C: Create new skills (use writing-skills skill)
Workstream D: Create new agents (use writing-agents skill)
Workstream E: Modify orchestration scripts (use cc-orchestration-writer agent)
Workstream F: Update hooks and settings

Each task in the plan must specify:

  • File path to create/modify/delete
  • What changes and why
  • Which skill/agent to use for the task (writing-skills, writing-agents, cc-orchestration-writer, etc.)
  • Dependencies on other tasks (if any)
Show full SKILL.md (395 more words)Show less
Phase 5: Execute with Subagents

REQUIRED: Use the subagent-driven-development skill to execute the plan.

Route tasks to the correct agent/skill:

Task TypeHow to Execute
Delete filesDirect (no subagent needed)
Modify existing skillsEdit directly, following writing-skills patterns
Create new skillsInvoke writing-skills skill
Modify existing agentsEdit directly, following writing-agents patterns
Create new agentsInvoke writing-agents skill
Modify orchestration scriptsDispatch cc-orchestration-writer agent via Task tool
Modify hooks/settingsDirect edit
Create new hooksbash-script-craftsman agent via Task tool

Parallel execution: Tasks in different workstreams with no shared files can run in parallel using dispatching-parallel-agents.

Phase 6: Verify

After all modifications:

  1. File inventory check — Glob .claude/ and verify no orphaned or irrelevant files remain
  2. Cross-reference check — Grep for references to deleted skills/agents/files and fix broken refs
  3. Settings validation — Ensure settings.json hooks reference existing files and commands
  4. Skill description audit — All skill descriptions match new project context
  5. Agent coordination audit — Deferral relationships between agents are consistent
  6. Dry run — Walk through a typical workflow (e.g., implement-issue) mentally to verify the pipeline makes sense

Common Adaptation Patterns

Web to CLI/Library

Delete: bulletproof-frontend, review-ui, ui-design-fundamentals, bulletproof-frontend-developer agent, all frontend prompts

Replace: laravel-backend-developer → language-specific developer agent

Modify: code-simplifier (change language), test validators (change framework)

Laravel to Python/Django

Replace: laravel-backend-developer → django-backend-developer, php-test-validator → pytest-validator, code-simplifier → python code simplifier, write-docblocks → python docstring writer

Modify: settings.json (Pint → Black/Ruff), post-pr-simplify.sh (PHP → Python)

Monolith to Microservices

Add: Service-specific agents, API contract validation skill, cross-service testing patterns

Modify: implement-issue workflow (multi-repo awareness), code-reviewer (service boundaries)

Adding New Domain

Add: Domain-specific agents (ML engineer, data pipeline developer, etc.), domain testing skills

Keep: All process skills, orchestration infrastructure

Red Flags

  • Keeping irrelevant skills "just in case" — delete them. They add noise and confuse skill discovery.
  • Generic agent personas — every agent should reference the actual project, its structure, and its conventions.
  • Orphaned references — grep for deleted skill/agent names in remaining files.
  • Skipping web research — domain patterns and anti-patterns are critical for agent quality.
  • Not updating settings.json — stale hooks that reference missing tools will cause errors.

Key Principles

  • Delete aggressively — fewer, focused files beat a bloated pipeline
  • Research before writing — WebSearch for domain patterns before creating agents/skills
  • Test the pipeline — walk through a real workflow after adaptation
  • Use the meta-skills — writing-skills and writing-agents exist to ensure quality; use them for new content
  • Preserve process skills — brainstorming, TDD, debugging, planning are universal; don't delete these

© aaddrick, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .claude/skills/adapting-claude-pipeline of aaddrick/claude-pipeline.

Open the folder on GitHubat commit 402eac7

Compare with similar skills

Adapting Claude Pipeline next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Adapting Claude Pipeline compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Adapting Claude Pipeline this skillaaddrick/claude-pipeline130—~2.8kAutomated safety check: PassMIT
Documentationsamchon/typia5.9k—~1.1kAutomated safety check: PassMIT
Openlark Code Standardsfoxzool/openlark106—~1.8kAutomated safety check: NotesApache-2.0
Tasksgenkovich/sdd171—~4.8kAutomated safety check: PassMIT
Agentsbutterbase-ai/butterbase-skills534—~1.8kAutomated safety check: PassMIT
Building With Medusamedusajs/medusa-agent-skills228—~4.1kAutomated safety check: PassNone

Similar skills

  • Documentation

    samchon/typia

    Defines README, website-guide, and agent-instruction structure, audience, prose formatting, and voice for typia.

    5.9k GitHub stars~1.1k tokensUpdated 4 days ago
    Agent WorkflowsAuto-check passed

  • Openlark Code Standards

    foxzool/openlark

    OpenLark 项目代码规范检查技能。用于快速审查仓库内的架构一致性、API 实现套路、参数校验、命名与导出规范，并输出可执行检查清单与证据路径。Triggers: code review / consistency check / architecture audit / 规范检查 / 风格一致性 / 体检 / 对齐约定。项目锚点见 AGENTS.mdCONVENTIONS 与…

    106 GitHub stars~1.8k tokensUpdated yesterday
    Agent WorkflowsAuto-check: notes

  • Tasks

    genkovich/sdd

    A skill your agent uses to break a designed feature into atomic, ≤1-day tasks with a dependency graph, a per-task Definition of Done, and a machine-readable tasks.json that the implement engine…

    171 GitHub stars~4.8k tokensUpdated 1 mo ago
    Agent WorkflowsAuto-check passed

  • Agents

    butterbase-ai/butterbase-skills

    A skill your agent uses when designing, deploying, or debugging a Butterbase Agent (declarative LLM/tool graph), registering an MCP server for tool use, or wiring access controls and rate limits.

    534 GitHub stars~1.8k tokensUpdated 5 days ago
    Agent WorkflowsAuto-check passed

  • Building With Medusa

    medusajs/medusa-agent-skills

    Load automatically when planning, researching, or implementing ANY Medusa backend features (custom modules, API routes, workflows, data models, module links, business logic).

    228 GitHub stars~4.1k tokensUpdated 6 days ago
    Agent WorkflowsAuto-check passed

  • Blueprint Cloudflare Scaffold

    receptron/mulmoterminal

    Lay out a Worker with D1 and static Vue assets, with tests that run inside the Workers runtime.

    237 GitHub stars~782 tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from aaddrick/claude-pipeline

All 12 skills in this repo

  • Writing Agents

    aaddrick/claude-pipeline

    A skill your agent uses when creating new agents, editing existing agents, or defining specialized subagent roles for the Task tool

    130 GitHub starsUsed in 1 repo~3.3k tokens
    Auto-check passed

  • Investigating Codebase For User Stories

    aaddrick/claude-pipeline

    A skill your agent uses when asked to create user stories from a codebase, document existing features as stories, or reverse-engineer requirements from code

    130 GitHub stars~2.2k tokensUpdated 7 mo ago
    Auto-check passed

  • Review UI

    aaddrick/claude-pipeline

    Comprehensive UI/CSS review using parallel agents. An agent skill from aaddrick/claude-pipeline.

    130 GitHub stars~2.5k tokensUpdated 7 mo ago
    Auto-check passed

  • Using Git Worktrees

    aaddrick/claude-pipeline

    A skill your agent uses when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees in .worktrees/

    130 GitHub stars~1.3k tokensUpdated 7 mo ago
    Auto-check passed

  • Implement Issue

    aaddrick/claude-pipeline

    A skill your agent uses when given a GitHub issue number and base branch to implement end-to-end

    130 GitHub starsUsed in 1 repo~889 tokens
    Auto-check passed

  • Write Docblocks

    aaddrick/claude-pipeline

    A skill your agent uses when documentation coverage is low, after composer docs:coverage shows gaps, or when asked to batch-write PHPDoc blocks across multiple files

    130 GitHub stars~956 tokensUpdated 7 mo ago
    Auto-check passed

Categories

Questions about Adapting Claude Pipeline

What does Adapting Claude Pipeline do?

A skill your agent uses when adapting the generic .claude pipeline folder to a specific codebase - adjusting skills, agents, hooks, scripts, prompts, and settings for the target project's tech stack…. Adapting Claude Pipeline is an agent skill from aaddrick/claude-pipeline.

When should I use Adapting Claude Pipeline?

Adapting Claude Pipeline fits situations like: adapting the generic .claude pipeline folder to a specific codebase - adjusting skills; settings for the target projects tech stack and workflows.

How do I install Adapting Claude Pipeline in Claude Code?

Run `npx skills add aaddrick/claude-pipeline --skill adapting-claude-pipeline -a claude-code`. Or copy the skill folder (.claude/skills/adapting-claude-pipeline in aaddrick/claude-pipeline) into .claude/skills/adapting-claude-pipeline in your project. Claude Code loads it when a task matches its description.

How do I install Adapting Claude Pipeline in Codex?

Run `npx skills add aaddrick/claude-pipeline --skill adapting-claude-pipeline -a codex`. Or copy the skill folder (.claude/skills/adapting-claude-pipeline in aaddrick/claude-pipeline) into .agents/skills/adapting-claude-pipeline in your project. Codex loads it when a task matches its description.

Can I use Adapting Claude Pipeline in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add aaddrick/claude-pipeline --skill adapting-claude-pipeline -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/adapting-claude-pipeline, .gemini/skills/adapting-claude-pipeline, .github/skills/adapting-claude-pipeline and .opencode/skills/adapting-claude-pipeline in your project.

What does Adapting Claude Pipeline need to run?

SKILL.md names no scripts, command-line tools or credentials: Adapting Claude Pipeline is instructions for the agent only. Our summary lists: Python 3.

Does Adapting Claude Pipeline access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Adapting Claude Pipeline safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Adapting Claude Pipeline use?

Adapting Claude Pipeline is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Adapting Claude Pipeline use?

About 2.8k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Adapting Claude Pipeline?

Skills that share tags, products or a category with Adapting Claude Pipeline: Documentation (samchon/typia, 5.9k stars), Openlark Code Standards (foxzool/openlark, 106 stars), Tasks (genkovich/sdd, 171 stars) and Agents (butterbase-ai/butterbase-skills, 534 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Adapting Claude Pipeline?

aaddrick (a GitHub user) maintains it in aaddrick/claude-pipeline, which has 130 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on February 25, 2026.

Source: aaddrick/claude-pipeline on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.