New: Earn 20% as an AgentAlley affiliate. Share your link and earn on every sale you refer. Join now New: Earn 20% as an affiliate. Join now

Write a structured monthly or quarterly investor update

Investor Update Skill

by mohitagw15856 · MIT license · ★ 1,395 on GitHub · updated Sep 23

Investor Update Skill cover

Write a structured monthly or quarterly investor update. Use when asked to write an investor update, investor newsletter, board update, or startup progress report for investors.

---
name: investor-update
description: "Write a structured monthly or quarterly investor update. Use when asked to write an investor update, investor newsletter, board update, or startup progress report for investors. Produces a clear, credible update with highlights, metrics, challenges, and asks — in the format investors actually want to read."
---

# Investor Update Skill

This skill writes a complete investor update — structured for clarity, honest about challenges, and specific about asks. Output follows the format preferred by most early-stage and growth investors.

## Required Inputs

Ask the user for these if not provided:
- **Company name and stage** (Seed / Series A / Series B / etc.)
- **Period covered** (month or quarter)
- **Key metrics this period** (revenue, MRR, users, churn, burn, runway — whatever's relevant)
- **Biggest wins**
- **Biggest challenges or misses**
- **Specific asks from investors** (intros, advice, talent, partnerships)

Overview

This skill writes a complete investor update — structured for clarity, honest about challenges, and specific about asks. Output follows the format preferred by most early-stage and growth investors.

Manual install (npx, ZIP)
Claude Codenpx skills add mohitagw15856/pm-claude-skills --skill investor-update -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/mohitagw15856/pm-claude-skills/tar.gz/f6ca79348c55 \ | tar -xz -C ~/.claude/skills --strip-components=2 pm-claude-skills-f6ca79348c55/skills/investor-update
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/3704b0f8c99d70a96ed8/investor-update.zip" -OutFile "$env:TEMP\investor-update.zip"; Expand-Archive "$env:TEMP\investor-update.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md4.9 KB
Read the files here
mohitagw15856/f6ca7931 file
SKILL.md
Show the full text136 lines

Investor Update Skill

This skill writes a complete investor update — structured for clarity, honest about challenges, and specific about asks. Output follows the format preferred by most early-stage and growth investors.

Required Inputs

Ask the user for these if not provided:

  • Company name and stage (Seed / Series A / Series B / etc.)
  • Period covered (month or quarter)
  • Key metrics this period (revenue, MRR, users, churn, burn, runway — whatever's relevant)
  • Biggest wins
  • Biggest challenges or misses
  • Specific asks from investors (intros, advice, talent, partnerships)
  • What's coming next period
  • Tone (formal / conversational — most investors prefer conversational)

Output Structure


[Company Name] — [Month/Quarter] Update [Date]


Hi [Investor names or "all"],

[One or two sentence opener — a specific highlight or honest framing of the period. Don't open with "Hope you're well." Open with the most important thing that happened.]


The Numbers

Metric This Period Last Period Change
[MRR / ARR] [Value] [Value] [+/- %]
[Active users / customers]
[Churn rate]
[Burn rate]
[Runway]
[Other key metric]

[1–2 sentences of narrative on the numbers — what's the story behind the movement? Don't just repeat the table.]


Highlights

[Highlight 1 — 4–6 word title] [2–4 sentences. What happened. Why it matters. Be specific — name the customer, the number, the milestone.]

[Highlight 2] [2–4 sentences]

[Highlight 3 — optional]


Challenges

[This section is what separates trustworthy updates from self-promotional ones. Investors know you have challenges. Being direct builds trust.]

[Challenge 1] [2–4 sentences. What the problem is. What you've tried. What you're doing about it. Don't spin — investors see through it.]

[Challenge 2 — if applicable]


Focus for Next [Month/Quarter]

[3–5 bullet points. What you're concentrating on next period and why. Keep it tight — not an exhaustive roadmap.]

  • [Priority 1]
  • [Priority 2]
  • [Priority 3]

Asks

[Be specific. "Let me know if you can help" is not an ask. These should be actionable items an investor can act on immediately.]

  1. [Ask type: e.g. Intro] — [Specific request. e.g. "Looking for an intro to procurement leads at mid-market SaaS companies. Happy to share a warm intro note."]
  2. [Ask type: e.g. Advice] — [Specific question you want input on]
  3. [Ask type: e.g. Talent] — [Specific hire you're looking for — title, key requirements]

[Closing line — 1 sentence. Forward-looking or a genuine thanks. Not "as always, let me know if you have questions."]

[Signature] [Name] [Company] [One way to reply — email / Calendly / reply to this thread]


Writing Rules

  • Updates should take an investor 3–4 minutes to read. If it's longer, trim it.
  • Never lead with process ("This month we focused on...") — lead with outcomes
  • Challenges section must be honest. A missing challenges section signals the founder isn't self-aware or isn't being transparent.
  • Metrics table must include comparison to last period — a number without context is meaningless
  • Asks must be specific enough that an investor knows within 5 seconds if they can help
  • No jargon or buzzwords ("synergies," "crushing it," "hockey stick") — plain language only

Quality Checks

  • Opens with a specific highlight or honest framing (not a pleasantry)
  • Numbers include period-over-period comparison
  • Challenges section is present and honest
  • Asks are specific and actionable
  • Total length is skimmable in 3–4 minutes
  • No spin or buzzwords

Anti-Patterns

  • Do not omit challenges or bad news — sanitised updates erode investor trust faster than bad results do
  • Do not bury the lead — use BLUF structure and put the most important news in the first paragraph
  • Do not send an update without a clear "Ask" section — investors who want to help need to know how
  • Do not use buzzwords or spin — investors see hundreds of updates and will see through vague positive language
  • Do not report metrics without a comparison baseline — numbers without context (vs. last period or target) are meaningless

Example Trigger Phrases

  • "Write an investor update for [month/quarter]"
  • "Draft a monthly update for our investors based on these notes: [paste notes]"
  • "Help me write a board update for Q[N]"
  • "Write our Series A investor newsletter"
1---
2name: investor-update
3description: "Write a structured monthly or quarterly investor update. Use when asked to write an investor update, investor newsletter, board update, or startup progress report for investors. Produces a clear, credible update with highlights, metrics, challenges, and asks — in the format investors actually want to read."
4---
5 
6# Investor Update Skill
7 
8This skill writes a complete investor update — structured for clarity, honest about challenges, and specific about asks. Output follows the format preferred by most early-stage and growth investors.
9 
10## Required Inputs
11 
12Ask the user for these if not provided:
13- **Company name and stage** (Seed / Series A / Series B / etc.)
14- **Period covered** (month or quarter)
15- **Key metrics this period** (revenue, MRR, users, churn, burn, runway — whatever's relevant)
16- **Biggest wins**
17- **Biggest challenges or misses**
18- **Specific asks from investors** (intros, advice, talent, partnerships)
19- **What's coming next period**
20- **Tone** (formal / conversational — most investors prefer conversational)
21 
22## Output Structure
23 
24---
25 
26**[Company Name] — [Month/Quarter] Update**
27*[Date]*
28 
29---
30 
31Hi [Investor names or "all"],
32 
33[One or two sentence opener — a specific highlight or honest framing of the period. Don't open with "Hope you're well." Open with the most important thing that happened.]
34 
35---
36 
37## The Numbers
38 
39| Metric | This Period | Last Period | Change |
40|---|---|---|---|
41| [MRR / ARR] | [Value] | [Value] | [+/- %] |
42| [Active users / customers] | | | |
43| [Churn rate] | | | |
44| [Burn rate] | | | |
45| [Runway] | | | |
46| [Other key metric] | | | |
47 
48[1–2 sentences of narrative on the numbers — what's the story behind the movement? Don't just repeat the table.]
49 
50---
51 
52## Highlights
53 
54**[Highlight 1 — 4–6 word title]**
55[2–4 sentences. What happened. Why it matters. Be specific — name the customer, the number, the milestone.]
56 
57**[Highlight 2]**
58[2–4 sentences]
59 
60**[Highlight 3 — optional]**
61 
62---
63 
64## Challenges
65 
66[This section is what separates trustworthy updates from self-promotional ones. Investors know you have challenges. Being direct builds trust.]
67 
68**[Challenge 1]**
69[2–4 sentences. What the problem is. What you've tried. What you're doing about it. Don't spin — investors see through it.]
70 
71**[Challenge 2 — if applicable]**
72 
73---
74 
75## Focus for Next [Month/Quarter]
76 
77[3–5 bullet points. What you're concentrating on next period and why. Keep it tight — not an exhaustive roadmap.]
78 
79- [Priority 1]
80- [Priority 2]
81- [Priority 3]
82 
83---
84 
85## Asks
86 
87[Be specific. "Let me know if you can help" is not an ask. These should be actionable items an investor can act on immediately.]
88 
891. **[Ask type: e.g. Intro]** — [Specific request. e.g. "Looking for an intro to procurement leads at mid-market SaaS companies. Happy to share a warm intro note."]
902. **[Ask type: e.g. Advice]** — [Specific question you want input on]
913. **[Ask type: e.g. Talent]** — [Specific hire you're looking for — title, key requirements]
92 
93---
94 
95[Closing line — 1 sentence. Forward-looking or a genuine thanks. Not "as always, let me know if you have questions."]
96 
97[Signature]
98[Name]
99[Company]
100[One way to reply — email / Calendly / reply to this thread]
101 
102---
103 
104## Writing Rules
105 
106- Updates should take an investor 3–4 minutes to read. If it's longer, trim it.
107- Never lead with process ("This month we focused on...") — lead with outcomes
108- Challenges section must be honest. A missing challenges section signals the founder isn't self-aware or isn't being transparent.
109- Metrics table must include comparison to last period — a number without context is meaningless
110- Asks must be specific enough that an investor knows within 5 seconds if they can help
111- No jargon or buzzwords ("synergies," "crushing it," "hockey stick") — plain language only
112 
113## Quality Checks
114 
115- [ ] Opens with a specific highlight or honest framing (not a pleasantry)
116- [ ] Numbers include period-over-period comparison
117- [ ] Challenges section is present and honest
118- [ ] Asks are specific and actionable
119- [ ] Total length is skimmable in 3–4 minutes
120- [ ] No spin or buzzwords
121 
122## Anti-Patterns
123 
124- [ ] Do not omit challenges or bad news — sanitised updates erode investor trust faster than bad results do
125- [ ] Do not bury the lead — use BLUF structure and put the most important news in the first paragraph
126- [ ] Do not send an update without a clear "Ask" section — investors who want to help need to know how
127- [ ] Do not use buzzwords or spin — investors see hundreds of updates and will see through vague positive language
128- [ ] Do not report metrics without a comparison baseline — numbers without context (vs. last period or target) are meaningless
129 
130## Example Trigger Phrases
131 
132- "Write an investor update for [month/quarter]"
133- "Draft a monthly update for our investors based on these notes: [paste notes]"
134- "Help me write a board update for Q[N]"
135- "Write our Series A investor newsletter"
136 
View all files on GitHub →

Details

Updated
Sep 23, 2026
License
MIT
Stars on the repo
★ 1,395
Checked
Source
mohitagw15856/pm-claude-skills ↗
Creator
mohitagw15856 · 193 listings
View creator

Made with investor-update

Investor Update Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)
Investor Update Skill — Galaxy 3D — fly through all 1170 skills as a glowing constellation you orbit and click into (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Investor Update Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)
Investor Update Skill — PM Skills Wrapped — your practice turned into a shareable, Spotify-Wrapped-style story (from the mohitagw15856/pm-claude-skills README)

by mohitagw15856

Similar skills

See all →
SkillTell us about your business and who you sell toA Free Giveaway That Grows Your Email Listcoreyhaines31/marketingskills · by coreyhaines31Tell us about your business and who you sell to, and get back a ready-to-launch free offer that turns website visitors into email signups and future customers.★ 51.1k GitHub starsSkillSays 'newsletter', 'email newsletter', 'weekly digest'Newsletter: Writing email newsletter edition...cwinvestments/memstack · by cwinvestmentsUse this skill when the user says 'newsletter', 'email newsletter', 'weekly digest', 'subscriber growth', 'open rates', or needs subject lines, content structure, sponsorship placement, and growth tactics for email newsletters. Do NOT use for lead magnets or content pipelines.★ 423 GitHub starsSkillWrite a signal-based cold outreach email that earns a replySignal-Based Cold Email (2026 benchmarks)kami-community/kami · by kami-communityWrite a signal-based cold outreach email that earns a reply. Use when drafting outbound/SDR email to a prospect with a known recent signal (funding, hiring, exec hire, launch, community post).★ 64 GitHub starsSkillHostinger Reach API for contact management, segmentationHostinger Reach (Email Marketing)hostinger/hostinger-agent-skills · by hostingerHostinger Reach (Email Marketing) API for contact management, segmentation, contact groups, and profile management. Use when creating or listing contacts, managing contact segments or groups, filtering contacts by subscription status, or working with email marketing profiles.★ 23 GitHub starsMCPExpert email marketing strategist for CRM-driven campaignsmsitarzewski/agency-agents · by msitarzewskiExpert email marketing strategist for CRM-driven campaigns, lifecycle automation, segmentation architecture, and deliverability. Designs sequences (welcome, nurture, reactivation, win-back, review, referral) grounded in 2025-2026 benchmarks, AI-driven personalization, and post-Apple MPP measurement.★ 154k GitHub starsSkillWrite B2B cold emails and follow-up sequences that getCold Email Writingcoreyhaines31/marketingskills · by coreyhaines31Write B2B cold emails and follow-up sequences that get replies. Use when the user wants to write cold outreach emails, prospecting emails, cold email campaigns, sales development emails, or SDR emails. Also use when the user mentions "cold outreach," "prospecting email," "outbound email," "email to leads," "reach out to prospects," "sales email," "follow-up email sequence," "nobody's replying to my emails," or "how do I write a cold email." Covers subject lines, opening lines, body copy, CTAs, personalization, and multi-touch follow-up sequences. For warm/lifecycle email sequences, see emails. For sales collateral beyond emails, see sales-enablement.★ 51.1k GitHub stars

More from mohitagw15856

SkillDesign a 360-degree feedback survey or write a structured360-Degree Feedback Template Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.★ 1.4k GitHub starsSkillDesign statistically rigorous A/B tests for product featuresA/B Test Planner Skillmohitagw15856/pm-claude-skills · by mohitagw15856Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.★ 1.4k GitHub starsSkillGenerate a WCAG 2.2 accessibility audit checklistAccessibility Audit Skillmohitagw15856/pm-claude-skills · by mohitagw15856Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.★ 1.4k GitHub starsSkillBuild a structured account plan for any key customerAccount Plan Skillmohitagw15856/pm-claude-skills · by mohitagw15856Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.★ 1.4k GitHub starsSkillOptimize an article for Answer Engine Optimization so AIAEO Optimizer Skillmohitagw15856/pm-claude-skills · by mohitagw15856Optimize an article for Answer Engine Optimization (AEO) so AI engines like ChatGPT, Perplexity, and Claude can extract, quote, and cite it. Use when asked to AEO-optimize, make content AI-readable, improve AI citation chances, or adapt an article for answer engines. Produces an AEO-optimised rewrite with question headings, 50–80 word answer capsules, a paragraph-length audit, and flagged trust signals.★ 1.4k GitHub starsSkillConduct a structured ethical review of an AI or ML featureAI Ethics Review Skillmohitagw15856/pm-claude-skills · by mohitagw15856Conduct a structured ethical review of an AI or ML feature, model, or product. Use when preparing to deploy an AI system, assessing algorithmic risk, auditing a model for bias, or producing a responsible AI impact assessment. Produces a structured ethics review covering fairness, transparency, privacy, safety, accountability, and societal impact with a risk tier score, pre-deployment checklist, and prioritised mitigations.★ 1.4k GitHub stars