user-onboarding
Skill1 starsChanged 8 months agoMITView on GitHub
Help users design effective product onboarding. Use when someone is creating first-user experiences, trying to improve activation rates, designing the first 30 seconds of product usage, or working on the path to the aha moment.
9 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- itsryanarmani/skillstheir own version, first seen Nov 8, 2026
- pooriaarab/skillstheir own version, first seen Nov 7, 2026
- juandelossantos/another-agent-skillstheir own version, first seen Oct 17, 2026
- TGPSKI/flow-indicatortheir own version, first seen Sep 4, 2026
- 2867203296/hermes-agenttheir own version, first seen Aug 19, 2026
- Bappoz/My-Claude-Skillstheir own version, first seen Jul 15, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- CodeAlive-AI/ceo-ai-os★ 996% same
Wrote their own version · 8
- Starchild-ai-agent/official-skills★ 32same name
- Bappoz/My-Claude-Skills★ 1same name
- certivpaul/claude-skills★ 1same name
- itsryanarmani/skills★ 1same name
- juandelossantos/another-agent-skills★ 1same name
- pooriaarab/skills★ 1same name
- TGPSKI/flow-indicator★ 1same name
- 2867203296/hermes-agent★ 0same name
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 repository47 other files it gives its agents.
- anti-pattern-auditSkill
- brand-storytellingSkill
- business-investigationSkill
- ceo-weekly-reviewSkill
- cold-emailSkill
- community-buildingSkill
- competitive-analysisSkill
- conducting-user-interviewsSkill
- content-strategySkill
- copywritingSkill
- daily-recapSkill
- decision-playbookSkill
- designing-growth-loopsSkill
- discovery-debriefSkill
- email-sequenceSkill
- enterprise-salesSkill
- exa-code-searchSkill
- exa-company-researchSkill
- exa-lead-genSkill
- exa-people-researchSkill
- exa-personal-siteSkill
- exa-x-searchSkill
- founder-salesSkill
- fpf-problem-solvingSkill
- humanizerSkill
- hypothesis-trackerSkill
- idea-generatorSkill
- launch-marketingSkill
- measuring-product-market-fitSkill
- metrics-briefingSkill
- ph-launch-timelineSkill
- positioning-messagingSkill
- posthog-analyticsSkill
- pricing-strategySkill
- problem-definitionSkill
- product-hunt-launchSkill
- product-led-salesSkill
- product-marketing-contextSkill
- programmatic-seoSkill
- prompt-engeneeringSkill
- sales-qualificationSkill
- seo-auditSkill
- social-writerSkill
- strategic-reviewSkill
- structured-logSkill
- web-browserSkill
- writing-north-star-metricsSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 7
Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.
- Distinctive: line 9
Follow output preferences from USER.md (language, format, platform constraints).
- Distinctive: line 17
When the user asks for help with user onboarding:
- Distinctive: line 19
Understand the aha moment: - Ask what the key value moment is and how quickly users need to reach it
- Distinctive: line 21
Apply game design principles: - Use progressive disclosure and reward mechanics from game design
- Distinctive: line 22
Connect to retention: - Ensure the onboarding inflects the early user experience toward long-term engagement
- Distinctive: line 53
Delaying the aha moment: - Every screen between signup and value is a potential dropoff point
“Common” is measured: kept by at least 6 in 10 of the 7 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
Company Context
Before helping, read MEMORY.md for: current wedge, ICP, competitors, PMF stage, system constraint.
Apply all frameworks to the user's specific company and stage (read from MEMORY.md).
Follow output preferences from USER.md (language, format, platform constraints).
User Onboarding
Help the user design effective product onboarding using frameworks and insights from 4 product leaders.
How to Help
When the user asks for help with user onboarding:
- Understand the aha moment - Ask what the key value moment is and how quickly users need to reach it
- Design the first 30 seconds - Focus intensely on what happens immediately after signup
- Apply game design principles - Use progressive disclosure and reward mechanics from game design
- Connect to retention - Ensure the onboarding inflects the early user experience toward long-term engagement
Core Principles
Make the first 30 seconds magical
Grant Lee: "We are going to do everything we possibly can to make the first 30 seconds of the product feel magical." The first moments of the user experience are the primary driver for word-of-mouth growth. Invest disproportionately here.
Retention wins come from early experience
Dan Hockenmaier: "Very often I think the biggest wins in retention come from inflecting the early user experience." The onboarding experience is the biggest lever for long-term retention, not just initial activation.
Design from onboarding outward
Merci Grace: "I would design the game from the onboarding experience." Use game design principles where onboarding isn't an afterthought but the foundation from which the rest of the product is built.
Remove blockers to the aha moment
Cam Adams: "We worked a lot on the onboarding process in the last couple of months of launch and that was really pivotal because the product features were there but there was this thing holding people back." Product features may be complete, but invisible friction can prevent users from experiencing them.
Avoid common onboarding anti-patterns
Skip carousels, non-native frameworks, and explanatory screens that don't provide value. Get users into the core product experience as quickly as possible.
Questions to Help Users
- "What is the single moment where users first experience the core value of your product?"
- "What happens in the first 30 seconds after a user signs up?"
- "What friction is between signup and the aha moment, and can any of it be removed?"
- "Have you watched real users go through onboarding and seen where they struggle?"
- "How quickly can a user do something meaningful, not just view something?"
- "What would the onboarding look like if designed like a game tutorial?"
Common Mistakes to Flag
- Explanation screens instead of action - Users learn by doing, not by reading about doing
- Delaying the aha moment - Every screen between signup and value is a potential dropoff point
- Carousels and tooltips - These patterns often indicate the product itself isn't intuitive enough
- Treating onboarding as separate - Onboarding should be designed as part of the core product, not bolted on
- Ignoring the first 30 seconds - This is where most users decide whether to invest further
Deep Dive
For all 4 insights from 4 guests, see references/guest-insights.md
Related Skills
- Measuring Product-Market Fit
- Designing Growth Loops
- Retention & Engagement
- Usability Testing
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.

