investor-update
Skill0 starsChanged 4 months agoMITView on GitHub
Draft concise, honest investor updates from raw notes and metrics. Use when the user wants to write a monthly or quarterly investor update, report progress to investors or advisors, or asks how to communicate with their cap table.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- Nomanriaz786/claude-consulting-teamtheir own version, first seen Nov 1, 2026
- skills-agents-co/skills-and-agents-librarytheir own version, first seen Oct 15, 2026
- mvfernando/founder-sales-skillstheir own version, first seen Sep 30, 2026
- Pitchdrive/investor-update-skilltheir own version, first seen Jul 22, 2026
- Unabyss/unabyss-skillstheir own version, first seen Jul 16, 2026
- getnao/sylphtheir own version, first seen May 19, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- getnao/sylph★ 195same name
- Unabyss/unabyss-skills★ 15same name
- Kotrotsos/claude-skills-non-coding★ 8same name
- Pitchdrive/investor-update-skill★ 4same name
- Nomanriaz786/claude-consulting-team★ 1same name
- skills-agents-co/skills-and-agents-library★ 1same name
- mvfernando/founder-sales-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- cold-outreachSkill
- competitor-scanSkill
- customer-discoverySkill
- hiring-kitSkill
- landing-copySkill
- launch-planSkill
- metrics-reviewSkill
- mvp-cutSkill
- pitch-deck-reviewSkill
- pricing-strategySkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 3 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Write investor updates that busy investors actually read: short, numbers-first, honest about problems, and ending with specific asks.
- Very specific: line 19
If the user cannot supply a number, write [TODO: figure] in its place.
- Distinctive: line 23
Keep the full update under 600 words.
- Distinctive: line 58
No adjectives doing the work of numbers ("massive growth" is banned.
“Common” is measured: kept by at least 6 in 10 of the 7 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Investor Update
Write investor updates that busy investors actually read: short, numbers-first, honest about problems, and ending with specific asks.
Before writing
Collect from the user (ask if missing, never invent):
- Period covered and the previous period's numbers for comparison
- Core metrics: revenue or usage, growth rate, burn, runway in months
- One to three highlights and at least one lowlight
- Specific asks (intros, hiring, feedback)
If the user cannot supply a number, write [TODO: figure] in its place. Never estimate or fabricate a metric.
Structure
Keep the full update under 600 words.
Subject: [Company] Update: [Month Year]
TL;DR: One sentence on the state of the business.
METRICS
- MRR: $X (+Y% vs last month)
- Active users: X (+Y%)
- Burn: $X/mo, Runway: X months
Show the same metrics every update so trends are visible.
HIGHLIGHTS
2-3 bullets. Concrete outcomes, not activity. "Closed 3 pilots"
beats "had many promising conversations."
LOWLIGHTS
1-2 bullets. What went wrong or slower than planned, and what
you are doing about it. Updates without lowlights read as spin.
ASKS
Specific and answerable in one reply. "Intro to a payments PM
at Stripe" beats "any advice welcome."
Thanks for the support.
[Name]Rules
- Numbers before narrative. Investors scan metrics first.
- Same metric set every period. Changing definitions between updates destroys trust.
- Lowlights are mandatory. A founder who reports only wins gets less help.
- One ask per line, each one forwardable as-is.
- No adjectives doing the work of numbers ("massive growth" is banned; "+41% MoM" is not).
- Consistent cadence matters more than polish. Monthly is the default.
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.

