Generate sales enablement content (battle cards, one-pagers, demo scripts, objection handlers, proposal sections) that equips sales teams with competitive intelligence and deal-closing tools from portfolio data. Use this skill when the user asks to 'create a battle card', 'one-pager', 'demo script', 'objection handling', 'sales collateral', 'proposal section', 'competitive comparison', 'sales enablement', 'arm the sales team', or wants decision-stage internal content for deal support — even if they don't say 'sales enablement' explicitly.
From cogni-marketingnpx claudepluginhub cogni-work/insight-wave --plugin cogni-marketingThis skill is limited to using the following tools:
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Generate internal-facing content that equips sales and consulting teams with the intelligence, scripts, and tools they need to close deals. Sales enablement sits at the decision stage — the prospect is evaluating specific solutions and the sales team needs competitive differentiation, objection responses, and deal-specific materials.
| Parameter | Required | Description |
|---|---|---|
| market | Yes | Market slug |
| gtm_path | Yes | GTM path theme ID |
| format | No | battle-card, one-pager, demo-script, objection-handler, proposal-section. If omitted, ask |
marketing-project.json — brand, languagesources.enriched_portfolio_narratives exists in marketing-project.json, read the market-level and persona-level customer narratives for this market. These contain pre-written buyer-facing language that strengthens objection handlers and one-pagers with tested messaging. Especially useful for the "When we win" sections in battle cards.Structure:
| Dimension | Us | Competitor |
|------------------|-----------------------|----------------------|
| Core approach | [IS statement] | [Their positioning] |
| Key advantage | [DOES statement] | [Their advantage] |
| Customer value | [MEANS statement] | [Their value claim] |
| Pricing model | [From solutions] | [From compete data] |
| Readiness | [Blueprint readiness] | [Est. maturity] |
Generate one battle card per top competitor (typically 2-3 per market). Use competitor data from competitors/{feature}--{market}.json.
Structure:
Designed for: PDF handout, email attachment, meeting leave-behind.
Structure:
Each segment includes: what to show, what to say, what to emphasize, what to avoid.
Structure — table format:
| Objection | Response | Evidence | When to use |
Generate 8-12 common objections sourced from:
Each response follows: Acknowledge → Reframe → Evidence → Redirect
A drop-in section for sales proposals covering this GTM path:
Write to content/sales-enablement/ with frontmatter.
For battle cards with multiple competitors, use: {market}--{gtm-path}--battle-card--{competitor}.md
Update content-strategy.json.
Generated: {format} ({word_count} words)
File: content/sales-enablement/{filename}
Internal distribution:
- Share battle cards with sales team via CRM or shared drive
- Add proposal sections to proposal template library
- Review objection handlers quarterly (competitors evolve)
Refresh triggers:
- New competitor data → regenerate battle cards
- Updated pricing → regenerate one-pagers and proposal sections
- New TIPS pursuit → refresh trend context in all formats