cold-iq/coldiq-marketplace-skills/icp-personas

Claude Code and agent skill by cold-iq/coldiq-marketplace-skills

Trust tier 3
  • community
Source check pending

Checking that the SKILL.md file is still in the repository.

Define the ICP, size and tier an ABM target-account list, and map the buying committee — the strategy layer before list-building and enrichment. Use when defining an Ideal Customer Profile and scoring criteria, deciding how many accounts to target for a revenue goal, tiering accounts (A/B/C/D), mapping personas/buying committee (champion, economic buyer, end user, technical evaluator), or planning persona-based messaging. Triggers on "ICP", "ideal customer profile", "who to target", "scoring criteria", "ABM accounts", "how many accounts", "account tiering", "buying committee", "persona mapping", "champion", "economic buyer", "revenue reverse-engineering". Do NOT use for actually sourcing companies/contacts (see apollo-search / coldiq-search-enrich), scoring math on an export (see tam-scoring), or writing copy (see crawford-method / cold-email-copy).

Install

npx vskill@latest install cold-iq/coldiq-marketplace-skills/icp-personas

SKILL.md

ICP, Accounts & Personas

The strategy layer: decide WHO to target, HOW MANY, and WHICH people inside each account — before you spend credits sourcing and enriching. Mostly methodology; a few steps source data from ColdIQ.

ColdIQ Marketplace Endpoints (where strategy touches data)

TaskMethodPathCreditsEndpoint IDNotes
Validate filter values (ICP criteria)POST/v1/limadata/references/autocompletefreelimadata.references.autocompleteConfirm titles/industries exist
Size the addressable marketPOST/v1/ai-ark/companiesper resultai_ark.companies.searchHow many fit the ICP
Layer intent for prioritizationGET/v1/signalbase/funding-signalsunknownsignalbase.funding_signalsBump in-market accounts
Map the buying committeePOST/v1/limadata/prospect/employees25limadata.prospect.employeesFind personas at an account

1. Define the ICP (3 layers + scoring)

  • Firmographic: industry, employee size, revenue, geography, growth, funding stage.
  • Technographic: tech stack, CRM, marketing automation, competitor tools.
  • Behavioral/intent: hiring, funding, leadership changes, content engagement, website visits.

Reverse-engineer from your best 10–20 closed-won customers. Score 100 pts (example weights): industry 20 · size 15 · revenue 15 · geography 10 · tech fit 15 · growth 10 · intent 15. Tiers: A 90–100 (1:1 ABM) · B 70–89 (1:few) · C 50–69 (programmatic) · D <50 (exclude).

Validate your criteria translate to real filter values before sizing: → POST /v1/limadata/references/autocomplete · free · limadata.references.autocomplete

(Hand the scoring rules to tam-scoring to run on an actual export.)

2. Size & select the account list (ABM)

Revenue reverse-engineering — work backward from the target through funnel benchmarks: Identified→Aware 55% · Aware→Interested 32% · Interested→Considering 18%. (e.g. $1M ARR target ≈ ~3,367 accounts identified.)

Check how many companies actually fit before committing: → POST /v1/ai-ark/companies · per result · ai_ark.companies.search

4-layer selection: firmographic fit · technographic indicators · CRM intelligence (closed-lost, lost-to-competitor, churned) · lookalike modeling from best customers. Then prioritize the in-market ones: → GET /v1/signalbase/funding-signals · ? cr · signalbase.funding_signals (unverified)

Track stage progression: Identified → Aware → Interested (5+ clicks / 10+ engagements) → Considering (site visits, content, demo interest).

3. Map the buying committee

RoleFunctionBudget priority
ChampionInternal advocate driving evaluation40–50%
Economic BuyerSigns the check; cares about ROI20–30%
End UserDaily user; cares about UX/workflow15–20%
Technical EvaluatorIntegration, security, compliance5–10%
Blocker/GatekeeperCan veto, rarely initiatesmonitor

For each persona capture: title patterns + seniority, function, jobs-to-be-done, pains, success metrics, content preference, buying role. Find the actual people once you've defined the personas: → POST /v1/limadata/prospect/employees · 25 cr · limadata.prospect.employees

Messaging matrix: per persona, different JTBD + pain + stage-appropriate content + role-appropriate CTA (champion → demo/ROI, end user → trial/ease-of-use). Hand off to crawford-method / cold-email-copy to write it.

Where this hands off

ICP scoring rules → tam-scoring · sourcing companies/contacts → apollo-search / coldiq-search-enrich · personas-into-ads → ad-audiences · the full build order → campaign-delivery.

Security

  • Security scanPassed, 90 of 100Pattern checks on the skill's files.
  • Model reviewPassed

Quality evaluation

  • Task evaluationNot runNo evaluation yet. Run one in Skill Studio.

Source

Popularity

Repository stars
1
Repository forks
1
7-day trend score
0

Stars and forks are for the whole GitHub repository, not this skill alone. Not refreshed yet.

Works with

Any agent vskill installs to: 56 targets in all. These 39 have a page on this site.

  • Claude Code
  • Cursor
  • GitHub Copilot
  • Windsurf
  • Codex
  • Gemini CLI
  • Cline
  • Amp
  • Roo Code
  • Goose
  • Continue
  • Kilo Code
  • Junie
  • Trae
  • OpenHands
  • Qwen Code
  • AI Agent
  • Tabnine Chat
  • Sourcegraph Cody
  • Amazon Q
  • Firebase Genkit
  • Sweep
  • Devin
  • Phind
  • Mentat
  • Claude Desktop
  • Aider
  • GPT Pilot
  • Plandex
  • bolt.new
  • v0
  • Replit Agent
  • Anse
  • TypingMind
  • BetterChatGPT
  • LibreChat
  • Warp AI
  • Pieces
  • Fig AI
Embed badge
vskill VERIFIED badge
[![vskill VERIFIED](https://verified-skill.com/api/v1/skills/cold-iq/coldiq-marketplace-skills/icp-personas/badge)](https://verified-skill.com/skills/cold-iq/coldiq-marketplace-skills/icp-personas)

Something wrong with this skill or its page? Tell us.