setup
Skill8 starsChanged 8 months agoMITView on GitHub
Interactive setup wizard. Personalizes your agent-seed with voice, context, agents, and integrations. Run this first.
191 other projects use a version of this.
Adopted by
Most recently taken up by
- 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
- 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
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
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. 0 are common, 13 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 168 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Check what's available:
- Distinctive: line 16
If installed: "I'll create PRs for all changes so you can review them."
- Distinctive: line 17
If not: "No worries! I'll commit changes directly.
- Distinctive: line 22
Ask these questions one at a time.
- Distinctive: line 34
Ask: "I'd love to learn your communication style so I can draft messages that sound like you.
- Very specific: line 46
Leave context/voice/patterns.md with a template for later
- Distinctive: line 49
Leave template files in place
- Distinctive: line 68
All defaults + suggest: drafter (writing), tracker (issue tracking)
- Distinctive: line 71
Always include: todo-manager, reflection (these are core)
- Distinctive: line 73
Ask: "Based on your role as [X], I'd suggest these agents: [list].
- Very specific: line 76
Create the agent .md file with proper frontmatter
- Very specific: line 77
Add it to .claude/agents/index.md routing table
- Distinctive: line 81
Ask: "Do you want to connect any of these?
- Distinctive: line 91
Create the agent definition
- Very specific: line 93
Add safety hooks to .claude/settings.json if needed (e.g., Slack read-only)
- Very specific: line 97
Update context/index.md to link to all created context files
- Very specific: line 98
Update memory/MEMORY.md with basic profile info
- Distinctive: line 101
If gh CLI is available:
- Very specific: line 104
Commit: "feat: initial agent-seed setup"
- Distinctive: line 107
If no gh CLI:
“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
/setup - Setup Wizard
Interactive wizard that personalizes your agent-seed installation. Can be re-run anytime to add new agents or integrations.
Step 0: Environment Check
Check what's available:
- git — run
git --version. If missing, stop and tell the user to install git. - gh CLI — run
gh --version.- If installed: "I'll create PRs for all changes so you can review them."
- If not: "No worries! I'll commit changes directly. You can install the GitHub CLI later if you want PR-based workflows: https://cli.github.com"
- Detect LLM tool — check which tool is running (Claude Code, Cursor, etc.) and note it for context.
Step 1: Identity
Ask these questions one at a time. Wait for each answer before proceeding.
- "What's your name?"
- "What do you do? (e.g., software engineer, product manager, designer, founder, student, etc.)"
- "What tools and services do you use daily? (e.g., GitHub, Linear, Slack, Jira, Notion, etc.)"
Save answers to:
context/work/index.md— role and overviewcontext/work/tools.md— tools and services
Step 2: Voice (Optional but Encouraged)
Ask: "I'd love to learn your communication style so I can draft messages that sound like you. You can:"
- Option A: "Paste 5-10 messages you've sent recently (Slack, email, etc.)"
- Option B: "Describe your style: formal or casual? Emoji or no emoji? Short or detailed?"
- Option C: "Skip this for now — you can always add it later"
If Option A:
- Analyze the messages for patterns: tone, capitalization, punctuation, greetings, closings, emoji usage, sentence length, formality level
- Generate
context/voice/index.mdwith a voice profile - Generate
context/voice/patterns.mdwith extracted patterns and examples
If Option B:
- Generate a basic
context/voice/index.mdfrom the description - Leave
context/voice/patterns.mdwith a template for later
If Option C:
- Leave template files in place
Step 3: Agent Selection
Based on the user's role, suggest a starter set of agents:
Software Engineer:
- coder, reviewer, researcher, todo-manager, reflection (all ship by default)
- Suggest: pr-agent (branch + PR creation)
Product Manager:
- researcher, todo-manager, reflection (ship by default)
- Suggest: note-taker (meeting notes), tracker (issue tracking)
Designer:
- researcher, todo-manager, reflection (ship by default)
- Suggest: feedback-collector (design review)
Founder / Generalist:
- All defaults + suggest: drafter (writing), tracker (issue tracking)
Any role:
- Always include: todo-manager, reflection (these are core)
Ask: "Based on your role as [X], I'd suggest these agents: [list]. Want me to add any of these? Or describe what else you need and I'll create a custom agent."
For each selected agent:
- Create the agent
.mdfile with proper frontmatter - Add it to
.claude/agents/index.mdrouting table
Step 4: Integrations (Optional)
Ask: "Do you want to connect any of these? (just say which ones)"
| Integration | What it adds |
| Slack (read-only) | slack-reader agent + safety hook to block posting |
| GitHub | pr-agent for branch + PR workflows |
| Linear | tracker agent for issue management |
| Jira | tracker agent (Jira variant) |
For each selected integration:
- Create the agent definition
- Update
.claude/agents/index.md - Add safety hooks to
.claude/settings.jsonif needed (e.g., Slack read-only)
Step 5: Save and Commit
- Update
context/index.mdto link to all created context files - Update
memory/MEMORY.mdwith basic profile info - Validate everything: run
scripts/check-markdown-policy.sh
If gh CLI is available:
- Create branch:
feat/initial-setup - Stage all generated files
- Commit: "feat: initial agent-seed setup"
- Push and create PR with summary of what was configured
If no gh CLI:
- Stage all generated files
- Commit: "feat: initial agent-seed setup"
- Tell the user what was created
Step 6: Next Steps
Tell the user: "You're all set! Here's what you can do now:"
/standup— start your day with a briefing/eod— end your day, capture learnings/learn— let the system improve itself- "Edit
context/voice/anytime to refine your voice profile" - "The system will learn your preferences over time and propose improvements via PRs"
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.

