Agent skill · data analytics · onewave-ai
icp-deep-scanner
Deep-scan any tools you connect (CRM, email, support, reviews, analytics, billing, database) to produce a data-grounded Ideal Customer Profile and a reusable persona library. Read-only by default. Use when you need to define or refresh your ICP, build buyer personas from real data instead of guesses, or generate the persona inputs that the customer-panel-of-experts and prospect-panel-simulator skills consume.
Why this skill is useful
Adds executable scripts for deep scanning and aggregating data from various tools to create a data-driven Ideal Customer Profile.
What it needs
Requires bash, glob, grep installed locally. About 4k tokens when loaded. Last updated 2026-07-15. 242 stars on the source repository.
What this skill does
ICP Deep Scanner Turn the data already sitting in your connected tools into a rigorous, evidence-backed Ideal Customer Profile (ICP) and a library of buyer personas. Most ICPs are invented in a slide deck. This one is reverse-engineered from your actual best customers, your won/lost deals, your support tickets, and your reviews — then written so it can drive real decisions and feed the panel skills. This skill is the data layer beneath customer-panel-of-experts, prospect-panel-simulator, and product-launch-war-room. Run it first; those skills read the persona library it writes. Operating principles (read first) Read-only by default. You may query and read connected sources. You must NOT create, update, delete, send, or move anything in any connected tool unless the user explicitly asks in this session. Before any write or outbound action, stop and confirm. Least data necessary. Pull aggregates and representative samples, not entire databases. You are building a profile, not exfiltrating a CRM. PII minimization. Persona artifacts are archetypes, not dossiers. Do not write real customer names, emails, phone numbers, or account IDs into the output files. Reference real records only as anonymized counts and quotes (quotes scrubbed of identifying detail). Secrets via environment only. Never read, print, or write credentials. Assume tokens live in environment variables (e.g. $SUPABASETOKEN, $OPENAIAPIKEY) or in the MCP connection itself. If a source needs auth that isn't present, list it under "Sources I could not reach" and continue. Cite the evidence. Every claim in the ICP must trace to a source. "Buyers are mostly ops leaders" is worthless; "14 of the last 20 closed-won champions held an Operations title (CRM, trailing 12 mo)" is usable. Step 1 — Inventory connectable sources Ask the user which tools to scan, or detect what's available. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills onewave-ai/icp-deep-scanner