mirror of
https://github.com/affaan-m/everything-claude-code.git
synced 2026-06-23 13:49:30 +08:00
db7f2a6fd5
The official Agent Skills spec (agentskills.io/specification) whitelists exactly 6 top-level frontmatter keys (name/description/license/compatibility/metadata/ allowed-tools). A top-level `origin` key fails the official validator (anthropics/skills quick_validate.py ALLOWED_PROPERTIES; skills-ref validate). This moves `origin: X` -> `metadata.origin: X` across the canonical skills/ tree, preserving each value verbatim. Frontmatter-only, minimal diff. - 251 SKILL.md updated (242 new metadata block, 9 appended to existing metadata) - origin values preserved verbatim (verified 251/251) - YAML validated on all changed files - scoped to canonical skills/ only (docs/<lang> translations + tool mirrors .cursor/.kiro/.agents left untouched; presumably regenerated from canonical) Addresses #2233
93 lines
2.6 KiB
Markdown
93 lines
2.6 KiB
Markdown
---
|
|
name: investor-outreach
|
|
description: Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.
|
|
metadata:
|
|
origin: ECC
|
|
---
|
|
|
|
# Investor Outreach
|
|
|
|
Write investor communication that is short, concrete, and easy to act on.
|
|
|
|
## When to Activate
|
|
|
|
- writing a cold email to an investor
|
|
- drafting a warm intro request
|
|
- sending follow-ups after a meeting or no response
|
|
- writing investor updates during a process
|
|
- tailoring outreach based on fund thesis or partner fit
|
|
|
|
## Core Rules
|
|
|
|
1. Personalize every outbound message.
|
|
2. Keep the ask low-friction.
|
|
3. Use proof instead of adjectives.
|
|
4. Stay concise.
|
|
5. Never send copy that could go to any investor.
|
|
|
|
## Voice Handling
|
|
|
|
If the user's voice matters, run `brand-voice` first and reuse its `VOICE PROFILE`.
|
|
This skill should keep the investor-specific structure and ask discipline, not recreate its own parallel voice system.
|
|
|
|
## Hard Bans
|
|
|
|
Delete and rewrite any of these:
|
|
- "I'd love to connect"
|
|
- "excited to share"
|
|
- generic thesis praise without a real tie-in
|
|
- vague founder adjectives
|
|
- begging language
|
|
- soft closing questions when a direct ask is clearer
|
|
|
|
## Cold Email Structure
|
|
|
|
1. subject line: short and specific
|
|
2. opener: why this investor specifically
|
|
3. pitch: what the company does, why now, and what proof matters
|
|
4. ask: one concrete next step
|
|
5. sign-off: name, role, and one credibility anchor if needed
|
|
|
|
## Personalization Sources
|
|
|
|
Reference one or more of:
|
|
- relevant portfolio companies
|
|
- a public thesis, talk, post, or article
|
|
- a mutual connection
|
|
- a clear market or product fit with the investor's focus
|
|
|
|
If that context is missing, state that the draft still needs personalization instead of pretending it is finished.
|
|
|
|
## Follow-Up Cadence
|
|
|
|
Default:
|
|
- day 0: initial outbound
|
|
- day 4 or 5: short follow-up with one new data point
|
|
- day 10 to 12: final follow-up with a clean close
|
|
|
|
Do not keep nudging after that unless the user wants a longer sequence.
|
|
|
|
## Warm Intro Requests
|
|
|
|
Make life easy for the connector:
|
|
- explain why the intro is a fit
|
|
- include a forwardable blurb
|
|
- keep the forwardable blurb under 100 words
|
|
|
|
## Post-Meeting Updates
|
|
|
|
Include:
|
|
- the specific thing discussed
|
|
- the answer or update promised
|
|
- one new proof point if available
|
|
- the next step
|
|
|
|
## Quality Gate
|
|
|
|
Before delivering:
|
|
- the message is genuinely personalized
|
|
- the ask is explicit
|
|
- the proof point is concrete
|
|
- filler praise and softener language are gone
|
|
- word count stays tight
|