Investor Update Generator Skill for Claude
> Validate a monthly investor update against a rubric of strong-update sections (transparency, decision-relevance, specific asks). Use before sending a monthly investor update or setting a fundraise communication cadence.
Install
one command, takes just this skill from the repositorynpx skills add https://github.com/borghei/Claude-Skills --skill investor-update-generatorWhat comes with it
14 273 bytes besides the instructionThe instruction itself
12 sections, as written by the authorInvestor Update Generator
Validate a draft monthly investor update against a rubric of what makes them work — and provide a starting template if you don't have one yet.
Keywords
investor update, monthly update, founder update, investor communication, fundraise, lead investor, board, KPIs, asks
Clarify First
Before generating the update, confirm these inputs. If any is unknown or vague, ASK — do not assume:
- [ ] Stage & cadence — early-stage monthly vs later-stage quarterly changes which sections the rubric expects
- [ ] This period's metrics — the same defined set every month; re-defining metrics signals dishonest reporting
- [ ] Specific asks — what you need from investors (intros, hires, advice); the highest-leverage section
- [ ] Bad news / risks — strong updates lead with these, so they must be surfaced, not buried
Stop rule: ask only the 2-3 that most change the output. If the user says "just draft it," proceed and list your assumptions at the top of the artifact.
Quick Start
- Draft your update as
update.md - Run:
python scripts/investor_update_validator.py update.md - Address any missing sections; aim for the rubric score > 80
OR start from scratch with assets/investor_update_template.md.
Core Workflows
Workflow 1: Monthly Update Production
- First of month: pull metrics dashboard, last update, current asks
- Draft against
assets/investor_update_template.md - Validate:
python scripts/investor_update_validator.py update.md - Send within 5 business days of month-end
Time Estimate: 1-2 hours/month.
Workflow 2: Update Cadence Establishment
- Read
references/what_makes_good_updates.md - Decide cadence: monthly is standard for early-stage; quarterly for later-stage
- Pick distribution: investors only, or extended (advisors, helpful operators)
- Commit publicly — once you start, don't skip months
Time Estimate: 1 week to set up; recurring monthly thereafter.
Tools
investor_update_validator.py
Scans an update markdown file for the structural sections of a strong update and scores it.
python scripts/investor_update_validator.py update.md
python scripts/investor_update_validator.py update.md --json
Reference Guides
references/what_makes_good_updates.md— What separates good investor updates from bad
Templates
assets/investor_update_template.md— Monthly update template
Best Practices
- Send the bad news first. Investors notice when they only hear the good.
- Asks specific. "Help with sales" is too vague; "Intros to VPs of Engineering at SaaS companies 100-1000 employees in NA" is actionable.
- Cadence > perfection. A consistent OK update beats a perfect annual one.
- Same metrics every month. Defining and re-defining metrics signals dishonest reporting.
- One page (or one screen). Past two screens, attention drops.
Other skills for the same job
different authors, same section of the catalogue
Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.
Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.
Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.
Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
How to use it
Take borghei/investor-update-generator from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.