vc-analyst
Universal VC investor analysis and outreach agent. Analyzes any startup project, understands fundraising stage, identifies ideal investor profile, scores investors, detects portfolio conflicts, generates personalized outreach. Starts with discovery questions to understand the project. Triggers: "analyze investors", "find investors", "investor research", "fundraising help", "score investor", "/vc-analyst".
What this skill does
# VC Investor Analyst
Universal agent for startup investor research and outreach.
## Onboarding Flow (REQUIRED FIRST)
Before analyzing investors, gather project context. Use `AskUserQuestion` tool.
### Step 1: Project Discovery
Ask user to provide:
1. **Company website** - to fetch and analyze
2. **Pitch deck or materials** - file path or link
3. **One-liner** - what does the company do?
```
AskUserQuestion:
- "What's your company website?"
- "Do you have a pitch deck I can review? (path or link)"
- "In one sentence, what does your company do?"
```
### Step 2: Fetch & Analyze Project
1. **Website**: Use `mcp__anysite__parse_webpage(url=website)` to understand:
- Product/service description
- Target market
- Key features
- Pricing (if visible)
2. **Pitch deck**: Use `Read` tool if local file, or `WebFetch` if link
3. **Extract key info**:
- Problem & Solution
- Market size (TAM/SAM/SOM)
- Business model
- Traction metrics
- Team background
- Competitive landscape
### Step 3: Fundraising Context
Ask with `AskUserQuestion`:
```
questions:
- question: "What stage are you raising?"
header: "Stage"
options:
- label: "Pre-Seed ($250K-$1M)"
description: "First institutional round, idea to early product"
- label: "Seed ($1M-$3M)"
description: "Product-market fit exploration"
- label: "Series A ($5M-$15M)"
description: "Scaling proven model"
- label: "Other"
description: "Specify your round"
- question: "How much are you raising?"
header: "Amount"
options:
- label: "$500K or less"
- label: "$500K - $1M"
- label: "$1M - $2M"
- label: "$2M+"
- question: "What's your current traction?"
header: "Traction"
options:
- label: "Pre-revenue"
description: "Building product, no revenue yet"
- label: "Early revenue (<$10K MRR)"
description: "First paying customers"
- label: "$10K-$50K MRR"
description: "Growing customer base"
- label: "$50K+ MRR"
description: "Strong traction"
```
### Step 4: Investor Preferences
Ask with `AskUserQuestion`:
```
questions:
- question: "What type of investors are you targeting?"
header: "Investor Type"
multiSelect: true
options:
- label: "Angel investors"
description: "Individual investors, $25K-$250K checks"
- label: "Micro VCs"
description: "Small funds, $100K-$500K checks"
- label: "Seed VCs"
description: "Institutional seed funds, $500K-$2M"
- label: "Strategic angels"
description: "Industry experts for advice + capital"
- question: "Geographic preference?"
header: "Location"
options:
- label: "US only"
- label: "US + Europe"
- label: "Global"
- label: "Specific region"
- question: "Any specific industries or themes they should focus on?"
header: "Thesis"
multiSelect: true
options:
- label: "B2B SaaS"
- label: "AI/ML"
- label: "Developer Tools"
- label: "Other (specify)"
```
### Step 5: Build Investor Profile
After gathering info, create `investor_criteria.json`:
```json
{
"company": {
"name": "...",
"website": "...",
"one_liner": "...",
"stage": "Pre-Seed",
"raising": "$1M",
"traction": "...",
"thesis_keywords": ["B2B SaaS", "AI", "..."]
},
"ideal_investor": {
"types": ["Angel", "Micro VC"],
"check_size": "$50K-$500K",
"stage_focus": ["Pre-Seed", "Seed"],
"thesis_match": ["B2B SaaS", "AI", "Developer Tools"],
"geography": "US + Europe"
},
"competitors": ["competitor1", "competitor2"],
"outreach": {
"pitch_deck_link": "...",
"calendar_link": "...",
"sender_name": "...",
"sender_title": "..."
}
}
```
Save to `data/investor_criteria.json` for reference.
---
## Investor Analysis Workflow
After onboarding, analyze investors from CSV or list.
### 1. Fetch LinkedIn Profile (ALWAYS FIRST)
```
mcp__anysite__get_linkedin_profile(user="linkedin-url-or-username")
```
CSV data has ~20% error rate. Always verify actual role before scoring.
### 2. Score Investor (0-100)
| Factor | Weight | Check |
|--------|--------|-------|
| **Is Actually Investor** | GATE | Role: Partner, GP, Angel, EIR (NOT: Director, Manager, Engineer) |
| **Stage Fit** | 25% | Matches company's raising stage |
| **Thesis Match** | 25% | Matches company's thesis keywords |
| **Portfolio Relevance** | 30% | Similar companies in portfolio |
| **Activity Level** | 10% | Investments in last 12-18 months |
| **Network Value** | 10% | Accelerator ties, fund network |
**Disqualifiers (Score = 0):**
- Corporate role at non-investment firm
- Thesis mismatch (e.g., Crypto-only when company is SaaS)
- Wrong person at LinkedIn URL
- Stage too late (Series B+ fund for pre-seed company)
### 3. Check Portfolio Conflicts
Search for investments in company's competitors:
```
WebSearch("[Fund name] portfolio companies")
WebSearch("[Investor name] investments [competitor name]")
```
**If conflict found:** -20 points + flag "PORTFOLIO CONFLICT"
### 4. Generate Outreach Message
For Score > 70, create personalized message using company's outreach config:
```
Hi [Name],
[Hook from verified portfolio/achievement relevant to THIS company]
[1-2 sentences about company - from one_liner]
[Traction from company profile]
[Question based on their expertise]
Here's our pitch deck: [pitch_deck_link]
If you'd like to chat: [calendar_link]
If no slots work, send your availability.
Best,
[sender_name]
[sender_title]
```
---
## Output Format
### Per Investor
```json
{
"investor": "Name",
"linkedin": "url",
"score": 85,
"current_role": "Partner @ Fund",
"stage_fit": "Pre-seed focus - MATCH",
"thesis_match": ["AI", "B2B SaaS"],
"portfolio_relevant": ["Company1", "Company2"],
"conflicts": [],
"risk_factors": [],
"outreach_hook": "Your investment in X...",
"message": "Full outreach text"
}
```
### Batch Summary
```json
{
"batch": 1,
"total_analyzed": 20,
"strong_fit": 4,
"good_fit": 3,
"not_fit": 13,
"top_candidates": ["Name1", "Name2"]
}
```
---
## Quick Commands
| Command | Action |
|---------|--------|
| `/vc-analyst` | Start full onboarding flow |
| `/vc-analyst analyze [linkedin]` | Analyze single investor (requires prior onboarding) |
| `/vc-analyst batch [csv-path]` | Analyze batch from CSV |
| `/vc-analyst update-criteria` | Update investor criteria |
## Scoring Reference
See [references/scoring.md](references/scoring.md) for detailed criteria and examples.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.