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 whawkinsiv/solo-founder-skills --skill conversiongit clone --depth 1 https://github.com/whawkinsiv/solo-founder-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/whawkinsiv/solo-founder-skills/conversion)<a href="https://agentmods.dev/skills/whawkinsiv/solo-founder-skills/conversion"><img src="https://agentmods.dev/badge/skills/whawkinsiv/solo-founder-skills/conversion/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/whawkinsiv/solo-founder-skills/conversion"><img src="https://agentmods.dev/badge/skills/whawkinsiv/solo-founder-skills/conversion.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
SkillSpector: 1 finding, up to low
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- low Privilege Escalation · line 99 Skill requests more permissions than appear necessary for its stated functionality. Review if elevated access is justified.Fix: Request only the minimum permissions required. Document why each permission is needed. Remove broad permissions like '*' or 'all'.
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.00049 | $0.01892 |
| Opus 5 | $0.00024 | $0.00946 |
| Sonnet 5 | $0.00010 | $0.00378 |
| Haiku 4.5 | $0.00005 | $0.00189 |
Grade A, and why
conversion 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 — 221 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Conversion Rate Optimization
Every page has one job. If you can't name it, the page is broken. This skill helps you find where users drop off and fix it.
Core Principles
- Friction is the enemy. Every field, click, and decision point costs conversions.
- Don't guess — measure. But don't measure everything — measure what drives revenue.
- Social proof is the most underused conversion lever in SaaS.
- Speed is a feature. Every 100ms of load time costs ~1% conversion.
- The best optimization is often removal, not addition.
Finding Your Biggest Bottleneck
Before optimizing, find where users actually drop off.
Step 1: Map Your Funnel
Typical SaaS funnel:
Landing page visit → Signup page viewed → Account created →
Onboarding started → Key action completed → Returned next week →
Upgrade page viewed → Subscription created
Step 2: Measure Drop-Off
Tell AI:
Analyze our conversion funnel:
- Pull the number of users at each step: [list your funnel steps]
- Calculate the drop-off % between each step
- Identify the step with the biggest drop-off — that's our priority
- Show results in a table: Step | Users | Drop-off %
If you don't have analytics yet: Set them up first (see analytics-instrumentation skill). In the meantime, track manually: count signups, count activations, count paying customers. Even rough numbers reveal the biggest leak.
Step 3: Diagnose Why
For the biggest drop-off, evaluate the page/flow using this framework:
- CLARITY: Does the user know what to do and why?
- MOTIVATION: Is the value of completing this step obvious?
- FRICTION: What's making this harder than it needs to be?
- ANXIETY: What fears or objections might stall the user?
- DISTRACTION: What elements compete with the primary action?
Signup & Registration
- Minimize fields. Email + password is ideal. Email-only or SSO is even better.
- Defer everything else to onboarding (company name, role, team size).
- Show password requirements before the user types, not after they fail.
- Social login (Google, GitHub) should be visually prominent if your audience uses them.
- Post-signup, go DIRECTLY to value — not a "check your email" dead end.
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 · 221 lines · 49 tokens per session scan A 296bded3ee50
conversion is a skill published in the GitHub repository whawkinsiv/solo-founder-skills (243 stars, last pushed 15d ago), licensed MIT. It adds 49 tokens to every session and 1,892 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…