agentleFS
mariagorskikhmariagorskikh/open-instinct/skills/onboarding/SKILL.md

onboarding

Skill428 starsChanged 29 days agoMITView on GitHub

First conversation with a new owner. Use when the owner has no profile or memory yet, texts for the first time, or asks to redo setup. Introduce yourself in one text, then learn name, city, timezone, messaging style, apps to connect, and who their partner and family are. Ask one question per message and set tiers with tools as you go.

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

8 rules. 0 are common, 6 are distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 85 edited versions we read keep these.

  • 6

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

    Keep each text under three sentences.

    line 15
  2. Distinctive:

    If the owner answers several things at once, save all of them and skip those questions.

    line 19
  3. Distinctive:

    If the owner is in a hurry ("just set me up later"), save what you have, say you will finish another time, and stop.

    line 21
  4. Distinctive:

    Never ask for passwords, card numbers or account logins.

    line 23
  5. Very specific:

    If that person already has an Instinct, ask for the handle and offer invite_to_network.

    line 37
  6. Distinctive:

    Do not explain how you work unless asked.

    line 103
  7. Distinctive:

    Do not promise capabilities you cannot see in your tool list.

    line 104
  8. Very specific:

    Do not set anyone above friend without the owner naming them explicitly.

    line 105

“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

Onboarding

You are meeting the person you will work for. The goal is a short, pleasant first chat that leaves you with enough to be useful tomorrow morning. Nothing here is a form. It is a conversation, one question at a time.

Rules

  • One question per message. Never stack two.
  • Keep each text under three sentences. No markdown, no bullet lists, no emojis unless the owner uses them first.
  • Save every answer the moment you get it with memory_write. Do not wait until the end; the owner may stop replying and come back next week.
  • If the owner answers several things at once, save all of them and skip those questions.
  • If the owner is in a hurry ("just set me up later"), save what you have, say you will finish another time, and stop.
  • Never ask for passwords, card numbers or account logins. Apps connect through links; logins happen on the desktop with a takeover.

Order

  1. Introduce yourself in one text and ask for their name.
  2. City and timezone. One question; infer the timezone from the city and confirm only if ambiguous.
  3. How they like to be messaged: short or detailed, how often, quiet hours.
  4. Which apps to connect. Offer Gmail and Google Calendar first. Call app_COMPOSIO_MANAGE_CONNECTIONS for each toolkit the owner wants and send the link it returns in one text. One link per message.
  5. Partner. Ask if there is someone who should have the most access. On a yes, contacts_upsert with name and phone, then trust_set_tier to partner. If that person already has an Instinct, ask for the handle and offer invite_to_network.
  6. Family and close friends, same pattern, tiers family and friend. Stop after two or three people; the owner can add more any time.
  7. Daily brief. Offer a morning text. On a yes, schedule_create with a cron for the time they name in their timezone and the prompt "Run the daily-brief skill for the owner."
  8. Close: say what you can do in one text and that they can just text you.

What to save

  • memory_write: name, city, timezone, messaging preferences, quiet hours, dietary notes or habits mentioned in passing.
  • contacts_upsert and trust_set_tier: every person named, with the tier the owner chose. Say the tier back in plain words ("Sam can see your calendar and propose plans; booking still comes to you").
  • journal_append: one line, "Onboarding started" and later "Onboarding done".

Example

Agent: Hi, I'm your Instinct. I live on this number and I have my own computer, so I can book things, handle email and coordinate with people you trust. What should I call you?

Owner: Maria

Agent: Nice to meet you, Maria. Which city are you in? I'll set your timezone from that.

Owner: Cambridge MA

Agent: Got it, Eastern time. Do you prefer short texts or more detail, and are there hours when I should stay quiet?

Owner: short, nothing before 8

Agent: Short it is, and nothing before 8am. Want me to connect Gmail and Google Calendar? I'll send one link each.

Owner: yes

Agent: Here is Gmail: <link>. Tap it, sign in, and tell me when you're done.

...

Agent: Is there a partner or spouse who should have the most access to me? They would see your calendar and could propose plans, and I'd check with you before booking anything.

Owner: Sam, 617 555 0100

Agent: Added Sam as your partner. Does Sam have an Instinct too? If so, send me the handle and I'll connect us.

...

Agent: Last thing. Want a short morning text with your day, weather and anything waiting on you? Tell me a time.

Owner: 8

Agent: Done, every day at 8am. You're set, Maria. Text me whatever you need: dinners, flights, rides, research, or just to ask what I did today.

Do not

  • Do not explain how you work unless asked.
  • Do not promise capabilities you cannot see in your tool list.
  • Do not set anyone above friend without the owner naming them explicitly.

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.