accessibility
Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when…
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.
$ npx -y skills add affaan-m/ECC --skill investor-outreach --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/investor-outreachContext preview
The summary Claude sees to decide when to auto-load this skill.
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.
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
Write investor communication that is short, concrete, and easy to act on.
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.
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.
Delete and rewrite any of these:
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
Reference one or more of:
If that context is missing, state that the draft still needs personalization instead of pretending it is finished.
Default:
Do not keep nudging after that unless the user wants a longer sequence.
Make life easy for the connector:
Include:
Before delivering:
Your agent can write code, but ECC gives it a coordinated engineering system and toolbox: it plans before it builds, verifies changes with tests, reviews its own work from a fresh context, remembers what matters, and turns repeated wins into reusable skills
Repo: affaan-m/ECC
Design, implement, and audit inclusive digital products using WCAG 2.2 Level AA. Use when building or auditing UI that must meet WCAG 2.2 Level AA, or when…
Full-stack diagnostic for agent and LLM applications. Audits the 12-layer agent stack for wrapper regression, memory pollution, tool discipline failures,…
Head-to-head comparison of coding agents (Claude Code, Aider, Codex, etc.) on custom tasks with pass rate, cost, time, and consistency metrics. Use when…
Design and optimize AI agent action spaces, tool definitions, and observation formatting for higher completion rates. Use when defining or revising an agent's…
Structured self-debugging workflow for AI agent failures using capture, diagnosis, contained recovery, and introspection reports. Use when an agent run fails…
Add x402 payment execution to AI agents with per-task budgets, spending controls, and non-custodial wallets. Supports Base through agentwallet-sdk and X Layer…