funding-signal-outreach
End-to-end funding signal composite. Takes any set of companies, detects recent funding events, qualifies against your company context, finds relevant people (buyers, champions, users), and drafts personalized outreach. Tool-agnostic — works with any company source, contact finder, and outreach platform.
npx skills add gooseworks-ai/goose-skills --skill funding-signal-outreach --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Detects recent funding events across a set of companies, qualifies them against your company context, finds the right people to reach out to, and drafts personalized emails. The full chain from signal to outreach-ready.
How it works
- Step 0: Configuration (one-time) to store company source, signal tool, contact tool, outreach tool, and your company context.
- Step 1: Detect Funding Signals for each input company using a configured signal_tool (web search, Apollo, Crunchbase, PitchBook, etc.); extract funding details and filter to those with a signal; output funded_companies with funding_amount, funding_stage, funding_date, lead_investors, source_url, confidence, and original_company_data.
- Step 2: Qualify & Prioritize funded_companies against your company context, assigning a priority_tier (tier_1, tier_2, tier_3, or Drop) and producing relevance_reasoning, outreach_angle, recommended_approach, and estimated_team_size. Also output dropped_companies with a drop_reason.
- Step 3: Find Relevant People for each qualified company using contact_tool (Apollo, LinkedIn Sales Nav, Clearbit, Web search, etc.); gather full_name, title, email (if available), LinkedIn URL, and role_type (buyer, champion, user); prioritization by buyer, then champion, then user; cap at max_contacts_per_company; output contacts and contacts_without_email.
- Step 4: Draft Personalized Emails for each contact with your company context to produce email_sequences; select framework based on funding signal; build personalization context (signal reference, company context, role-specific pain, proof point, outreach angle); generate multi-touch sequences with specified word counts and CTAs, adhering to the email-drafting rules.
When to use it
Load this composite when:
- User says "check if any of these companies raised funding", "funding signal outreach", or "reach out to recently funded companies".
- User has a list of companies and wants to act on funding signals.
- An upstream workflow triggers a funding signal check.
What it can touch
- inputs include: company_list, your_company_context.
- tools configured per step: web search, Apollo, Crunchbase, PitchBook, LinkedIn, Clearbit, etc., and outreach platforms for sending emails.
- outputs include: funded_companies, qualified_companies, contacts, email_sequences.
Caveats
- The process is tool-agnostic and relies on external data sources; results depend on tool availability and data freshness.
- It preserves data contracts per step and requires configuration for data sources and outreach tools.
- The skill describes one-time setup and repeatable steps, with human checkpoints at key stages (funding results, qualification, and contact lists).
# Funding Signal Outreach Detects recent funding events across a set of companies, qualifies them against your company's context, finds the right people to reach out to, and drafts personalized emails. The full chain from signal to outreach-ready. ## When to Auto-Load Load this composite when: - User says "check if any of these companies raised funding", "funding signal outreach", "reach out to recently funded companies" - User has a list of companies and wants to act on funding signals - An upstream workflow (TAM Pulse, company monitoring) triggers a funding signal check ## Architecture This composite is **tool-agnostic**. Each step defines a data contract (what goes in, what comes out). The specific tools that fulfill each step are configured once per client/user, not asked every run. ``` ┌─────────────────────────────────────────────────────────────────┐ │ FUNDING SIGNAL OUTREACH │ │ │ │ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌──────────┐ │ │ │ DETECT │──▶│ QUALIFY │──▶│ FIND │──▶│ DRAFT │ │ │ │ Funding │ │ & Rank │ │ People │ │ Emails │ │ │ └──────────┘ └──────────┘ └──────────┘ └──────────┘ │ │ │ │ │ │ │ │ Input: companies + your company + buyer + signal │ │ Tool: web search c
- When to Auto-Load
- Architecture
- Step 0: Configuration (One-Time Setup)
- Company Source Config
- Signal Detection Config
- Contact Finding Config
- Outreach Config
- Your Company Context
- Step 1: Detect Funding Signals
- Input Contract
- Process
- Output Contract
- Human Checkpoint
- Step 2: Qualify & Prioritize
What does the funding-signal-outreach skill do?
End-to-end funding signal composite. Takes any set of companies, detects recent funding events, qualifies against your company context, finds relevant people (buyers, champions, users), and drafts personalized outreach. Tool-agnostic — works with any company source, contact finder, and outreach platform.
How do I install it?
Run `npx skills add gooseworks-ai/goose-skills --skill funding-signal-outreach --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From gooseworks-ai/goose-skills, a repository with 1,091 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.