onboarding
Skill5 starsChanged 33 days agoMITView on GitHub
Sets up this vault for a new user. Interviews them briefly, fills in the "About me" and Git sections of AGENTS.md, tailors the writing guide, creates their first real project and person notes from the templates, and offers to remove the fictional examples. Use when the user says "set up my vault", "onboard me", "get me started", "personalize this", runs /onboarding, or opens a fresh copy of this template where AGENTS.md still says "(your name)".
106 other projects use a version of this.
Adopted by
Most recently taken up by
- martinbattaglia-commits/Claude-skillstheir own version, first seen Nov 16, 2026
- Littlpinguin/linkedin-agent-templatetheir own version, first seen Nov 16, 2026
- lengrufeng2008/dsh-skill-librarytheir own version, first seen Nov 15, 2026
- anthropics/claude-plugins-officialtheir own version, first seen Nov 15, 2026
- Kealman/cland-v0their own version, first seen Nov 15, 2026
- LordVayron/video-factorytheir own version, first seen Nov 15, 2026
Used with
Projects with it also use paywalls, popups 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.
CesarjoquinSkillpaywalls
When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions "paywall," "upgrade screen," "upgrade modal," "upsell," "feature gate," "convert free to paid," "freemium conversion," "trial expiration screen," "limit reached screen," "plan upgrade prompt," "in-app pricing," "free users won't upgrade," "trial to paid conversion," or "how do I get users to pay." Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.
Also in 20 projects that use this
CesarjoquinSkillpopups
When the user wants to create or optimize popups, modals, overlays, slide-ins, or banners for conversion purposes. Also use when the user mentions "exit intent," "popup conversions," "modal optimization," "lead capture popup," "email popup," "announcement banner," "overlay," "collect emails with a popup," "exit popup," "scroll trigger," "sticky bar," or "notification bar." Use this for any overlay or interrupt-style conversion element. For forms outside of popups, see cro. For general page conversion optimization, see cro.
Also in 19 projects that use this
coreyhaines31Skillmarketing-council
When the user wants several expert takes on a marketing decision, or asks what a famous marketer would say about it: a simulated board (Seth Godin, David Ogilvy, April Dunford, Byron Sharp, and more), each grounded in their documented frameworks, where they disagree, and a recommendation. To execute, hand off to the relevant skill.
Also in 13 projects that use this
roerohanSkillprospecting
When the user wants to find, qualify, and build a list of prospects to reach out to — across B2B SaaS, general B2B, or local small businesses. Also use when the user mentions "prospecting," "build a prospect list," "find prospects," "find leads," "lead gen list," "find SaaS companies that," "find B2B companies," "find local businesses," "ICP-fit accounts," "who should we go after," "outbound list," "target account list," "find clients near me," "businesses without websites," "prospect research," "qualified leads," "find my first customers," "early adopters," "design partners," "beta users," or "who has this problem." Use this for the list-building and qualification phase. For writing the outbound copy after the list is built, see cold-email. For deep competitive research on specific accounts, see competitor-profiling.
Also in 17 projects that use this
martinbattaglia-commitsSkillmarketing-loops
When the user wants to set up a recurring, self-running marketing workflow — a repeatable loop an AI agent runs on a cadence (weekly, daily, on a trigger) rather than a one-off task. Also use when the user mentions 'marketing loop,' 'recurring marketing workflow,' 'automate my marketing,' 'marketing on autopilot,' 'weekly marketing review,' 'ad fatigue check,' 'content refresh loop,' 'churn watch,' 'ranking drop alert,' 'always-on marketing,' 'marketing automation workflow,' or 'run this every week.' Use this to pick, adapt, and schedule an ongoing marketing loop that orchestrates the other marketing skills. For one-off marketing ideas, see marketing-ideas. For the experimentation loop specifically, see ab-testing.
Also in 10 projects that use this
roerohanSkillemails
When the user wants to create or optimize an email sequence, drip campaign, automated email flow, or lifecycle email program. Also use when the user mentions "email sequence," "drip campaign," "nurture sequence," "onboarding emails," "welcome sequence," "re-engagement emails," "email automation," "lifecycle emails," "trigger-based emails," "email funnel," "email workflow," "what emails should I send," "welcome series," or "email cadence." Use this for any multi-email automated flow. For cold outreach emails, see cold-email. For in-app onboarding, see onboarding.
Also in 19 projects that use this
- +6 more from Cesarjoquin
Other versions106 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 106
- coreyhaines31/marketingskills★ 61ksame name
- anthropics/claude-plugins-official★ 47ksame name
- anthropics/knowledge-work-plugins★ 36ksame name
- actions/runner-images★ 14ksame name
- BuilderIO/agent-native★ 7.7ksame name
- gnekt/My-Brain-Is-Full-Crew★ 3.9ksame name
- ColeMurray/background-agents★ 3.5ksame name
- huytieu/COG-second-brain★ 1.3ksame name
- openai/mcp-extensions★ 1.1ksame name
- Nexus-JPF/note-companion★ 874same name
96 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 repository9 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- decision-recordSkill
- inbox-triageSkill
- log-feedbackSkill
- meeting-notesSkill
- project-briefSkill
- research-captureSkill
- weekly-reviewSkill
The file
We split this skill into the rules it gives an agent
11 rules. 0 are common, 3 are distinctive, and 8 are very specific to this project.
0
Common
Most of the 90 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
8
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Keep the interview short. Ask a few questions at a time, accept short answers, and do not lecture about features.
- Distinctive: line 13
Read AGENTS.md. If "About me" is already filled in, ask whether to update it or skip to step 4.
- Very specific: line 14
Check whether _examples/ folders still exist.
- Very specific: line 15
Run git status to see whether the vault is a git repo and whether origin still points at the template's repository (git remote -v).
- Distinctive: line 19
Ask, in two or three short rounds:
- Very specific: line 30
Add anything they said about tone or phrasing to System/writing-guide.md under "Your additions".
- Very specific: line 35
Ask for one current project.
- Very specific: line 36
Ask for one person they work with or want to keep in touch with.
- Very specific: line 37
Run python3 scripts/check_vault.py and fix anything it reports.
- Very specific: line 42
If origin still points at the template repository, explain that pushing there will fail and offer the commands to point it at their own …
- Very specific: line 43
Commit with vault: onboarding - personalize AGENTS.md, first notes if they agreed to agent commits.
“Common” is measured: kept by at least 6 in 10 of the 90 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
Onboarding
Goal: in about ten minutes, turn the template into the user's vault, with their context in AGENTS.md and at least one real note of their own.
Keep the interview short. Ask a few questions at a time, accept short answers, and do not lecture about features.
1. Check the state
- Read
AGENTS.md. If "About me" is already filled in, ask whether to update it or skip to step 4. - Check whether
_examples/folders still exist. - Run
git statusto see whether the vault is a git repo and whetheroriginstill points at the template's repository (git remote -v).
2. Interview
Ask, in two or three short rounds:
- Their name, and what they do (role, field, or main focus).
- What they want this vault for: projects, research, people, writing, a mix.
- How they want answers: length, tone, anything that annoys them in AI writing.
- Git: do they want agents to commit? To push? Is the remote private?
3. Write it down
- Fill in "About me" in
AGENTS.mdwith their answers, in their words, a line each. - In the Git section, keep the push option they chose and delete the other.
- Add anything they said about tone or phrasing to
System/writing-guide.mdunder "Your additions". - Show them the diff (
git diff AGENTS.md System/writing-guide.md) and ask if it reads right.
4. First real notes
- Ask for one current project. Create it from
System/Templates/Project.mdasProjects/<Name>.md, with today's date and at least one next action. - Ask for one person they work with or want to keep in touch with. Create
People/<First-Last>.mdfromSystem/Templates/Person.mdand link it to the project if they are connected. - Run
python3 scripts/check_vault.pyand fix anything it reports.
5. Clean up and hand over
- Offer to remove the examples:
./setup.sh --remove-examples(it asks before deleting). - If
originstill points at the template repository, explain that pushing there will fail and offer the commands to point it at their own private repository; do not run them without a yes. - Commit with
vault: onboarding - personalize AGENTS.md, first notesif they agreed to agent commits. - Finish with three things to try next, picked for what they said they want:
/meeting-notesafter their next meeting,/inbox-triageonce something lands inInbox/,/weekly-reviewat the end of the week.
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.

