skills/pipeline/SKILL.md
Deal-level coaching with diagnosis, stakeholder strategy, and next-step recommendations. Use when user says "help with this deal", "deal is stalled", "how to close", "competitive deal", "multi-thread", "deal coaching", or mentions a specific stuck deal.
npx skillsauth add octavehq/lfgtm pipelineInstall 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.
Deal-level coaching and strategy. Diagnose stalled deals, plan multi-threading, counter competitive threats, engage executives, and generate deal-specific next steps — all informed by your library's Motion ICP narratives and real conversation data.
/octave:pipeline [mode] <account> [--contact <email>] [--competitor <name>]
/octave:pipeline # Interactive - describe the deal
/octave:pipeline stalled acme.com # Deal is stuck
/octave:pipeline multi-thread acme.com # Expand to more stakeholders
/octave:pipeline competitive acme.com --competitor "Acme" # Competitor entered the deal
/octave:pipeline executive acme.com # Need executive engagement
/octave:pipeline close acme.com # Final stage strategy
/octave:pipeline expand acme.com # Customer expansion / upsell
When the user runs /octave:pipeline:
If no mode specified, ask:
Tell me about the deal. What's happening?
DEAL CHALLENGES
1. Stalled - Deal has gone quiet or lost momentum
2. Multi-thread - Need to engage more stakeholders
3. Competitive - A competitor has entered or is threatening
4. Executive - Need to get executive buy-in
5. Close - Deal is in final stages, need to close
6. Expand - Existing customer, upsell/cross-sell opportunity
7. Other - Describe the situation
Your choice:
Then gather context:
A few more details:
1. Account: [company name or domain]
2. Primary contact: [name or email, if known]
3. Deal stage: [Where is it in your pipeline?]
4. How long at this stage: [days/weeks]
5. What happened last: [last interaction or event]
6. Any other context: [budget, timeline, blockers]
# Enrich the company
enrich_company({ companyDomain: "<domain>" })
# Qualify the company
qualify_company({ companyDomain: "<domain>" })
# Research the primary contact
enrich_person({
person: {
email: "<email>",
companyDomain: "<domain>"
}
})
# Qualify the contact
qualify_person({
person: {
email: "<email>",
companyDomain: "<domain>"
},
additionalContext: "This is an active deal. Evaluate persona fit and likely buying role."
})
# Check for conversation history
list_events({
startDate: "<365 days ago>",
filters: {
companyDomains: ["<domain>"]
}
})
# Get findings from past interactions
list_findings({
query: "objections pain points next steps commitments",
startDate: "<365 days ago>",
eventFilters: {
companyDomains: ["<domain>"]
}
})
# Match to Motion ICP cell for this deal's persona × segment
list_motions() # find the Motion for the offering being sold (and motion type, e.g. NET_NEW)
list_motion_icps({ motionOId: "<motion_oId>" }) # see the persona × segment matrix
find_motion_icp({ motionIcpOId: "<motion_icp_oId>", includeLearnings: true }) # full cell narrative + Learning Loop learnings
# If a Custom Motion Playbook (COMPETITIVE / MILESTONE / ACCOUNT / THEMATIC) is more relevant:
list_motion_playbooks({ motionOId: "<motion_oId>" })
get_motion_playbook({ motionPlaybookOId: "<mp_oId>" })
# Get competitive intel if relevant
search_knowledge_base({
query: "<competitor name or signals>",
entityTypes: ["competitor"]
})
# Get proof points for this situation
search_knowledge_base({
query: "<company industry> <deal stage> results",
entityTypes: ["proof_point", "reference"]
})
See mode-stalled-output.md for the Stalled Deal mode output template.
See mode-multi-thread-output.md for the Multi-Thread mode output template.
See mode-competitive-output.md for the Competitive mode output template.
See mode-executive-output.md for the Executive Engagement mode output template.
Generate appropriate coaching for closing or expansion scenarios following the same pattern: diagnosis, strategy, specific actions, messaging, and follow-ups.
Always end with actionable next steps:
What would you like to do next?
1. Draft the recommended email/message
2. Generate full call prep for next meeting
3. Research a specific stakeholder
4. Get competitive intelligence
5. Analyze past conversations for patterns
6. Create a deal-specific one-pager
7. Done
enrich_company - Account intelligenceenrich_person - Stakeholder researchqualify_company - ICP fit assessmentqualify_person - Persona matchingfind_person - Stakeholder discoverylist_events - Conversation and deal historylist_findings - Extracted insights from interactionsget_event_detail - Deep dive into specific interactionssearch_knowledge_base - Competitors, proof points, referenceslist_motions / list_motion_icps / find_motion_icp - Pull the Motion ICP cell for this deal's persona × segment (Strategic narrative, Pains and consequences, Benefits and impacts, Methodology, References, plus Learning Loop learnings)list_motion_playbooks / get_motion_playbook - Pull Custom Motion Playbooks (COMPETITIVE, MILESTONE, ACCOUNT, THEMATIC) when a specific angle fits the deal better than the Default Motion Playbookgenerate_email - Outreach and follow-up draftsgenerate_content - Talk tracks, one-pagers, executive messaginggenerate_call_prep - Meeting preparationNo Conversation History:
No previous interactions found with [Company].
I'll base coaching on your library intelligence and general deal patterns. As you log calls and emails, coaching will get more contextual.
Contact Not Found:
Couldn't find [contact] at [Company].
Options:
- Provide their email or LinkedIn
- I'll search for stakeholders at the company
- Proceed with company-level coaching
No Matching Motion ICP:
No Motion ICP cell matches this deal's persona × segment perfectly.
Using closest match: [Motion ICP cell] If this is a recurring scenario, consider creating a Custom Motion Playbook (
THEMATIC,MILESTONE,ACCOUNT, orCOMPETITIVE) layered on the relevant Motion:/octave:library create motion-playbook
/octave:research - Deep research on any stakeholder/octave:battlecard - Full competitive intelligence/octave:abm - Complete account plan (broader than deal-level)/octave:generate - Quick content generation/octave:wins-losses - Learn from similar deal outcomes/octave:analyzer - Analyze a specific conversation from this dealtools
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.