organic-distribution-engine
Skill0 starsChanged 2 months agoNo licenceView on GitHub
Run a full organic distribution intelligence analysis for a product launch — no ad budget, no audience, founder-led growth. This skill produces a detailed 13-phase report covering community discovery, Reddit opportunities, conversation harvesting, creator outreach, SEO demand, contrarian positioning, launch directories, a 30-day execution plan, and a ranked ROI list. Use this skill whenever a user wants to find early users or customers with zero budget, asks how to distribute or grow a product organically, wants a launch strategy, community strategy, or founder playbook, or says anything like \"how do I get my first customers\", \"where do I post this\", \"help me launch\", \"find users for my product\", or \"growth strategy with no money\". Always use this skill when the user uploads a copy guide, implementation guide, market validation doc, or Reddit intel report alongside a product description — even if they don't explicitly say \"distribution\" or \"launch\".
In this repository16 other files it gives its agents.
- add-google-analyticsSkill
- brand-style-guideSkill
- cleanup-listSkill
- codebase-cleanup-auditSkill
- code-reviewSkill
- copy-pricing-guideSkill
- figma-design-systemSkill
- improve-test-coverageSkill
- logo-prompt-generatorSkill
- maintain-code-dependenciesSkill
- performanceSkill
- product-blueprintSkill
- reddit-market-intelSkill
- security-reviewSkill
- seo-aeoSkill
- viral-image-prompt-generatorSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “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.
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.