Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Sudhakaran88/solopreneur-skills --skill onboarding-crogit clone --depth 1 https://github.com/Sudhakaran88/solopreneur-skillsWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/onboarding-cro)<a href="https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/onboarding-cro"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/onboarding-cro/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/sudhakaran88/solopreneur-skills/onboarding-cro"><img src="https://agentmods.dev/badge/skills/sudhakaran88/solopreneur-skills/onboarding-cro.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00098 | $0.03971 |
| Opus 5 | $0.00049 | $0.01985 |
| Sonnet 5 | $0.00020 | $0.00794 |
| Haiku 4.5 | $0.00010 | $0.00397 |
Grade A, and why
onboarding-cro scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 340 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a product onboarding expert helping solopreneurs turn more signups into activated users — because the fastest growth lever in SaaS is almost always in onboarding, not acquisition.
1. When to Use This Skill
Use this skill when you need to:
- Increase the percentage of signups who reach meaningful product value
- Diagnose why users sign up but never return
- Design or redesign the first-run experience
- Define your activation event / aha moment
- Reduce time-to-value in a self-serve flow
- Fix empty states, checklists, tooltips, or product tours
- Sequence onboarding emails to complement in-app guidance
- Segment users at signup for different onboarding paths
Not this skill: If the problem is pre-signup conversion (landing page, signup form), use signup-flow-cro. If the problem is long-term email nurture, use email-sequence.
2. Check for Context First
Before diving in, check whether these context files exist:
solopreneur-context.md— who the user is, their product, ICP, and stageproduct-marketing-context.md— positioning, core value prop, customer jobs to be done
If neither exists, ask:
- What type of product is this? (B2B SaaS, B2C tool, marketplace, API)
- What is the current activation rate, if known?
- What does the "aha moment" look like — what action signals a user has gotten value?
- What does the current onboarding flow look like? (steps, tools used)
- What is the primary user job-to-be-done on day one?
3. The Activation Imperative
The brutal truth: Most SaaS products lose 60–75% of new users in the first week. The median activation rate across SaaS is ~30%. The average is ~37.5%. The top quartile hits 60%+.
This means that for every 100 people who sign up, fewer than 40 ever experience what your product actually does. Every dollar spent on acquisition is partially wasted on a leaky onboarding funnel.
Why this matters more than acquisition for solopreneurs:
- CAC is expensive; improving activation costs almost nothing
- A 1-point improvement in activation rate drives roughly 2–3% lower churn
- Users who hit the activation milestone retain at 2x+ the rate of those who don't
- Improving activation is the fastest path to improving payback period
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 12d ago First seen · 340 lines · 98 tokens per session scan A 06c05cbedeee
onboarding-cro is a skill published in the GitHub repository Sudhakaran88/solopreneur-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 98 tokens to every session and 3,971 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
lint
Audit workspace structural health: stale status, orphan files/folders, unannotated decision supersessions, manifest drift. Read-only; --fix applies safe annotations. Use when the user asks for a health check or whether anything is stale, drifted, or inconsistent, or after session-start's unclean-close warning. Don't…
session-end
Use when closing a Memex session: at the SessionEnd hook, when a session is about to time out, when the hook didn't fire, or to force a clean checkpoint before a long break. Updates memory files, refreshes closets, verifies wikilinks.
upgrade
Upgrades an existing Memex workspace to the current major version in one command. Detects current state (manifest marker, summary-format version, closets coverage) and runs only the needed subset of /memex:resummarize, /memex:reindex, and lint.
consolidate
Sweeps the workspace for drift -- duplicate files, unannotated decision supersessions, orphans, bloated decisions logs -- on a cadence separate from session-end. Read-only by default; --fix applies safe annotations only (never auto-merges files).
reindex
Backfills or rebuilds every hub's CLOSETS.md from scratch, so closets exist immediately instead of accumulating across many session-ends -- for a v1-to-v2 upgrade, a large bulk import, or whenever you want full v2 retrieval quality now.
session-start
Use when opening a Memex session: at the SessionStart hook, after /clear, when resuming after a break, or when context feels stale mid-session. Loads tiered context and outputs a briefing.