welcome
Skill2 starsChanged 8 months agoMITView on GitHub
First-run onboarding for a beginner. Assesses level and needs in 6 questions, explains each tool before installing it, installs only after a yes, then writes the profile.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- microsoft/amplifier-app-nanoclawtheir own version, first seen Oct 13, 2026
- TravisCao/cleanresearchtheir own version, first seen Oct 13, 2026
- Pearl1531/Archetype-talktheir own version, first seen Oct 13, 2026
- shorin-nikita/ai-teamtheir own version, first seen Oct 11, 2026
- tymrtn/tomorrowkit-for-mindstheir own version, first seen Aug 30, 2026
- Q00/ouroborostheir own version, first seen Jul 31, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- Q00/ouroboros★ 6.4ksame name
- microsoft/amplifier-app-nanoclaw★ 5same name
- tymrtn/tomorrowkit-for-minds★ 4same name
- adraalabs/skills★ 2same name
- Pearl1531/Archetype-talk★ 2same name
- omarrns/claude-code-skills★ 1same name
- shorin-nikita/ai-team★ 1same name
- TravisCao/cleanresearch★ 1same name
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 repository34 other files it gives its agents.
- global/CLAUDE.mdCLAUDE.md
- templates/CLAUDE.mdCLAUDE.md
- accessibility-reviewSkill
- api-designSkill
- audit-runnerSkill
- auto-fixSkill
- brainstormSkill
- compliance-checkSkill
- continuous-testing-guardianSkill
- contract-lookupSkill
- explainSkill
- idea-validatorSkill
- load-test-auditSkill
- monthly-reviewSkill
- new-featureSkill
- nextjs-reviewSkill
- perfection-auditSkill
- performance-deep-auditSkill
- post-code-security-auditSkill
- pre-code-security-checkSkill
- pre-deploymentSkill
- project-setupSkill
- pro-samuelSkill
- quick-auditSkill
- risk-scoreSkill
- roadmap-builderSkill
- secret-scannerSkill
- seo-auditSkill
- supabase-reviewSkill
- token-economySkill
- typescript-reviewSkill
- ux-cognitive-load-checkSkill
- ux-heuristic-auditSkill
- ux-progressive-disclosureSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
If the person asks a side question, answer it, then ask the pending question once, plainly.
- Distinctive: line 21
If a read needs permission, say "I ask your permission before reading", never "blocked".
- Distinctive: line 22
Never guess the level: ask, then confirm in one sentence ("So you are at level Practice, correct?").
- Very specific: line 26
Read ~/.claude/kit/profile.json.
- Distinctive: line 34
Do you work with mail, calendar, documents or other apps you would like Claude to reach?
- Distinctive: line 35
Do you need Claude to browse or test web pages for you?
- Very specific: line 62
Write ~/.claude/kit/profile.json with language, level, needs, tools_installed, mode: "learner", date.
“Common” is measured: kept by at least 6 in 10 of the 7 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
/welcome
Language: if the person writes in French, or language is fr in ~/.claude/kit/profile.json, follow SKILL.fr.md in this folder instead.
Didactic path for someone setting up Claude Code alone (or after a short training). Skipped by /pro-samuel.
Principles
- Simple words. Define any technical term the first time, or point to
/explain <term>. - Nothing is installed without a clear "yes". Before each tool: what it is, why it helps this person, what it changes on the machine, how to remove it.
- One question at a time. Never more than 6 in total.
- If the person asks a side question, answer it, then ask the pending question once, plainly. Never apologise for repeating it or promise it is the last time.
- If a read needs permission, say "I ask your permission before reading", never "blocked". If the profile cannot be read, answer in the language of the person's message.
- Never guess the level: ask, then confirm in one sentence ("So you are at level Practice, correct?").
Step 1: Detect the setup (no questions yet)
Read ~/.claude/kit/profile.json. If it exists and --redo is absent, greet by level and ask what to do today instead of restarting.
Otherwise detect: OS, shell, and presence of Homebrew or winget, Git, Node, Python. Report in plain words what is already there.
Step 2: Six questions
- What do you want to do with Claude Code? (write, code, automate, analyse, other)
- Have you used a terminal before? (never / a little / often)
- Have you used Claude Code before? (never / a few times / daily)
- Do you work with mail, calendar, documents or other apps you would like Claude to reach?
- Do you need Claude to browse or test web pages for you?
- How do you prefer to learn: short explanations, or detail with examples?
Step 3: Level
| Level | Signal | Effect |
| Discovery | never used a terminal or Claude Code | Explain everything, propose few tools, extra safeguards |
| Practice | some terminal or Claude Code use | Short explanations, tools proposed from needs |
| Autonomous | daily use | Terse, option lists, advanced tier offered |
Step 4: Propose tools from needs, one by one
| Need | Tool | Plain explanation |
| Browse or test pages | Playwright | Lets Claude drive a Chrome window like a person would |
| Mail, calendar, docs, many apps | Composio | One account that connects Claude to hundreds of apps without wiring each one |
| Any person, any level | Composio, offered to everyone | Optional: the benefit is explained, a free account is needed, refusal costs nothing |
| Reusable routines | Skills | A written recipe Claude can follow on demand |
| Safety net | Guardrails (2 hooks) | Small checks that stop risky commands before they run |
For each: explain, ask "install it?", install on yes, verify it works, record in profile.
Guardrails: on yes, run node ~/.claude/kit/hooks/register-hooks.mjs (backs up settings.json, merges, undo with --remove). Say what they block: destructive commands (guard-destructive) and real-looking secrets written to files (guard-secrets). Pro mode registers them in the single confirmed pass.
Step 5: Write the profile
Write ~/.claude/kit/profile.json with language, level, needs, tools_installed, mode: "learner", date. Local file, never sent anywhere.
Step 6: Close
One short summary: what is installed, what each does, how to ask for help (/explain <term>), how to change level (/welcome --redo). Offer the advanced tier only to Autonomous, and say how: keep the kit folder you downloaded (the starter copies only 3 skills), then run bash global/install-global.sh --dry-run to preview and without --dry-run to install (backs up, never overwrites). Everyone else: mention once that /welcome --redo later unlocks it.
Rules
- Windows: tier 1 runs natively. The advanced tier needs WSL2; explain it and let the person decide.
- Language follows
languagein the profile; the French edition mirrors this file. - Any external send or account creation needs a confirmation in the same turn.
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.

