deal-sourcing-signals
Scan a company or sector for deal-sourcing signals across 6 dimensions. Triggered by: "/venture-capital-intelligence:deal-sourcing-signals", "scan signals for X", "what signals is X showing", "deal sourcing scan", "hiring signals for X", "is X raising soon", "monitor this company", "company signal scan", "sourcing brief for X", "what is X up to", "is X growing", "track this company", "deal signal report for X", "is this company fundraising", "what are the momentum signals for X", "find signals on X", "is X worth tracking". Claude Code only. Requires Python 3.x. Uses web search for live signal data.
Best use case
deal-sourcing-signals is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Scan a company or sector for deal-sourcing signals across 6 dimensions. Triggered by: "/venture-capital-intelligence:deal-sourcing-signals", "scan signals for X", "what signals is X showing", "deal sourcing scan", "hiring signals for X", "is X raising soon", "monitor this company", "company signal scan", "sourcing brief for X", "what is X up to", "is X growing", "track this company", "deal signal report for X", "is this company fundraising", "what are the momentum signals for X", "find signals on X", "is X worth tracking". Claude Code only. Requires Python 3.x. Uses web search for live signal data.
Teams using deal-sourcing-signals should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/deal-sourcing-signals/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How deal-sourcing-signals Compares
| Feature / Agent | deal-sourcing-signals | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Scan a company or sector for deal-sourcing signals across 6 dimensions. Triggered by: "/venture-capital-intelligence:deal-sourcing-signals", "scan signals for X", "what signals is X showing", "deal sourcing scan", "hiring signals for X", "is X raising soon", "monitor this company", "company signal scan", "sourcing brief for X", "what is X up to", "is X growing", "track this company", "deal signal report for X", "is this company fundraising", "what are the momentum signals for X", "find signals on X", "is X worth tracking". Claude Code only. Requires Python 3.x. Uses web search for live signal data.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Best AI Skills for Claude
Explore the best AI skills for Claude and Claude Code across coding, research, workflow automation, documentation, and agent operations.
ChatGPT vs Claude for Agent Skills
Compare ChatGPT and Claude for AI agent skills across coding, writing, research, and reusable workflow execution.
SKILL.md Source
# Venture Capital Intelligence — Deal Sourcing Signals Agent
You are a deal sourcing analyst at a top VC firm. You systematically scan companies for 6 types of signals that indicate investment readiness, growth momentum, or competitive threats.
**Signal taxonomy (from wizenheimer/subsignal):** Hiring · Funding · Product · Team · Market · Tech
**Pipeline:** Claude web searches → Claude classifies signals → Python scores → Claude writes sourcing brief → Python formats
---
## STEP 1 — DEFINE SCAN TARGET
Ask for or extract:
- Company name (or sector/theme if doing a landscape scan)
- Website URL (if known)
- Stage filter (Pre-Seed / Seed / Series A)
- Geographic focus
---
## STEP 2 — CLAUDE: RUN TARGETED WEB SEARCHES
Execute 6 searches — one per signal type:
**HIRING SIGNALS** — `"[company name]" jobs hiring engineer 2024 2025`
Look for: headcount growth rate, new roles (sales/marketing = GTM signal), senior hires (exec = scaling signal), engineering roles (product build = technical depth)
**FUNDING SIGNALS** — `"[company name]" funding raised investment round 2024`
Look for: recent raises, investors named, valuation mentions, fundraise announcements
**PRODUCT SIGNALS** — `"[company name]" launch new feature product update changelog 2024`
Look for: product launches, new integrations, press coverage of product milestones, G2/ProductHunt activity
**TEAM SIGNALS** — `"[company name]" CEO CTO hire joined left departed leadership 2024`
Look for: key executive hires (positive), executive departures (risk), advisor additions (network signal), founding team additions
**MARKET SIGNALS** — `"[market category of company]" growth 2024 2025 trend acquisition`
Look for: market growth announcements, category-defining acquisitions, competitor funding (validates category), regulatory tailwinds
**TECH SIGNALS** — `"[company name]" technology stack API open-source github developer`
Look for: tech stack clues from job postings, GitHub activity, API announcements, developer tools adoption
---
## STEP 3 — CLAUDE: EXTRACT AND CLASSIFY RAW SIGNALS
For each search, extract up to 5 specific signals found. Save to `${CLAUDE_PLUGIN_ROOT}/skills/deal-sourcing-signals/output/raw_signals.json`:
```json
{
"company": "",
"scan_date": "",
"signals": [
{
"type": "HIRING",
"description": "Posted 12 engineering roles in last 30 days — 3× increase from prior quarter",
"source": "LinkedIn jobs",
"date": "2025-01",
"strength": 8,
"sentiment": "POSITIVE"
}
]
}
```
**Signal types (canonical):** HIRING · FUNDING · PRODUCT · TEAM · MARKET · TECH
**Strength scoring (1–10):**
- 9–10: Very strong signal (e.g., Series A just closed, CTO hired from Google)
- 7–8: Strong signal (e.g., 3× hiring growth, major product launch)
- 5–6: Moderate signal (e.g., minor product update, 1 new hire)
- 3–4: Weak signal (e.g., old news, could be noise)
- 1–2: Noise (e.g., unverified rumor, no corroboration)
**Sentiment:** POSITIVE · NEGATIVE · NEUTRAL
---
## STEP 4 — PYTHON: SCORE SIGNALS AND COMPUTE DEAL SCORE
Run: `python "${CLAUDE_PLUGIN_ROOT}/skills/deal-sourcing-signals/scripts/signal_scorer.py"`
Computes:
- Score per signal type (0–100)
- Overall deal score (0–100)
- Investment readiness: MONITOR / ENGAGE / MOVE FAST
---
## STEP 5 — CLAUDE: WRITE SOURCING BRIEF
Using the signal data, write a 200-word sourcing brief:
- **Why interesting**: what the signal pattern reveals about company trajectory
- **Timing**: why now is the right time to reach out
- **First meeting angle**: what specific question or value-add to lead with
- **Watch items**: signals to monitor over next 30–90 days
---
## STEP 6 — PYTHON: FORMAT FINAL REPORT
Run: `python "${CLAUDE_PLUGIN_ROOT}/skills/deal-sourcing-signals/scripts/sourcing_formatter.py"`
---
## SIGNAL INTERPRETATION GUIDE
```
Pattern: Heavy hiring + no funding announcement
→ Likely bootstrapped or post-raise spending. May be raising soon.
Pattern: Product launches + positive press + no Series A
→ PMF validation period. Prime Series A target.
Pattern: Exec departures + hiring freeze
→ Risk signal. Monitor before engaging.
Pattern: Market signal strong (competitors raising) + company quiet
→ Category validated by others. May be stealth or early.
Pattern: Tech signals (GitHub activity, API launch) + small team
→ Developer-led GTM. High technical quality signal.
```Related Skills
soft-screening-startup
Activate for ANY startup evaluation, investment screening, or company assessment. Triggers include: "evaluate this startup", "screen this company", "should I invest in X", "is this a good investment", "what do you think about this company", "review this startup", "score this company", "rate this pitch", "assess this founder", "quick take on X", "is X worth investing in", "pass or decline on X", "what's your verdict on X", "first look at this company", "quick screen on X", "what's your take on this founder", "is this fundable", "would a VC invest in this". Also triggers when a user pastes a company description, funding ask, or founder background and asks for an opinion. Works on claude.ai and Claude Code. For hard-mode deterministic scoring with Python audit trail, use /venture-capital-intelligence:hard-screening-startup.
market-size
Run TAM/SAM/SOM market sizing with top-down and bottom-up methods, competitive landscape, and tech stack analysis. Triggered by: "/venture-capital-intelligence:market-size", "size this market", "what is the TAM for X", "market sizing analysis", "competitive landscape for X", "who are the competitors", "TAM SAM SOM for X", "market opportunity analysis", "how big is this market", "is this market big enough", "what's the addressable market", "total addressable market for X", "how large is the opportunity", "market research for X", "how saturated is this market", "market size estimate", "go-to-market sizing", "what is the serviceable market". Claude Code only. Requires Python 3.x. Uses web search for market data.
hard-screening-startup
Deterministic Python-scored startup screening with full audit trail. Use when you need a reproducible, weighted-score verdict on a startup — not just a qualitative opinion. Triggered by: "/venture-capital-intelligence:hard-screening-startup", "hard screen this startup", "run a hard screen on X", "score this startup with Python", "give me an auditable screen", "run a scored evaluation on X", "give me a weighted score for this startup", "screen with numbers", "objective startup score", "reproducible screen", "investment scorecard for X", "score this company out of 100", "run the full screen on X". Claude Code only. Requires Python 3.x. For conversational soft-mode screening, use /venture-capital-intelligence:soft-screening-startup.
fund-operations
Compute fund KPIs (TVPI, DPI, IRR, MOIC), model carried interest and management fees, and generate LP quarterly update narratives. Triggered by: "/venture-capital-intelligence:fund-operations", "calculate fund KPIs", "what is my fund TVPI", "IRR calculation", "compute MOIC", "LP report", "quarterly update draft", "carried interest calculation", "management fee calculation", "fund performance report", "write my LP update", "how is my fund performing", "what is my DPI", "fund returns analysis", "model my carry", "how much carry do I earn", "portfolio performance summary", "generate investor update". Claude Code only. Requires Python 3.x.
financial-model
Run deterministic financial models for startup valuation and SaaS health analysis. Triggered by: "/venture-capital-intelligence:financial-model", "run a financial model on X", "DCF this company", "model the financials", "calculate runway", "what is the valuation", "SaaS metrics model", "LTV CAC analysis", "unit economics", "burn rate analysis", "comparable valuation", "how long is my runway", "what's my burn multiple", "revenue projection for X", "model the ARR growth", "what is the pre-money valuation", "comps analysis", "NRR and churn model", "how healthy are these SaaS metrics". Claude Code only. Requires Python 3.x. Accepts user-supplied numbers or searches for publicly available data.
explain-equity-terms
Activate for ANY equity, legal, or term sheet question related to startup investing or fundraising. Triggers include: "what is a SAFE", "explain this term sheet", "what does pro-rata mean", "what is liquidation preference", "explain anti-dilution", "ISO vs NSO", "what is a 83(b) election", "what is carried interest", "explain drag-along", "what is a valuation cap", "what does MFN mean", "explain convertible note vs SAFE", "what is a down round", "explain vesting cliff", "what does fully diluted mean", "term sheet question", "equity question", "what does this clause mean". Also triggers when a user pastes legal text from a term sheet, SAFE, or subscription agreement and asks what it means. Works on claude.ai and Claude Code.
cap-table-waterfall
Model cap table dilution, SAFE conversion, and exit waterfall across scenarios. Triggered by: "/venture-capital-intelligence:cap-table-waterfall", "model my cap table", "simulate dilution", "SAFE conversion math", "exit waterfall", "how much do I own after Series A", "liquidation waterfall", "cap table scenario", "what happens to equity at exit", "model the waterfall", "how much equity do I have left", "what is my ownership after funding", "run dilution scenarios", "model a new round", "what happens at acquisition", "cap table after SAFE conversion", "pari passu waterfall", "preference stack analysis". Claude Code only. Requires Python 3.x.
analyze-pitch-deck
Activate for ANY pitch deck analysis, feedback, or review request. Triggers include: "analyze this deck", "review my pitch deck", "critique my pitch", "feedback on my slides", "is my deck investor ready", "what's wrong with my pitch", "how would a VC react to this deck", "score my pitch deck", "rate my slides", "improve my deck", "what slides am I missing", "is this pitch compelling". Also triggers when a user pastes slide content, describes their deck structure, or shares a company narrative and asks for investor feedback. Works on claude.ai and Claude Code.
public-plugin-builder
Activate when the user wants to build a Claude plugin, create a Claude skill, make a Claude agent, structure a Claude Code plugin, says "build a plugin", "create a skill", "new claude skill", "new agent", "help me make a plugin", "plugin builder", "claude plugin helper", "how do I build a Claude skill", "I want to create a Claude plugin", "plugin building", or asks how to structure a Claude Code plugin or publish to the Claude marketplace. Works on both claude.ai (generates files as code blocks) and Claude Code (writes and pushes files).
server-components
This skill should be used when the user asks about "Server Components", "Client Components", "'use client' directive", "when to use server vs client", "RSC patterns", "component composition", "data fetching in components", or needs guidance on React Server Components architecture in Next.js.
server-actions
This skill should be used when the user asks about "Server Actions", "form handling in Next.js", "mutations", "useFormState", "useFormStatus", "revalidatePath", "revalidateTag", or needs guidance on data mutations and form submissions in Next.js App Router.
route-handlers
This skill should be used when the user asks to "create an API route", "add an endpoint", "build a REST API", "handle POST requests", "create route handlers", "stream responses", or needs guidance on Next.js API development in the App Router.