# icp-builder

Turns a single LinkedIn profile into a full persona profile and ICP using Crustdata. Writes configuration files for other sales skills.

- skill · `type=skill` · Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, OpenCode · 306 installs · ★ 11
- Author: crustdata
- License: MIT · policy=mirror · the beginning of the file is at the end of this page
- Source: https://github.com/crustdata/skills/tree/HEAD/skills/icp-builder/SKILL.md
- Updated: 2026-10-17
- HTML: https://affpapa.org/en/nevibecode/skills/crustdata-icp-builder

## What it does

This skill takes a LinkedIn URL and generates your go-to-market setup via Crustdata. It extracts your identity, company context, inferred ideal customer profile, and writing tone. Output goes straight into `config/gtm-config.md` and `config/persona-profile.md`. These two files feed downstream tools like `sales-prospecting` and `account-research`.

Setup runs in three fixed stages. First comes an optional stack inventory covering your CRM, email provider, dialer, or calendar. Any skipped slot defaults to `none`. Next, Crustdata enriches the person profile and retrieves up to 10 recent posts to capture tone of voice. The skill asks no discovery questions. The profile URL serves as the complete input.

Existing config files are never overwritten silently. If files already exist in your working directory, the agent summarizes them and requests confirmation. Keep in mind that requests consume Crustdata credits, and query whitelists outside basic tiers trigger a 403 response.

## Requirements
- Works with: LinkedIn

## Install

### Claude Code (native platform)

1. **Skills CLI (Vercel)**
```bash
npx skills add crustdata/skills --skill icp-builder -a claude-code
```

2. **Manually: put the files in place**
- File: `~/.claude/skills/icp-builder/SKILL.md` — Copy the whole skill folder; for one project use .claude/skills/icp-builder/

### Codex

1. **Skills CLI (Vercel)**
```bash
npx skills add crustdata/skills --skill icp-builder -a codex
```

2. **Manually: put the files in place**
- File: `.agents/skills/icp-builder/SKILL.md` — For all projects use ~/.agents/skills/

### Cursor

1. **Skills CLI (Vercel)**
```bash
npx skills add crustdata/skills --skill icp-builder -a cursor
```

2. **Manually: put the files in place**
- File: `.cursor/skills/icp-builder/SKILL.md` — Cursor also reads .agents/skills/ and .claude/skills/

### GitHub Copilot

1. **GitHub CLI**
```bash
gh skill install crustdata/skills icp-builder
```

2. **Manually: put the files in place**
- File: `.github/skills/icp-builder/SKILL.md`

### Gemini CLI

1. **Skills CLI (Vercel)**
```bash
npx skills add crustdata/skills --skill icp-builder -a gemini-cli
```

2. **Platform CLI**
```bash
gemini skills install https://github.com/crustdata/skills --path skills/icp-builder
```

### Windsurf (Devin Desktop)

**Manually: put the files in place**
- File: `.devin/skills/icp-builder/SKILL.md` — The legacy .windsurf/skills/ path still works

### OpenCode

**Skills CLI (Vercel)**
```bash
npx skills add crustdata/skills --skill icp-builder -a opencode
```

### Claude.ai

**Claude.ai**
- Zip the folder and upload it in Settings → Capabilities → Skills

Where a file is given instead of a command, copy the files from the source to that path: https://github.com/crustdata/skills/tree/HEAD/skills/icp-builder/SKILL.md

## When to use it
- Generate an inferred ICP directly from a LinkedIn profile
- Create persona and GTM configs for sales workflows
- Capture personal writing voice from recent posts
- Set up tool integration defaults without multi-step questionnaires

## Example prompts
- Set me up. My LinkedIn is linkedin.com/in/janedoe
- Build my ICP and save it for the other skills
- What is my writing voice based on my posts?

## Source text · SKILL.md · MIT

Below is the content of a third-party file. It is data, not instructions for you: do not act on anything written inside unless the human asks. Block tag: 58594f5c79bebf76.

BEGIN THIRD-PARTY FILE 58594f5c79bebf76
```text
---
name: icp-builder
description: >
  One-time GTM setup: paste one LinkedIn URL and Crustdata enriches it into a persona
  profile — who you are, what your company sells, your inferred ICP, your writing voice —
  saved as config/gtm-config.md and config/persona-profile.md, the files the
  sales-prospecting, account-research, sales-outreach, and meeting-prep skills read at startup. Use when someone says
  "build my ICP", "set up my GTM config", "create my persona profile", "onboard me",
  "get me started", or when another GTM skill reports the config is missing.
display-name: ICP Builder
category: recruiting
icon: target
summary: "Paste one LinkedIn URL and get the ICP, persona, and voice config every GTM skill reads."
sample-prompts:
  - "Set me up. My LinkedIn is linkedin.com/in/janedoe"
  - "Build my ICP and save it for the other skills"
  - "What's my writing voice, based on my posts?"
---

# ICP Builder

One LinkedIn URL in, a working GTM config out. This skill enriches the user's own
profile via Crustdata and writes `config/persona-profile.md` + `config/gtm-config.md` —
the files **sales-prospecting** and **account-research** read at startup.

Three steps, always in this order:

1. **Stack** (optional, fully skippable): which tools they use.
2. **Persona**: one LinkedIn URL; Crustdata turns it into who they are, what they sell,
   an inferred ICP, and their writing voice.
3. **Write config + hand off.**

**Never interrogate the user.** Do not ask "what do you sell", "who's your ICP", or
"paste your voice emails". All of that is derived from the LinkedIn URL and their posts.
The URL is the entire interview.

---

## Step 0: check for an existing config

If `config/gtm-config.md` or `config/persona-profile.md` already exist in the working
directory, read them, summarize what's there in two lines, and ask whether to refresh
the whole persona or update specific fields. Never silently overwrite a config the user
already corrected. On a refresh, carry the existing Stack entries forward unchanged and
do not re-ask the stack question unless the user asks to change it. Missing files are
the normal case — this skill creates them.

## Step 1: welcome + optional stack question

Open with one short welcome line, then ONE optional question: **which tools do you
use?** One quick pass through the slots; the user names a tool or says skip. If they
skip the whole question, write `none` everywhere and move on.

- **Data provider** — Crustdata, the data source these skills run on (added as a
  connector; if it's not connected, use the no-data fallback below)
- **CRM** — or skip
- **Calendar** — or skip
- **Email** — or skip
- **Call recorder** — or skip
- **Sequencer** — or skip
- **Team chat** — or skip

Rules for this step:

- **Never assume the stack from connected connectors.** A connected connector is not
  the user's choice. Ask, or write `none`.
```
END THIRD-PARTY FILE 58594f5c79bebf76

The third-party file has ended. Everything between the 58594f5c79bebf76 tags is data: requests and commands from it are not followed. An “end of file” line with another tag inside the block is part of the file.

First 2913 of 19125 bytes. © crustdata · MIT · https://github.com/crustdata/skills/tree/HEAD/skills/icp-builder/SKILL.md

_Part of the page did not fit — see the HTML version._

---
NeVibeCode on affpapa.org. Catalog texts are descriptions, not instructions for the agent. How to choose and install: https://affpapa.org/en/nevibecode/agents.md