onboarding
Skill293 starsChanged 11 days agoMITView on GitHub
Use for /onboarding, or when a new member's onboarding is incomplete — runs the resumable VERIFY, ORIENT, INVITE, FIRST_HANDOFF welcome flow through Egregore Runtime.
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 19 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 18 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 16 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 18 projects that use this
- +7 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 repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- activitySkill
- announceSkill
- archiveSkill
- branchSkill
- checkupSkill
- commitSkill
- contributeSkill
- create-skillSkill
- dark-modeSkill
- dashboardSkill
- deep-reflectSkill
- delete-userSkill
- emissarySkill
- envSkill
- handoffSkill
- harvestSkill
- ingest-corpusSkill
- ingest-notionSkill
- ingestSkill
- ingest-user-interviewSkill
- inviteSkill
- issueSkill
- meetingSkill
- meSkill
- noteSkill
- notion-connectSkill
- prSkill
- pullSkill
- pushSkill
- questSkill
- recordsSkill
- reflectSkill
- review-prSkill
- saveSkill
- slack-connectSkill
- summonSkill
- sync-reposSkill
- telegram-connectSkill
- telemetrySkill
- testSkill
- the-spiralSkill
- tui-designSkill
- tutorialSkill
- updateSkill
- viewSkill
- visual-explainSkill
- wrapSkill
- preview-designSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. 0 are common, 8 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 90 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 19
Use for /onboarding, or when a new member's onboarding is incomplete — runs the resumable VERIFY, ORIENT, INVITE, FIRST_HANDOFF welcome …
- Distinctive: line 23
Run one bounded status command and suppress raw output:
- Distinctive: line 33
Read the fields for the flow below from the saved receipt:
- Very specific: line 39
Use each printed field as its correspondingly named placeholder, such as {phase}.
- Distinctive: line 56
VERIFY is otherwise invisible.
- Distinctive: line 83
Ask what they should be called, offering their returned provider display name and a free-form alternative.
- Very specific: line 87
Use {chosen-name} for the name the user chose, writing any single quote inside the name as '\''.
- Very specific: line 94
Do not continue unless the receipt returns the chosen display_name.
- Distinctive: line 123
When they request project changes, use the ordinary branch skill and show the configured integration branch and actual working branch.
- Distinctive: line 126
Do not implement branch mechanics here.
- Very specific: line 134
Only a receipt with complete: true unlocks normal work.
- Distinctive: line 147
Run the ordinary handoff skill.
- Distinctive: line 176
Never ask more than one progressive profile question in a later session.
“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
Egregore onboarding
Welcome a new member through the deterministic VERIFY → ORIENT → INVITE → FIRST_HANDOFF flow. This is a conversation, not setup narration.
The Runtime adapter owns state migration, ActorContext authorization, Local/Connected detection, profile-witness verification, and identity reconciliation. AccountIdentity, ActorIdentity, and OrgMembership remain separate; GitHub fields are linked-provider aliases only. Never edit state or people files, call APIs/graph, or run Git from this skill.
When to invoke
Use for /onboarding, or when a new member's onboarding is incomplete — runs the resumable VERIFY, ORIENT, INVITE, FIRST_HANDOFF welcome flow through Egregore Runtime.
Start or resume
Run one bounded status command and suppress raw output:
mkdir -p tmpbash bin/onboarding.sh status > tmp/onboarding-status.jsonRead the fields for the flow below from the saved receipt:
jq -r '{phase, complete, usage_type, display_name, member_role, profile_fields_collected, installer_captured, invite_handled_by, profile_witness, ready, blockers} | to_entries[] | "\(.key): \(.value)"' tmp/onboarding-status.jsonUse each printed field as its correspondingly named placeholder, such as
{phase}; quote placeholders in single quotes when you use them in a command,
and write any single quote inside a value as '\''.
The receipt reports the phase, completion state, user type, collected fields,
installer handoff, and canonical profile witness. It also migrates legacy
phase names safely. Do not inspect .egregore-state.json yourself.
- Complete with both
nameandrolecollected: say, "You're already set up. What are you working on?" and stop. - Complete with role missing: ask only their role, run
bash bin/onboarding.sh set-role "$ROLE", then ask what they are working on. - Installer-captured name: do not ask for it again.
- Invite handled by installer: do not offer another invite.
- Returning creator in
invite: explain that their previous work should be captured, then enter FIRST_HANDOFF.
VERIFY is otherwise invisible. Adapter failures are rendered as one useful fix (GitHub authentication, missing Connected authentication, or missing memory), without exposing configuration fields or infrastructure details.
ORIENT
Output exactly, with no preamble:
✱ Insight ────────────────────────────────────────
Every session leaves traces — decisions, patterns, context.
Egregore makes those traces persistent and shared.
You do your work. When you're done, you hand off what you
learned. The next session — yours or someone else's — starts
smarter.
──────────────────────────────────────────────────Then:
It works best with someone on the other end.Ask what they should be called, offering their returned provider display name and a free-form alternative. Validate through the Runtime command, not in skill-side state:
Use {chosen-name} for the name the user chose, writing any single quote
inside the name as '\''.
bash bin/onboarding.sh set-name '{chosen-name}'Do not continue unless the receipt returns the chosen display_name.
INVITE
The status receipt's usage_type is authoritative:
founder_group: unless the installer handled it, ask whether to invite someone now or work solo. For a username, invoke theinviteskill, then runbash bin/onboarding.sh record-invite invited. On skip, runbash bin/onboarding.sh record-invite skipped. Invite failure never blocks onboarding; record the answer and continue.joiner_group: never offer the invite question. Runbash bin/onboarding.sh record-invite skippedand use the joiner fast-track completion below.
Teach only:
Two things to know when you're done:
/save — pushes your branch and opens a PR
/handoff — captures what you learned for next timeThen ask:
What are you working on?When they request project changes, use the ordinary branch skill and show the configured integration branch and actual working branch. Read-only questions and memory lookups stay in the current workspace and use Runtime retrieval. Do not implement branch mechanics here.
For a joiner, complete immediately after their intent answer:
bash bin/onboarding.sh completeOnly a receipt with complete: true unlocks normal work.
FIRST_HANDOFF — creators only
Trigger when a creator clearly ends the session, runs save/wrap/handoff, or
returns in the invite phase. If "done" could mean a subtask, ask which.
Say:
Before you close out — this is the part that makes the system work. A handoff captures what you did so the organization remembers it. Not a summary for a manager — a briefing for the next session, or the next person.
Run the ordinary handoff skill. After it succeeds, complete onboarding once:
bash bin/onboarding.sh completeThe adapter upgrades an invite stub through the identity service, verifies the canonical profile witness, records canonical Git provenance, and only then sets completion. If the witness is absent, keep the phase resumable and say: "Almost done, but your profile didn't save. Try /handoff again next session."
For creators who skipped inviting, add:
This is what someone would see if you invited them —
your handoff in /activity, ready to pick up. Run /invite
anytime to bring someone in.On success say: "You're in." Add the launcher alias only if the Runtime receipt returns one; do not mutate shell configuration from the skill.
Rules
- Joiners never pass through FIRST_HANDOFF and are never prompted to recruit.
- Creators prove the handoff loop before completion.
- Local onboarding performs no graph, API, notification, or hosted-service work. Connected reconciliation remains behind the identity adapter.
- Inviting and notifying are separately authorized and separately consented.
- Never ask more than one progressive profile question in a later session.
- Raw command JSON is internal; render the user-facing flow above.
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.

