agentleFS
OneWave-AIOneWave-AI/claude-skills/investor-update-writer/SKILL.md

investor-update-writer

Skill378 starsChanged 56 days agoMITView on GitHub

Generates monthly/quarterly investor updates. Takes KPIs, milestones, challenges, financials. Writes professional investor-update.md with highlights, metrics dashboard, product updates, team news, financial summary, upcoming milestones, asks. Multiple tones from seed-stage casual to Series B formal. Use when founders need to communicate progress to investors.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every KPI shows current and prior values with percentage change

    line 38
  2. Distinctive:

    Remind on confidentiality: Every update includes a confidentiality notice.

    line 50

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.