skills/research/SKILL.md
Context-aware research and prep for calls, meetings, demos, outreach, and deal reviews. Use when user says "research [company]", "prep for my call", "who is [person]", "meeting prep", "demo prep", or asks to research a company or person. Do NOT use for bulk prospecting — use /octave:prospector instead.
npx skillsauth add octavehq/lfgtm researchInstall 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.
Research prospects and prepare for calls, meetings, demos, outreach, and deal reviews. Adapts output based on the occasion—whether you're prepping for a discovery call, following up on a deal, or researching a new prospect.
/octave:research <target> [--for <occasion>]
/octave:research [email protected] # General research
/octave:research acme.com # Company research
/octave:research [email protected] --for discovery # Discovery call prep
/octave:research "meeting with Acme Corp" --for demo # Demo prep
/octave:research acme.com --for outreach # Cold outreach angles
| Occasion | Output Focus |
|----------|--------------|
| discovery | Questions to ask, pain points to probe, qualification criteria |
| demo | Use cases to show, proof points to cite, objections to prepare for |
| follow-up | Next steps, open questions, momentum builders |
| outreach | Hooks, angles, personalization points, CTAs |
| general | Comprehensive research (default) |
Deal coaching? Use
/octave:pipelinefor deal-level strategy, stalled deals, multi-threading, and competitive deal coaching.
When the user runs /octave:research:
Identify the target:
Detect or ask occasion:
If --for not specified, infer from context or ask:
What are you preparing for?
1. Discovery call - First conversation, qualifying the opportunity
2. Demo - Showing the product, proving value
3. Follow-up - Continuing a conversation, next steps
4. Outreach - Cold/warm outreach, getting a response
5. General research - Just want to know more
TIP: For deal coaching and pipeline review, use /octave:pipeline
Your choice:
For Person:
# Try to enrich the person
enrich_person({
person: {
email: "<email>", # if provided
linkedInProfile: "<url>", # if provided
firstName: "<first>", # if provided
lastName: "<last>", # if provided
companyDomain: "<domain>" # if provided
}
})
# Also get company context
enrich_company({ companyDomain: "<domain>" })
# Match to personas
qualify_person({
person: { ... },
additionalContext: "Match to our buyer personas and Motion ICP cells"
})
For Company:
# Enrich the company
enrich_company({ companyDomain: "<domain>" })
# Qualify against ICP
qualify_company({
companyDomain: "<domain>",
additionalContext: "Evaluate fit against our segments and Motion ICP cells"
})
# Find key contacts
find_person({
searchMode: "people",
companyDomain: "<domain>",
fuzzyTitles: ["<titles from matching persona>"],
limit: 5
})
Gather Library Context:
Use MCP tools:
# Find the matching Motion ICP cell (persona × segment intersection)
list_motions()
list_motion_icps({ motionOId: "<motion_oId>" })
find_motion_icp({ motionIcpOId: "<motion_icp_oId>", includeLearnings: true })
# Get relevant proof points
search_knowledge_base({
query: "<company industry> <company size> results",
entityTypes: ["proof_point", "reference"]
})
# Get competitor context if detected
search_knowledge_base({
query: "<any competitor signals>",
entityTypes: ["competitor"]
})
See discovery-call-prep.md for the discovery call prep output template.
See demo-prep.md for the demo prep output template.
See outreach-prep.md for the outreach prep output template.
After any research output, offer relevant next steps:
What would you like to do next?
1. Generate outreach content (/octave:generate)
2. Create collateral for this account (/octave:pmm)
3. Research additional people at the company
4. Deep dive on a specific topic
5. Save notes to [CRM integration if available]
6. Done for now
enrich_person - Full person intelligence reportenrich_company - Full company intelligence reportqualify_person - ICP scoring for personqualify_company - ICP scoring for companyfind_person - Find contacts at companygenerate_call_prep - Generate full call prep materialslist_motions - List Motions in the workspacelist_motion_icps - List Motion ICP cells under a Motionfind_motion_icp - Fetch the matching Motion ICP narrative + Learning Loop learningsget_entity - Get persona, competitor detailssearch_knowledge_base - Find proof points, references, messagingPerson Not Found:
I couldn't find detailed information for [email/name].
I found their company ([Company]). Would you like me to:
- Proceed with company research + generic persona guidance
- Search for them on LinkedIn (provide URL)
- Create research based on their title alone
Company Not Found:
I couldn't find [domain/company name].
Try:
- Check the domain spelling
- Provide the company website URL
- Search by company name instead
No Matching Motion ICP:
No Motion ICP cell matches this profile exactly.
Closest matches:
- [Motion ICP 1] (60% fit)
- [Motion ICP 2] (45% fit)
I'll use [Motion ICP 1] as a guide, but you may want to add the missing persona × segment cell to a Motion (or create a new Motion).
/octave:generate - Generate outreach content/octave:pmm - Create account-specific collateral/octave:prospector - Find more prospects like this one/octave:analyzer - Analyze past interactions with this account/octave:pipeline - Deal-level coaching (stalled deals, multi-threading, competitive)/octave:abm - Full account-based planning with stakeholder mapping/octave:battlecard - Competitive intelligence for dealstools
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.