shipshitdev/startup-icp-definer
bundles/startup/skills/startup-icp-definer/SKILL.md
Use this skill when users need to define their ideal customer profile, identify target personas, map buying centers, or understand who they're selling to. Activates for "who is my customer," "define ICP," "target audience," or persona questions.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library startup-icp-definerInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 8, 2026, 5:12 AM34.3s3 files scanned
SKILL.md
- name:
- startup-icp-definer
- description:
- Use this skill when users need to define their ideal customer profile, identify target personas, map buying centers, or understand who they're selling to. Activates for "who is my customer," "define ICP," "target audience," or persona questions.
- version:
- 1.0.0
- tags:
- business, hexa, icp, customer, persona, targeting, b2b
Startup ICP Definer - Ideal Customer Profile Builder
Overview
Help indie founders precisely define who they're building for using Hexa's Opportunity Memo methodology. Execute rigorous customer definition by guiding users through buying center mapping, pain point hierarchies, and validation frameworks.
Hexa's Core Principle: "Define the company type + the buying center people involved in the decision-making process."
When This Activates
- "Who is my customer"
- "Define my ICP"
- Target audience questions
- Customer personas
- "Everyone could use this"
- "Who should I target first"
The Framework: ICP Stack
┌─────────────────────────────────────────┐
│ BUYING CENTER │
│ (All people in the decision) │
├─────────────────────────────────────────┤
│ USER PERSONA │
│ (Who uses it daily) │
├─────────────────────────────────────────┤
│ BUYER PERSONA │
│ (Who signs the check) │
├─────────────────────────────────────────┤
│ COMPANY PROFILE │
│ (The organization) │
└─────────────────────────────────────────┘
Build from bottom up: Company → Buyer → User → Buying Center.
Quick Workflow
Step 1: Company Profile
- Industry/vertical
- Company size (employees/revenue)
- Stage (startup, growth, enterprise)
- Geography
- Tech stack
Step 2: Buyer Persona
- Title/role, seniority
- Goals and KPIs
- Decision authority
- What they care about (cost, time, risk)
Step 3: User Persona
- Daily workflow
- Pain points
- Tech savviness
Step 4: Buying Center Map
- Champion, Economic Buyer, Technical Evaluator
- End User, Influencer, Blocker
Step 5: Pain Hierarchy
Score: Urgency + Cost + Frequency + Actively Solving Focus on pains scoring 8+
The 50-Company Test
Before finalizing ICP:
- List 50 specific companies that fit
- Find buyer's name at 20 of them
- Reach out to 10
If you can't do this, your ICP isn't specific enough.
Too Broad Warning Signs
- Can't name 50 specific companies
- Can't find 10 people to interview
- Messaging must be vague to apply
- Sales conversations feel scattered
Integration
idea-validator- Validate the problemmarket-sizer- Size the segmentleads-researcher- Find matching companiesoffer-architect- Design offer for ICPoutbound-optimizer- Write outreach
For complete persona canvases, buying center maps, interview questions, pain hierarchy scoring, fit scoring framework, and output templates, see: references/full-guide.md
Related Skills
shipshitdev/typescript-refactor
development
VerifiedTrustedCommunity
TypeScript refactoring and modernization guidelines from a principal specialist perspective. This skill should be used when refactoring, reviewing, or modernizing TypeScript code to ensure type safety, compiler performance, and idiomatic patterns. Triggers on tasks involving TypeScript type architecture, narrowing, generics, error handling, or migration to modern TypeScript features.
30SKILL.mdUpdated Jul 14, 2026
shipshitdev/typescript-expert
tools
VerifiedTrustedCommunity
Resolves TypeScript and JavaScript problems across type-level programming, performance, monorepo management, migration, and modern tooling. Invoke when diagnosing "type instantiation excessively deep" errors, migrating JS to TS, configuring strict tsconfig, debugging module resolution, or choosing between Biome/ESLint/Turborepo/Nx.
30SKILL.mdUpdated Jul 14, 2026
shipshitdev/turborepo
tools
VerifiedTrustedCommunity
Turborepo monorepo build system guidance. Triggers on: `turbo.json`, task pipelines, `dependsOn`, caching, remote cache, the `turbo` CLI, `--filter`, `--affected`, CI optimization, environment variables, internal packages, monorepo structure, and package boundaries. Use when the user configures tasks or workflows, creates packages, sets up a monorepo, shares code between apps, runs changed packages, debugs cache behavior, or works in an `apps/` plus `packages/` workspace.
30SKILL.mdUpdated Jul 14, 2026
shipshitdev/tailwind
tools
VerifiedTrustedCommunity
Provides Tailwind CSS v4 performance optimization and best practices guidelines. Triggers when writing, reviewing, or refactoring Tailwind CSS v4 code; when working with Tailwind configuration, @theme directive, utility classes, responsive design, dark mode, container queries, or CSS generation optimization.
30SKILL.mdUpdated Jul 14, 2026