agentleFS
Sign inStart free
schub-techschub-tech/llm-ideation-wiki/.agents/skills/onboarding/SKILL.md

onboarding

Skill11 starsChanged 31 days agoMITView on GitHub

Set up a new Notion-backed LLM Ideation Wiki from a fresh clone. Use when the user asks to get started, onboard, initialize the wiki, or connect a Notion root page.

  • Pipes a download into a shell

100 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 19 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 18 projects that use this

  • coreyhaines31Skill

    marketing-council

    When the user wants multiple expert perspectives on a marketing question — a simulated board of advisors staffed by legendary marketers (Seth Godin, David Ogilvy, Eugene Schwartz, April Dunford, Rory Sutherland, Alex Hormozi, Byron Sharp, and more). Also use when the user mentions 'marketing council,' 'board of advisors,' 'advisory board,' 'what would Seth Godin say,' 'what would Ogilvy think,' 'channel Hormozi,' 'get multiple perspectives,' 'debate this,' 'have the council review,' 'marketing mentors,' or asks how a famous marketer would approach their problem. The council gives each advisor's take through their documented frameworks, surfaces where they disagree, and synthesizes a recommendation. For executing the winning direction, hand off to positioning, offers, copywriting, ads, or 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 16 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 18 projects that use this

  • +7 more from Cesarjoquin

The file

We split this skill into the rules it gives an agent

12 rules. 0 are common, 3 are distinctive, and 9 are very specific to this project.

  • 0

    Common

    Most of the 85 edited versions we read keep these.

  • 3

    Distinctive

    This author's own choices. Worth a look.

  • 9

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If the user has not already provided it, ask for the Notion page URL to use as the wiki root.

    line 10
  2. Distinctive:

    Do not proceed until you have the root page URL.

    line 12
  3. Very specific:

    Fetch vendored skills: Run scripts/check_agent_symlinks.py.

    line 14
  4. Very specific:

    Read README.md, AGENTS.md, docs/agent/notion-contract.md, and notion.config.json if it exists.

    line 18
  5. Very specific:

    Check whether ntn exists with command -v ntn or ntn --version.

    line 19
  6. Very specific:

    If ntn is missing, tell the user the Notion CLI is required.

    line 20
  7. Very specific:

    If the CLI is not authenticated, run ntn login.

    line 22
  8. Very specific:

    If the environment is headless and ntn login prints a URL and poll command, show the URL/code to the user, then run the printed poll …

    line 23
  9. Very specific:

    Run scripts/notion_wiki.py seed --refresh-existing to create Raw, Shared, Wiki, and Templates.

    line 28
  10. Very specific:

    Run the ritual (AGENTS.md § Mechanics), plus scripts/notion_wiki.py ls.

    line 32
  11. Distinctive:

    Do not create idea pages during onboarding.

    line 37
  12. Very specific:

    If the root page title or icon cannot be read, default to LLM Wiki and 🧠.

    line 38

“Common” is measured: kept by at least 6 in 10 of the 85 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

Set up the repo as a Notion-backed idea wiki. Do infrastructure only; do not create ideas.

Ask first.

If the user has not already provided it, ask for the Notion page URL to use as the wiki root.

Do not proceed until you have the root page URL.

Fetch vendored skills. Run scripts/check_agent_symlinks.py. If it reports a missing submodule, run git submodule update --init and re-run the check.

Set up Notion.

  1. Read README.md, AGENTS.md, docs/agent/notion-contract.md, and notion.config.json if it exists.
  2. Check whether ntn exists with command -v ntn or ntn --version.
  3. If ntn is missing, tell the user the Notion CLI is required. Ask before installing external software, then install with the official command curl -fsSL https://ntn.dev | bash when approved.
  4. Run ntn doctor.
  5. If the CLI is not authenticated, run ntn login. This should open the user's browser; ask the user to complete the browser approval and confirm the verification code.
  6. If the environment is headless and ntn login prints a URL and poll command, show the URL/code to the user, then run the printed poll command after they approve in the browser.
  7. Re-run ntn doctor after login.
  8. Extract the page ID from the Notion URL and store it as the compact ID in notion.config.json.
  9. For a new wiki root, reset pages in notion.config.json before seeding so old page IDs are not reused.
  10. Set mode to notion-cli, keep version: 1, and store root_url, root_page_id, root_title, and root_emoji.
  11. Run scripts/notion_wiki.py seed --refresh-existing to create Raw, Shared, Wiki, and Templates.

Finish.

  1. Run the ritual (AGENTS.md § Mechanics), plus scripts/notion_wiki.py ls.
  2. Tell the user setup is complete and the next step is /founder-profile. After that, use /new-idea to create the first idea.

Rules.

  • Do not create idea pages during onboarding.
  • If the root page title or icon cannot be read, default to LLM Wiki and 🧠.
  • The agent can start browser login, but the user must approve Notion access themselves.

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.

Check your setup, free