Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
onewave-ai avatar

Investor Update Writer

  • 160 installs
  • 237 repo stars
  • Updated July 15, 2026
  • onewave-ai/claude-skills

Draft periodic investor updates with metrics, milestones, risks, and asks formatted for email newsletters or stakeholder decks.

About

Produces polished investor update drafts combining key metrics, milestone recaps, risk disclosures, and funding asks into email- or deck-ready formats for recurring stakeholder lifecycle communications.

  • Metrics narrative
  • Milestone recap
  • Risk disclosure
  • Funding asks
  • Stakeholder formatting

Investor Update Writer by the numbers

  • 160 all-time installs (skills.sh)
  • +4 installs in the week ending Aug 4, 2026 (Skillselion tracking)
  • Ranked #280 of 688 Office & Documents skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
npx skills add https://github.com/onewave-ai/claude-skills --skill investor-update-writer

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs160
repo stars237
Last updatedJuly 15, 2026
Repositoryonewave-ai/claude-skills

What it does

Draft periodic investor updates with metrics, milestones, risks, and asks formatted for email newsletters or stakeholder decks.

Files

SKILL.mdMarkdownGitHub ↗

Investor Update Writer

Generate professional, honest, data-driven investor updates that keep investors informed and ready to help, with tone calibrated from seed-stage transparency to growth-stage formality.

Contents

  • references/output-template.md -- full investor-update.md structure to produce
  • references/tone-and-cadence.md -- voice by stage; monthly vs quarterly depth
  • references/industry-metrics.md -- which metrics to emphasize by business model
  • references/sensitive-situations.md -- handling misses, departures, pivots, down rounds; mistakes to avoid
  • references/examples.md -- worked request-to-approach examples

Workflow

1. Gather inputs. Collect or confirm: company basics (name, period, stage, industry); KPIs (revenue/MRR/ARR current and prior, burn, runway, customer count, growth rate, domain metrics); milestones and wins; challenges and learnings; financial summary (cash, revenue breakdown, expenses, fundraising status); upcoming milestones; and asks. Optional inputs include team changes, customer stories, competitive shifts, roadmap, cohort/retention data, and pipeline. Work with whatever is available and note gaps.

2. Calibrate tone and cadence. Select the voice for the company's stage and the depth for monthly vs quarterly. See references/tone-and-cadence.md. Honor any explicit tone request.

3. Select industry emphasis. Choose the metrics that matter for the business model. See references/industry-metrics.md.

4. Draft against the template. Produce investor-update.md following references/output-template.md. Add the date or period to the filename if the user prefers. Omit sections with no material content.

5. Apply the writing principles. Lead with the headline. Be honest about challenges and frame them with a response plan. Use numbers, not adjectives. Make it scannable with headers, bold, tables, and bullets. End with specific, actionable asks. Keep the format consistent period over period. Respect reader time (3-5 min monthly, deeper quarterly). Show trajectory with period-over-period comparisons. Use no emojis. Connect every metric to what it means for the business.

6. Handle sensitive content. For missed targets, departures, pivots, down rounds, or fundraising, follow references/sensitive-situations.md.

7. Integrate data sources. Given files or connected tools, extract and format automatically: parse CSV/spreadsheets for KPIs and trends; read prior updates for format consistency and period-over-period deltas; pull cash/burn/revenue/expenses from financial documents; pull pipeline, customer counts, deal values, and churn from CRM exports; incorporate usage, activation, and adoption from product analytics. Cross-reference extracted data with user-provided inputs and flag discrepancies.

8. Run the quality checklist. Confirm before delivering:

  • TL;DR present, covering the 3-5 most important items
  • Every KPI shows current and prior values with percentage change
  • At least one challenge or learning described honestly
  • Financial summary includes cash position, burn rate, and runway
  • Upcoming milestones include specific dates and measurable criteria
  • Asks section contains at least one specific, actionable request
  • Tone matches company stage and user preference
  • No emojis anywhere
  • Dollar amounts and percentages formatted consistently
  • Readable in under 5 minutes (monthly) or 10 minutes (quarterly)
  • Previous-period milestones scored as hit, missed, or partial
  • Confidentiality notice and contact information included

9. Remind on confidentiality. Every update includes a confidentiality notice. Advise the user to send via secure channels (not public links), use BCC or a dedicated platform for large lists, review for anything they are not comfortable sharing, and consider separate versions for different investor tiers.

Related skills

Office & Documentspmworkflownotes

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.