startup-white-paper
Skill3 starsChanged 7 months agoNo licenceView on GitHub
Write authoritative white papers for startups — the kind that make investors lean forward, enterprise buyers circulate internally, and founders look like the domain expert they are. Produces structured, research-backed documents that build a case from first principles: defining the problem, analysing why existing solutions fail, presenting the startup's approach as the logical answer, and grounding everything in market evidence and technical depth. Use this skill whenever the user wants to write a white paper, produce a thought leadership document, create a market thesis paper, write a technical white paper, build an investor-facing research document, draft a solution brief, or mentions "white paper", "thought leadership", "market thesis", "position paper", "technical brief", "solution paper", "industry report", or wants to turn startup analysis into a persuasive, outward-facing document. Also trigger when the user says "write something that makes us look credible", "we need a document for enterprise buyers", "help me establish authority in our space", or wants a long-form document that positions their startup.
In this repository14 other files it gives its agents.
- agent-report-annotationSkill
- architecture-patternsSkill
- dignified-pythonSkill
- find-skillsSkill
- notion-second-brainSkill
- optimal-learningSkill
- python-testing-patternsSkill
- refactorSkill
- research-paper-analysisSkill
- skill-creatorSkill
- startup-evaluatorSkill
- tddSkill
- typescript-standardsSkill
- web-ui-designSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
22 rules. About 0 are common, 21 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈21
Distinctive · estimate
This author's own choices. Worth a look.
1
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.