GTM-as-code: a backend-free Claude plugin that finds B2B accounts matching your ICP, then enriches, classifies and scores them into a prioritized target list for outreach — grounded on your own corpus, bring your own keys.
Judge ICP fit for an enriched account, grounded on your corpus, then score it deterministically.
Find ICP-fit companies from a natural-language brief (Perplexity, with no-key fallbacks).
Enrich a B2B account with firmographics (Apollo-first, no-key local fallback).
Build the GTM hand-off: a ranked CSV + per-account markdown dossier across every scored account.
Find contacts in a qualified account — map ICP personas to real people via Apollo (no-key persona-target fallback).
Judge whether an enriched account fits the ICP, grounded on your own knowledge corpus (won-deal patterns, positioning, case studies) rather than a generic prompt. Emits a pass/fail verdict per hard gate and a graded score per dimension, then runs a deterministic scorer to produce a 0-100 fit score and an A/B/Nurture/Reject tier. Use after enrich.
Find companies that fit an ICP from a natural-language brief — the front of the pipeline. Perplexity-grounded web research when a key is configured, with a no-key DuckDuckGo fallback and a deterministic seed-list path. Writes one account per company so enrich/classify/score/people pick them up unchanged.
Enrich a B2B account before ICP classification — firmographics (industry, size, revenue, location) plus deep intent signals scraped from the company website, careers/jobs pages, and GitHub. Apollo-first for firmographics when APOLLO_API_KEY is set; signals need no paid key. Use after discover, or directly on accounts the user supplies.
Build the GTM hand-off — aggregate every scored account into a ranked CSV (one row per account, tier then score) plus a markdown dossier (gates, score breakdown, intent signals with evidence, hiring board, and contacts). Run after accounts have been scored (and ideally had people resolved). No keys.
Find the right contacts inside a qualified account — map the ICP's buying personas (CPO, CTO, Head of Data, …) to real people via Apollo's people-search API. Apollo-first when APOLLO_API_KEY is set; without a key it returns the persona targets (the titles to pursue) so the stage is still actionable. Use after an account scores A/B in classify+score.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
This plugin requires configuration values that are prompted when the plugin is enabled. Sensitive values are stored in your system keychain.
k2_api_keyK2 API key sent to the K2 API host as `x-api-key`. Required when k2_api_host is set.
${user_config.k2_api_key}k2_api_hostBase URL of a Knowledge2 corpus API (e.g. https://api.knowledge2.ai). When set, classify/personalize ground their reasoning on your private corpus via the bundled stdio MCP shim. Leave blank to ground on local corpus files instead.
${user_config.k2_api_host}apollo_api_keyApollo.io API key used by the enrich skill (firmographics) and the people skill (contact search), both sync REST. Leave blank to run local: enrich is firmographic-only and people returns persona targets (the titles to pursue) instead of contacts.
${user_config.apollo_api_key}perplexity_api_keyPerplexity API key for the discover skill's internet-grounded account research. Leave blank to disable discovery; you can still enrich/classify accounts you supply directly.
${user_config.perplexity_api_key}GTM-as-code: a backend-free Claude plugin that finds B2B accounts matching your ICP, then enriches, classifies and scores them into a prioritized target list for outreach — grounded on your own corpus, bring your own keys.
Working name. The pipeline runs end to end —
discover → enrich (+ signals) → classify → score → people → list → personalize— from an ICP brief to a ranked, evidence-backed target list with contacts and grounded first-draft outreach.
Most ICP/lead-scoring tools are hosted SaaS that mark up data you already pay
for and score accounts with a generic prompt. gtm-icp flips both:
| Stage | Status | What it does |
|---|---|---|
discover | implemented | Find ICP-fit companies from a brief — Perplexity-grounded, with no-key DuckDuckGo + seed-list fallbacks. |
enrich | implemented | Firmographics (Apollo-first, no-key fallback) + deep intent signals from website, public ATS job boards (Greenhouse/Lever/Ashby), and GitHub — mapped to ICP scoring dimensions. |
classify | implemented | Corpus-grounded ICP verdict — hard gates + graded dimensions → deterministic 0-100 score & A/B/Nurture/Reject tier. |
people | implemented | Apollo people search — map the ICP's buying personas to real contacts per qualified account; no-key persona-target fallback. |
list | implemented | Aggregate every scored account into a ranked CSV + per-account markdown dossier (gates, signals, contacts) for GTM hand-off. |
personalize | implemented | Draft grounded outreach per contact from the detected signals — deterministic template with no key, rewritten by the model on the same evidence. |
Requires Python 3.10+. From the repo root:
# 1. Discover companies from a seed list (deterministic, no key) — or use
# --brief "<ICP description>" once PERPLEXITY_API_KEY is set.
printf 'Acme Robotics, acme.example\n' > /tmp/seeds.csv
python3 skills/discover/scripts/discover.py --seeds /tmp/seeds.csv
# 2. Enrich a discovered (or supplied) account (local, no paid key)
python3 skills/enrich/scripts/enrich.py --slug acme-example --local
# 2b. Collect deep intent signals — scans the website, public ATS job boards
# (Greenhouse/Lever/Ashby), and GitHub for the ICP's signal keywords
# (e.g. hiring LangChain engineers). No key needed.
python3 skills/enrich/scripts/signals.py --slug acme-example
# 3. Classify is the LLM step — in Claude, run /gtm-icp:classify acme-robotics
# Claude reads enrich.json + icp.criteria.json, grounds on corpus/, and
# writes .gtm/acme-robotics/classify.json. Then score it:
python3 skills/classify/scripts/score.py --slug acme-robotics
# 4. Find contacts in a qualified account (no key -> persona targets; with
# APOLLO_API_KEY -> real contacts mapped to the ICP's personas).
python3 skills/people/scripts/people.py --slug acme-robotics
# 5. Build the hand-off list across every scored account ->
# .gtm/_report/accounts.csv + .gtm/_report/dossier.md
python3 skills/list/scripts/build_list.py
# 6. Draft grounded outreach per contact (no-key template; in Claude,
# /gtm-icp:personalize acme-robotics then rewrites it on the same evidence).
python3 skills/personalize/scripts/personalize.py --slug acme-robotics
Per-account artifacts land in .gtm/<slug>/; the hand-off CSV + dossier land in
.gtm/_report/ (all git-ignored). See skills/_shared/artifact-structure.md.
Installed as a plugin, the stages are slash commands:
/gtm-icp:discover <ICP brief | --seeds path> — find ICP-fit companies/gtm-icp:enrich <company | domain | account.json>/gtm-icp:classify <slug>/gtm-icp:people <slug> — find contacts in a qualified account/gtm-icp:list [--include-reject] — build the ranked CSV + dossier hand-off/gtm-icp:personalize <slug> — draft grounded outreach for an account's contacts/gtm-icp:pipeline <ICP brief | company | accounts.json> — runs discover→enrich→classify→score→people→list→personalize end to endnpx claudepluginhub knowledge2-ai/gtm-icp --plugin gtm-icpComprehensive UI/UX design plugin for mobile (iOS, Android, React Native) and web applications with design systems, accessibility, and modern patterns
Standalone image generation plugin using Nano Banana MCP server. Generates and edits images, icons, diagrams, patterns, and visual assets via Gemini image models. No Gemini CLI dependency required.
Multi-model consensus engine integrating OpenAI Codex CLI, Gemini CLI, and Claude CLI for collaborative code review and problem-solving.
Write feature specs, plan roadmaps, and synthesize user research faster. Keep stakeholders updated and stay ahead of the competitive landscape.