agentleFS
Rome-1Rome-1/obsidian-claude-starter/.claude/skills/onboarding/SKILL.md

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

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.
  • CesarjoquinSkill

    paywalls

    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

  • CesarjoquinSkill

    popups

    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

  • coreyhaines31Skill

    marketing-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

  • roerohanSkill

    prospecting

    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-commitsSkill

    marketing-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

  • roerohanSkill

    emails

    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

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
  1. Distinctive:

    Keep the interview short. Ask a few questions at a time, accept short answers, and do not lecture about features.

    line 9
  2. Distinctive:

    Read AGENTS.md. If "About me" is already filled in, ask whether to update it or skip to step 4.

    line 13
  3. Very specific:

    Check whether _examples/ folders still exist.

    line 14
  4. Very specific:

    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).

    line 15
  5. Distinctive:

    Ask, in two or three short rounds:

    line 19
  6. Very specific:

    Add anything they said about tone or phrasing to System/writing-guide.md under "Your additions".

    line 30
  7. Very specific:

    Ask for one current project.

    line 35
  8. Very specific:

    Ask for one person they work with or want to keep in touch with.

    line 36
  9. Very specific:

    Run python3 scripts/check_vault.py and fix anything it reports.

    line 37
  10. Very specific:

    If origin still points at the template repository, explain that pushing there will fail and offer the commands to point it at their own …

    line 42
  11. Very specific:

    Commit with vault: onboarding - personalize AGENTS.md, first notes if they agreed to agent commits.

    line 43

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 status to see whether the vault is a git repo and whether origin still points at the template's repository (git remote -v).

2. Interview

Ask, in two or three short rounds:

  1. Their name, and what they do (role, field, or main focus).
  2. What they want this vault for: projects, research, people, writing, a mix.
  3. How they want answers: length, tone, anything that annoys them in AI writing.
  4. Git: do they want agents to commit? To push? Is the remote private?

3. Write it down

  • Fill in "About me" in AGENTS.md with 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.md under "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.md as Projects/<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>.md from System/Templates/Person.md and link it to the project if they are connected.
  • Run python3 scripts/check_vault.py and fix anything it reports.

5. Clean up and hand over

  • Offer to remove the examples: ./setup.sh --remove-examples (it asks before deleting).
  • If origin still 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 notes if they agreed to agent commits.
  • Finish with three things to try next, picked for what they said they want: /meeting-notes after their next meeting, /inbox-triage once something lands in Inbox/, /weekly-review at the end of the week.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.