find-revenue-leaks
Skill2 starsChanged 8 months agoMITView on GitHub
Find specific conversion issues that are costing revenue. Provides dollar estimates and implementation priorities.
In this repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- check-integrationsSkill
- check-seoSkill
- compare-sitesSkill
- find-dead-linksSkill
- generate-analytics-specSkill
- growth-auditSkill
- growth-diffSkill
- map-funnelSkill
- suggest-schemaSkill
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 31
Code fix: If applicable, show the exact code to add/change
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
/find-revenue-leaks
Identify the specific conversion issues costing you revenue, with estimated impact and fix priority.
Usage
/find-revenue-leaks <url>Instructions
- Run the scan:
cd /Users/sdm/Desktop/GrowthLint && python3 -c "import growthlint.cli; growthlint.cli.app()" -- scan "$URL" --format json --fix- Focus exclusively on revenue-impacting issues:
- Filter to critical and warning severity violations
- Sort by revenue_weight (highest impact first)
- Group by category
- For each revenue leak, provide:
- What's happening: Describe the issue in plain language a marketer understands
- Revenue impact: Estimate conversion rate impact (e.g., "This likely costs you 5-15% of signups")
- Implementation time: Quick win (< 1 hour), Medium (1 day), Heavy lift (1+ week)
- Code fix: If applicable, show the exact code to add/change
- CRO recommendation: Beyond the code fix, what CRO best practice applies here
- End with a Revenue Recovery Roadmap: "Fix these 3 things this week to recover an estimated X% conversion improvement"
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.

