Update to Unabyss

{
  "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.",
  "included_files": [],
  "name": "investor-update",
  "skill_md_contents": "---\nname: investor-update\ndescription: \"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.\"\n---\n\n# Investor Update\n\nDraft a complete investor update email from real signals — no manual compiling, no blank page. The founder reviews and sends, they don't assemble.\n\n## Required Integrations\n\nThis skill uses **Unabyss MCP** — `agentic_query` for cross-source synthesis, `store` to log that the update was sent.\n\n> If Unabyss is not connected, tell the user: \"This skill requires Unabyss MCP. You can connect it from the Tools menu.\"\n\n---\n\n## How to Run\n\n### Step 1 — Check for an existing export\n\nCall `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.\n\n### Step 2 — Run `agentic_query`\n\nInvestor updates need synthesis across product, sales, finance, team, and comms — use `agentic_query`:\n\n```\nLook across all connected sources from the last [30/60/90] days and surface everything relevant for an investor update:\n- Key metrics and numbers — revenue, MRR, ARR, growth, users, retention, burn, runway\n- What was shipped or built — product releases, features, technical milestones\n- Major decisions made — strategic pivots, pricing changes, hiring decisions, partnerships\n- Customer wins — new paying customers, expansions, notable logos, testimonials\n- Challenges or blockers — what's not working, what's slowing things down, what's at risk\n- Team updates — hires, departures, org changes\n- What's coming next — near-term roadmap, upcoming milestones, goals for next period\n\nReturn specific facts and numbers wherever available.\n```\n\nCall `agentic_query_read` to retrieve results.\n\n### Step 3 — Draft the update\n\n---\n\n**Subject:** [Company] Update — [Month/Quarter Year]\n\nHi [names],\n\n**The headline**\nOne honest sentence on where things stand overall.\n\n**Metrics**\n\n| Metric | This period | Last period |\n|--------|-------------|-------------|\n| [metric] | [value] | [value] |\n\n**What we shipped**\nSpecific features or releases. What they do, why they mattered.\n\n**Wins**\nCustomer wins, partnerships, proof points. Names and numbers where available.\n\n**What's hard**\nThe honest blockers. What's slower than expected, what's at risk, what hasn't worked.\n\n**Team**\nHires, departures, or notable changes. Skip if nothing significant.\n\n**Next 30–60 days**\n3–5 specific things the company is focused on.\n\n**Where we need help**\nThe most specific ask possible — an intro to X, advice on Y, a connection at Z.\n\nBest,\n[Name]\n\n---\n\n### Step 4 — Flag gaps and log\n\nAfter the draft:\n- List sections built on thin or inferred data — needs founder confirmation\n- List any metrics not found in Unabyss — needs manual addition\n\nOnce the founder confirms the update is sent, call `store`:\n> Investor update sent for [period] on [date]. Key metrics: [summary]. Main ask: [ask].\n\n---\n\n## Output Rules\n\n- Use `export_read` if a fresh export exists — skip `agentic_query`\n- \"What's hard\" is mandatory — an update without it reads as PR\n- Never invent metrics or outcomes — flag gaps instead\n- Under 400 words\n- No preamble before the subject line\n"
}