product-onboarding
Skill0 starsChanged 3 months agoMITView on GitHub
Use when building, designing, or reviewing anything a real user signs up for and uses. Triggers on onboarding flows, sign-up, activation, first-run experience, permissions requests, retention mechanics, monetization, paywalls, or any consumer or operator-facing product surface.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- SkeneTechnologies/plg-skillstheir own version, first seen Jan 26, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- SkeneTechnologies/plg-skills★ 19same 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 repository5 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- llm-actionsSkill
- product-specSkill
- research-swarmSkill
- ship-gateSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
WHEN building anything a real user signs up for and uses:
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
product-onboarding
WHEN building anything a real user signs up for and uses:
- Hold the whole funnel, not just features: acquisition, then activation (first run to the aha moment), then retention (education plus habit), then monetization. Name where the build sits and what is missing.
- Drive first run to first real value on the shortest reliable path: motivate, request only the permissions actually needed (show the real OS screens and deep-link them), low-friction sign-up, one personalization step (the investment effect), then a no-skip first use. Gate the product on setup completion, do not dump the user at a blank app.
- Teach continuously and lightly (contextual tips, progressive disclosure). Prove value before asking for payment. Personalize by reflecting the user's own choices back.
- Identity and data: passwordless by default, minimal cloud footprint, on-device data stays on device. Scope multi-tenant data to the user with row-level rules, never by modifying a managed auth or system schema.
Skill updated: 2026-06-09
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.