Update to Unabyss

{
  "description": "Draft personalized investor outreach — cold emails, warm intro requests, follow-ups, and post-meeting notes — grounded in real history and current traction pulled from Unabyss. Use this skill whenever the user wants to reach out to an investor, follow up after a meeting, ask for an intro, or send any fundraising communication. Also trigger when someone says they need to email an investor, haven't heard back, or wants to get a meeting.",
  "included_files": [],
  "name": "investor-outreach",
  "skill_md_contents": "---\nname: investor-outreach\ndescription: \"Draft personalized investor outreach — cold emails, warm intro requests, follow-ups, and post-meeting notes — grounded in real history and current traction pulled from Unabyss. Use this skill whenever the user wants to reach out to an investor, follow up after a meeting, ask for an intro, or send any fundraising communication. Also trigger when someone says they need to email an investor, haven't heard back, or wants to get a meeting.\"\n---\n\n# Investor Outreach\n\nWrite investor communication that is specific, honest, and easy to act on. Unabyss provides the actual history and traction — nothing needs to be fabricated or generically filled in.\n\n## Required Integrations\n\nThis skill uses **Unabyss MCP** and **web search**.\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 — Pull internal context with `query`\n\nTwo fast lookups — use `query` for both:\n\n**Traction:**\n```\nWhat is our current traction — MRR, ARR, growth rate, user numbers, key customer wins, or any other metrics that show momentum? What have we shipped recently? What's the one-line description of what we're building and why now?\n```\n\n**History with this investor:**\n```\nDo we have any prior context on [investor name] or [firm name]? Previous conversations, emails, intros, meetings, or anything discussed before?\n```\n\nIf prior history exists — use it. A follow-up to someone you've spoken to before is a different message than cold outreach.\n\n### Step 2 — Research the investor via web search\n\n- Their thesis and what they've said publicly about what they're looking for\n- Recent portfolio companies adjacent to the user's space\n- Any public writing, talks, or posts from the partner being targeted\n- Whether they're actively investing right now\n\n### Step 3 — Draft by outreach type\n\n**Cold email** — under 150 words:\n1. Why this investor specifically — one real, specific reason\n2. What the company does — one sentence, no jargon\n3. The proof point that matters most — one concrete number or signal\n4. The ask — one specific, low-friction next step\n\n**Warm intro request** — forwardable blurb under 100 words the connector can paste directly. One sentence each on why the intro makes sense for both sides.\n\n**Follow-up after no response** — one new data point that didn't exist before. Under 50 words. One sentence ask.\n\n**Post-meeting follow-up** — reference one specific thing discussed. Deliver any promised materials. State the clear next step.\n\n---\n\n## Hard Bans\n\n- \"I'd love to connect\" / \"excited to share\"\n- Thesis praise not tied to something specific they actually said or did\n- Vague asks (\"would love to get your thoughts\")\n- Anything copy-pasteable unchanged to a different investor\n\n---\n\n## Output Rules\n\n- Use `query` for both traction and investor history — fast and sufficient\n- If prior history exists, the draft must acknowledge it — don't treat warm as cold\n- Always offer multiple subject line options\n- After the draft, add: \"Personalization check — [what was used and what still needs verification]\"\n- No preamble — go straight to the draft\n\n"
}