setup
Skill4 starsChanged 14 days agoMITView on GitHub
Set this project up for red-green, or change its setup: profile file (gates, code rules, models, block prompts) and the agent instructions section.
191 other projects use a version of this.
Adopted by
Most recently taken up by
- furkandvrc/conductortheir own version, first seen Nov 16, 2026
- JCodesMore/jobs-for-ai-agentstheir own version, first seen Nov 16, 2026
- finolabs/finolabs-vibecodetheir own version, first seen Nov 16, 2026
- vincentventalon/claude-code-video-editing-skilltheir own version, first seen Nov 15, 2026
- vincentventalon/my-claude-skillstheir own version, first seen Nov 15, 2026
- GoogleCloudPlatform/gemini-cloud-assist-mcptheir own version, first seen Nov 15, 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
MicrosoftSkilladd-slack
Add Slack channel integration via Chat SDK.
Also in 11 projects that use this
juancruzmunozalbeloSkilladd-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★ 36ksame name
- garrytan/gbrain★ 33ksame name
- gavrielc/nanoclaw★ 31ksame name
- nanocoai/nanoclaw★ 31ksame name
- qwibitai/nanoclaw★ 31ksame name
- Q00/ouroboros★ 6.4ksame name
- pytorch/executorch★ 5.2ksame name
- aws/agent-toolkit-for-aws★ 3.5ksame name
- agenticnotetaking/arscontexta★ 3.5ksame 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.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 168 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Every candidate command stays unrun, so the table holds only what the files and CI history say.
- Very specific: line 17
Run ${CLAUDE_PLUGIN_ROOT}/.claude/workflows/red-green/workflow-doctor.sh.
- Very specific: line 24
Read .claude/red-green/profile.json when it exists.
- Distinctive: line 30
Read in this order, each source adding the commands the earlier ones lack:
- Very specific: line 50
Read the rule files: AGENTS.md, CLAUDE.md, contributing and style guides, linter and formatter configs, leaving out the ## red-green …
- Distinctive: line 79
Start from the current profile and set only what the user decided in step 5:
- Very specific: line 87
Every other key, block and field stays exactly as it was.
“Common” is measured: kept by at least 6 in 10 of the 168 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 a project up for red-green
You write the project's profile file, .claude/red-green/profile.json, from what the project's own files say and what
the user picks. The profile's shape is ${CLAUDE_PLUGIN_ROOT}/docs/red-green/args-and-profile.md; read it first.
Every candidate command stays unrun, so the table holds only what the files and CI history say. The user's picks alone decide the gates.
1. Machine
Run ${CLAUDE_PLUGIN_ROOT}/.claude/workflows/red-green/workflow-doctor.sh. Each MISSING line is a tool the user
installs before going on; give the user the doctor's "confirm by hand" list from its --help.
Done when the doctor exits 0 and the user has the hand-check list.
2. Current profile
Read .claude/red-green/profile.json when it exists; step 6 merges into it.
Done when you hold the current profile, or know the file is new.
3. Gate candidates
Read in this order, each source adding the commands the earlier ones lack:
- CI config, of whatever CI tool the project uses.
- Build and test files: package scripts,
Makefile,pyproject.toml,Cargo.tomland their kin.
For a CI tool whose history is reachable (gh run list and gh run view --json jobs for GitHub Actions, the
equivalent for others), take each job's recent duration from it.
Build one table, a row per candidate:
| command | source | kind | CI duration |
| the command as the project runs it | file and line | lint, type check, test or build | recent duration, or - |
A current gate the profile already declares joins the table with profile as its source.
Done when every CI step and build-file target that checks code has a row, and every row has all four columns.
4. Rule candidates
Read the rule files: AGENTS.md, CLAUDE.md, contributing and style guides, linter and formatter configs, leaving
out the ## red-green section step 8 writes. Draft:
code_rules: one line per convention the code must follow that no gate in the table already enforces.commit: the commit-message rule, when a file states one.
The current profile's code_rules and commit join the drafts, marked as current.
Done when every rule file is read and each draft names the file it came from.
5. Picks
Show the user the table and the drafts, then ask one question at a time, in this order, each led by your recommended answer:
- The gates: which rows, a short unique
namefor each, and a tier for each. Recommendfastfor a static check that reads the source without building it (lint, format check, type check),roundfor a build, a test suite or a row you are unsure of, andacceptancefor one too heavy to run each iteration. A run needs at least onefastorroundgate. - The code rules and the commit rule to keep.
- The model preset, from the presets table in
args-and-profile.mdwith what each is for, or keep the current models. - Any block's own
promptorskill(the Plug-ins section of${CLAUDE_PLUGIN_ROOT}/docs/red-green/blocks.md), one per block.
Done when every table row is kept or dropped, each kept row has a name and a tier, and the user has answered the other three; "none" and "keep" are answers.
6. Write
Start from the current profile and set only what the user decided in step 5:
blocks.gates.gates: the picked gates as{name, command, tier}.blocks.mutation: remove it, since a run fails on it.code_rules,commit: the kept rules.- A preset: set each
modelits row gives, and removemodelfrom every other block that any preset row names. - A block's
promptorskill: set it, and remove the other of the two on that block.
Every other key, block and field stays exactly as it was. Write the result to .claude/red-green/profile.json as
JSON with two-space indent.
Done when the file holds every decision and every key the user did not decide is unchanged.
7. Check
node ${CLAUDE_PLUGIN_ROOT}/.claude/workflows/red-green/template/render.mjs --check .claude/red-green/profile.jsonExit 1 prints the run's config error, naming the key: fix that key with the user, write the file again, re-run.
Done when the check exits 0.
8. Agent instructions
Edit CLAUDE.md at the project root when it exists, else AGENTS.md; with neither, ask the user which one to create.
Give it this section, replacing an existing ## red-green section in place:
## red-green
To implement a ticket or spec, offer the user `/red-green:start <path>`. Gates, rules and models live in
`.claude/red-green/profile.json`; `/red-green:setup` changes them.Done when the file has exactly one ## red-green section with this text and the rest of the file is unchanged.
9. Report
Tell the user the paths of the profile and the instructions file, what changed in each, that both are meant to be
committed, and that /red-green:start <ticket path> now runs with the profile.
Done when the user has all four.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

