cc-skill:investor-update-writer

Claude Code skill · anthropic · active

last 30 days

0 calls

0 of 30 days active

explain like I am new to this

what it does

Generates a monthly update email for investors and advisors in a clean, structured format. It pulls from your weekly memos, organizes wins with numbers, lists honest challenges, shows key metrics in a table, and ends with specific asks you need help with.

who it is for

Founders and CEOs who need to keep investors, advisors, or mentors informed about real progress and problems without marketing fluff.

when it fires

When you ask for an investor update, advisor update, monthly update, stakeholder report, investor letter, board update, or mention sending updates to a specific investor or advisor.

say something like

"Generate my investor update for December"
"Write an advisor update pulling from my weekly memos"
"Create a monthly stakeholder report for my angels"

what you might get back

Subject: ArbiCall update — December 2024 Hi all, We landed our first two paying customers and cut infrastructure costs in half. Wins - Closed TradeCorp at $8K MRR (3-year deal) - Reduced per-call cost from $0.18 to $0.04 Challenges - Free trial conversion stalled at 3%. Testing email sequence change next week. Metrics | Metric | December | November | | MRR | $12K | $4K | | Active users | 340 | 215 | Asks - Intro to operations heads at regional banks (target: 5) - Advice on handling pricing objections Thanks for the support, Jay

how to know it worked

You'll know it worked because you get a professional email with real numbers, honest problems, and clear asks you can actually send to your investors without revising.

is this skill working for me

never used

cloud runs

0 deployments

local fires

Claude Code (optional)

posts published

from drafts

attributed

$0.00

signups + revenue

Deploy this skill as a cloud automation to put it to work — runs on a schedule, dispatches output to Telegram or email, and logs every result here.

Deploy this skill

no laptop required

Run this skill on a schedule in the cloud. Pipe output to Telegram, email, or any webhook. Every run is logged here with full output, cost, and thumbs feedback.

How this performs

Cloud-automation runs, real outputs, and feedback.

No cloud runs yet for this skill.

Once you deploy it (above), every run will show up here with the actual output, exact cost, and a thumbs button so you can rate quality over time.

what this is

Claude Code skill at /Users/olanrewajukareem/.claude/skills/investor-update-writer/SKILL.md. Auto-triggered by description matching when you type in Claude Code, OR embedded into agent system prompts (LeadFlow framework skills are wired this way). Auto-synced from disk every 6h via launchd.

Use this skill when generating monthly investor updates, advisor updates, stakeholder reports, or any external-facing progress communication. Triggers on "investor update", "advisor update", "monthly update", "stakeholder report", "investor letter",

Local Claude Code use (optional)

Install the SKILL.md file locally so this skill is available the next time you open Claude Code on your Mac. Most users skip this and just use cloud deployments above.

Install on your machine

Save this skill to ~/.claude/skills/investor-update-writer/SKILL.md so Claude Code auto-loads it whenever its description matches your prompt.

30-day activity

never used

2026-04-03today

cost model

unitincluded

capabilities

{
  "source": "global",
  "description": "Use this skill when generating monthly investor updates, advisor updates, stakeholder reports, or any external-facing progress communication. Triggers on \"investor update\", \"advisor update\", \"monthly update\", \"stakeholder report\", \"investor letter\", \"board update\", or \"send update to [investor/advisor]\". Produces direct, no-spin updates with metrics, asks, and honest acknowledgment of challenges."
}

how it gets called

{
  "method": "embed_in_prompt",
  "skill_path": "/Users/olanrewajukareem/.claude/skills/investor-update-writer/SKILL.md"
}

This tool has never been called in the last 30 days.

That means either: (a) the system has not had a task that matched its strengths, (b) a more cost-effective alternative was picked by the router, or (c) the related automation is toggled OFF on /automations. The Recommender reviews idle tools weekly and may suggest killing it.