← Files UnabyssARCHIVED FILE

SKILL.md

3.5 KB · Oct 2, 2026 · 00:05 UTC

↓ Download file

---
name: investor-update
description: "Draft a monthly or quarterly investor update email from real company data — what shipped, key metrics, wins, blockers, and what help is needed — without the founder having to compile anything manually. Use this skill whenever the user wants to write an investor update, send a monthly update to investors, draft a board update, or keep investors in the loop on progress. Also trigger when someone says it's time to update investors or they haven't sent an update in a while."
---

# Investor Update

Draft a complete investor update email from real signals — no manual compiling, no blank page. The founder reviews and sends, they don't assemble.

## Required Integrations

This skill uses **Unabyss MCP** — `agentic_query` for cross-source synthesis, `store` to log that the update was sent.

> If Unabyss is not connected, tell the user: "This skill requires Unabyss MCP. You can connect it from the Tools menu."

---

## How to Run

### Step 1 — Check for an existing export

Call `export_list` first. If a recent company snapshot or investor update export exists and is fresh, call `export_read` to use it as a base.

### Step 2 — Run `agentic_query`

Investor updates need synthesis across product, sales, finance, team, and comms — use `agentic_query`:

```
Look across all connected sources from the last [30/60/90] days and surface everything relevant for an investor update:
- Key metrics and numbers — revenue, MRR, ARR, growth, users, retention, burn, runway
- What was shipped or built — product releases, features, technical milestones
- Major decisions made — strategic pivots, pricing changes, hiring decisions, partnerships
- Customer wins — new paying customers, expansions, notable logos, testimonials
- Challenges or blockers — what's not working, what's slowing things down, what's at risk
- Team updates — hires, departures, org changes
- What's coming next — near-term roadmap, upcoming milestones, goals for next period

Return specific facts and numbers wherever available.
```

Call `agentic_query_read` to retrieve results.

### Step 3 — Draft the update

---

**Subject:** [Company] Update — [Month/Quarter Year]

Hi [names],

**The headline**
One honest sentence on where things stand overall.

**Metrics**

| Metric | This period | Last period |
|--------|-------------|-------------|
| [metric] | [value] | [value] |

**What we shipped**
Specific features or releases. What they do, why they mattered.

**Wins**
Customer wins, partnerships, proof points. Names and numbers where available.

**What's hard**
The honest blockers. What's slower than expected, what's at risk, what hasn't worked.

**Team**
Hires, departures, or notable changes. Skip if nothing significant.

**Next 30–60 days**
3–5 specific things the company is focused on.

**Where we need help**
The most specific ask possible — an intro to X, advice on Y, a connection at Z.

Best,
[Name]

---

### Step 4 — Flag gaps and log

After the draft:
- List sections built on thin or inferred data — needs founder confirmation
- List any metrics not found in Unabyss — needs manual addition

Once the founder confirms the update is sent, call `store`:
> Investor update sent for [period] on [date]. Key metrics: [summary]. Main ask: [ask].

---

## Output Rules

- Use `export_read` if a fresh export exists — skip `agentic_query`
- "What's hard" is mandatory — an update without it reads as PR
- Never invent metrics or outcomes — flag gaps instead
- Under 400 words
- No preamble before the subject line

SHA-256: ecac37c4d3fa1379d8db41aed55d87307d340b2df66958972ed80a8d749ac8b1