skills/icp-refine/SKILL.md
Analyze deal outcomes and conversation patterns to refine ICP definitions and targeting criteria. Use when user says "refine ICP", "who should we target", "update our ICP", "ideal customer profile", or asks why deals are being won or lost.
npx skillsauth add octavehq/lfgtm icp-refineInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Analyze deal outcomes, conversation patterns, and qualification scores to refine your ICP definitions. Compares what your library says your ideal customer looks like against what actually wins — then recommends updates.
/octave:icp-refine [--period <days>] [--segment <name>] [--focus wins|losses|both]
/octave:icp-refine # Full ICP analysis (last 180 days)
/octave:icp-refine --period 90 # Last quarter
/octave:icp-refine --segment "Enterprise" # Specific segment
/octave:icp-refine --focus wins # Only analyze what's working
/octave:icp-refine --focus losses # Only analyze what's not working
When the user runs /octave:icp-refine:
If no options specified, use defaults and confirm:
I'll analyze your deal data to refine your ICP.
Period: Last 180 days (change with --period)
Segments: All (change with --segment)
Focus: Wins and losses
Starting analysis...
# Get current segments (this IS the ICP definition)
list_all_entities({ entityType: "segment" })
# Get full segment details
get_entity({ oId: "<segment_oId>" }) // for each segment
# Get current personas
list_all_entities({ entityType: "persona" })
get_entity({ oId: "<persona_oId>" }) // for key personas
# Get products/services (what we're selling)
list_all_entities({ entityType: "product" })
list_all_entities({ entityType: "service" })
# Get won deals
list_events({
startDate: "<period start>",
filters: {
eventTypes: ["DEAL_WON"]
}
})
# Get lost deals
list_events({
startDate: "<period start>",
filters: {
eventTypes: ["DEAL_LOST"]
}
})
# Get findings from won deals
list_findings({
query: "why we won success factors decision criteria champion",
startDate: "<period start>",
eventFilters: {
outcomeFilters: ["WON"]
}
})
# Get findings from lost deals
list_findings({
query: "why we lost objections blockers competition pricing",
startDate: "<period start>",
eventFilters: {
outcomeFilters: ["LOST"]
}
})
# Get positive conversation signals
list_findings({
query: "excited interested positive resonated value",
startDate: "<period start>",
eventFilters: {
sentiments: ["POSITIVE"]
}
})
# Get negative signals
list_findings({
query: "concerned hesitant not a fit wrong timing",
startDate: "<period start>",
eventFilters: {
sentiments: ["NEGATIVE"]
}
})
For each won deal, extract:
For each lost deal, extract:
See refinement-report-template.md for the full ICP refinement report template.
# Update segment
update_entity({
entityType: "segment",
oId: "<segment_oId>",
instructions: "<specific updates based on findings>"
})
# Update persona
update_entity({
entityType: "persona",
oId: "<persona_oId>",
instructions: "<specific updates>"
})
# Update Motion Playbook narrative sections (Strategic narrative, Pains and consequences, Benefits and impacts, etc.)
# for the Motion ICP cell that corresponds to the refined persona × segment.
update_motion_playbook({
motionPlaybookOId: "<motion_playbook_oId>",
instructions: "Update Strategic narrative and Pains and consequences for the [persona] × [segment] Motion ICP based on ICP refinement findings: [evidence]"
})
# Create new persona if recommended
create_entity({
entityType: "persona",
name: "<new persona name>",
instructions: "<details from deal analysis>"
})
What would you like to do next?
1. Deep dive on a specific finding
2. Analyze a specific segment or persona
3. Compare current quarter vs. previous
4. Update a specific library entity
5. Generate updated enablement materials
6. Export the full report
7. Done
list_all_entities - Segments, personas, productsget_entity - Full entity details for ICP definitionlist_events - Won/lost dealslist_findings - Conversation insights, objections, signalsget_event_detail - Deep dive into specific dealsupdate_entity - Update segments, personasupdate_motion_playbook - Edit Motion Playbook narrative sections (Strategic narrative, Pains and consequences, Benefits and impacts, etc.) for a Motion ICP cellcreate_entity - New personas or segmentslist_motions - List Motions in the workspacelist_motion_icps - List Motion ICP cells (persona × segment) for a Motionfind_motion_icp - Fetch a Motion ICP cell narrative + Learning Loop learningssearch_knowledge_base - Cross-reference patternsNo Deal Data:
No deal outcomes found in the last [N] days.
ICP refinement requires win/loss data. Options:
- Extend the time period (try --period 365)
- Review conversation data instead (calls/emails without deal outcomes)
- Do a manual ICP review using your library definitions
Insufficient Data:
Found only [N] deals. Statistical patterns may not be reliable.
I'll highlight patterns but flag low-confidence findings. Consider extending the period or combining with qualitative analysis.
No Segments Defined:
No segments found in your library.
I can still analyze deal patterns, but there's nothing to compare against. Consider creating segments first:
/octave:library create segmentOr I'll suggest segment definitions based on the deal data.
/octave:wins-losses - Deeper win/loss analysis (complements ICP refinement)/octave:insights - Field intelligence trends/octave:prospector - Use refined ICP to find new prospects/octave:audit - Check library health after updates/octave:library - Manually update entitiestools
Capture a brand's visual design system from its website and build a reusable component kit. Walks key pages on a domain (screenshots + HTML via the Octave scrape tool), derives design tokens (colors, type, spacing, radius, shadow), and produces a minimal component library (buttons, cards, headers, stats, tables, badges, hero, footer) as a self-contained HTML reference plus CSS tokens. Use when the user says "get brand components", "capture the brand", "build a component kit for <domain>", "make outputs look like <company>", or wants other skills to generate on-brand HTML for a target company.
tools
Define, run, and manage multi-step GTM workflows with human-in-the-loop execution. Use when user says "run a workflow", "show workflows", "create a workflow", "automate this process", or references workflow-based tasks.
development
Analyze won and lost deals for patterns, insights, and actionable learnings. Use when user says "win/loss analysis", "why did we lose", "deal patterns", "win themes", or asks about deal outcome trends. Do NOT use for visual HTML reports — use /octave:win-loss-report instead.
development
Generate visual win/loss analysis reports as self-contained HTML with CSS-based charts and data visualizations. Use when user says "win/loss report", "deal report", "visual analysis", or wants a formatted HTML version of deal outcome analysis. Do NOT use for text-based deal analysis — use /octave:wins-losses instead.