setup
Skill18 starsChanged 11 days agoMITView on GitHub
Make a project ready for the pipe-skills pipeline on Linear or GitHub Issues. Checks the tracker, the team and its project or initiative, or the GitHub project, its states and its priority, fixes what is missing after the user's go, and writes the tracker line in the project CLAUDE.md. Use only when the user runs /pipe-skills:setup or says "set up pipe-skills in this project" or "connect this repository to Linear" or "to a GitHub project".
191 other projects use a version of this.
Adopted by
Most recently taken up by
- finolabs/vibecodetheir own version, first seen Nov 15, 2026
- quickchatai/quickreviewtheir own version, first seen Nov 15, 2026
- tomw1808/flash-agentstheir own version, first seen Nov 15, 2026
- oss-invisible/playwright_mcptheir own version, first seen Nov 15, 2026
- hydra-db/hydradb-claude-codetheir own version, first seen Nov 8, 2026
- WALKERKILLER/Look-Tongji-Notestheir own version, first seen Nov 8, 2026
Used with
Projects with it also use add-voice-transcription, add-discord and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
juancruzmunozalbeloSkilladd-voice-transcription
Add voice message transcription to NanoClaw using OpenAI's Whisper API. Automatically transcribes WhatsApp voice notes so the agent can read and respond to them.
Also in 5 projects that use this
MicrosoftSkilladd-discord
Add Discord bot channel integration via Chat SDK.
Also in 11 projects that use this
- MicrosoftSkill
add-slack
Add Slack channel integration via Chat SDK.
Also in 11 projects that use this
- juancruzmunozalbeloSkill
add-telegram-swarm
Add Agent Swarm (Teams) support to Telegram. Each subagent gets its own bot identity in the group. Requires Telegram channel to be set up first (use /add-telegram). Triggers on "agent swarm", "agent teams telegram", "telegram swarm", "bot pool".
Also in 7 projects that use this
- +8 more from microsoft
Other versions191 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 191
- anthropics/knowledge-work-plugins★ 35ksame name
- garrytan/gbrain★ 32ksame name
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- Q00/ouroboros★ 6.3ksame name
- pytorch/executorch★ 5.2ksame name
- agenticnotetaking/arscontexta★ 3.5ksame name
- aws/agent-toolkit-for-aws★ 3.4ksame name
- spotify/portal-ai-plugins★ 2.8ksame name
181 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository13 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- adviseSkill
- assessSkill
- autonomous-loopSkill
- awaySkill
- final-stateSkill
- implementSkill
- interviewSkill
- prdSkill
- promote-ruleSkill
- reviewSkill
- shipSkill
- sweepSkill
The file
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 170 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 12
Read the tracker file, ${CLAUDE_PLUGIN_ROOT}/trackers/linear.md or ${CLAUDE_PLUGIN_ROOT}/trackers/github.md, and its setup file, …
“Common” is measured: kept by at least 6 in 10 of the 170 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Set up a project
Make the project ready for pipe-skills:prd, pipe-skills:implement, pipe-skills:ship and pipe-skills:autonomous-loop, and change nothing else. Running it again on a ready project changes nothing.
- Read the
CLAUDE.mdat the root of the repository. When it names a tracker, show the tracker line and ask the user to keep it or to change the scope; on keep, take that tracker, team, and project or initiative. On change, or when it names no tracker, ask the user: Linear or GitHub Issues, and which team and project, or team and initiative, or which GitHub project and owner. Offer the projects or initiatives that exist, and a new one as the last option. On change, the map line that exists does not apply to the new scope. - Read the tracker file,
${CLAUDE_PLUGIN_ROOT}/trackers/linear.mdor${CLAUDE_PLUGIN_ROOT}/trackers/github.md, and its setup file,${CLAUDE_SKILL_DIR}/linear.mdor${CLAUDE_SKILL_DIR}/github.md. Check each item of the Requirements of the setup file, read-only. - Report one line per requirement: ready, or missing with the fix. Name what the user must do by hand, and what you can do.
- After the user's go, run the fixes of the Setup section of the setup file. When a state has no option of its own, or the scope changed, the Setup maps every state again as if no map line exists; on keep, the entry of the old map line is the default answer, unless another state already takes that option. Then check the requirements again.
- Write the tracker line in the project
CLAUDE.mdin place of the tracker line that exists, if any. On change, or when the Setup mapped the states again, write the map line that the Setup made in place of the map line that exists, or remove the old line when it made none. Write them in the form that the tracker file shows, next to the rules they belong with, and with the user's names. Do not commit them: say that they are ready to commit.
End with the state of each requirement and the first command to run, for example /pipe-skills:prd.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.