competitive-positioning

Provides battlecard structure, win/loss analysis patterns, and competitive positioning principles for sales deals.

3|2|Updated Aug 24, 2026
One-click install
npx skills add https://github.com/hero-engine/hero --skill competitive-positioning-hero-engine
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: competitive-positioning
Source: https://github.com/hero-engine/hero/tree/main/domains/sales/skills/competitive-positioning
Command: npx skills add https://github.com/hero-engine/hero --skill competitive-positioning-hero-engine

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Sales teams often lose competitive deals because they lack structured battlecards, honest positioning guidance, and systematic win/loss analysis, leading to stale intel and unprovable claims in front of buyers. ## Core Features & Use Cases - Battlecard Structure: Defines what belongs in a battlecard (proof points, trap questions, deal signals, references) and what does not (unverifiable claims, stale data), plus a 90-day maintenance cadence. - Positioning Principles: Five principles covering outcome-based positioning, honest acknowledgment of competitor strengths, provable claims, letting prospects surface competitors, and leveraging champions. - Win/Loss Pattern Analysis: A process for recording competitive debriefs, updating battlecards, and tracking per-competitor metrics like win rate, deal cycle, and loss reasons. - Use Case: A rep discovers a competitor in an active evaluation, loads the battlecard, runs trap questions in discovery, secures a switch reference, and updates the battlecard with new intel after the deal closes. ## Quick Start Ask the competitive-intel agent to produce a deal-specific competitive brief for the competitor named in your active evaluation.

Frequently Asked Questions about competitive-positioning

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a sales battlecard for a competitor?▼

A battlecard should include where you genuinely win with proof points, where the competitor wins honestly, what they say about you with your response, trap questions, deal signals, and references from customers who switched. Exclude unverifiable claims and outdated information.

How to run win/loss analysis on closed sales deals?▼

After each closed competitive deal, record which competitors were present, what was said on both sides, and the outcome. Update the battlecard with new intel, and surface patterns appearing across three or more deals as playbook notes with win-rate data.

What metrics should I track for competitive deals?▼

Track win rate against each competitor, average deal cycle length, the top three loss reasons, the top three win reasons, and the stage at which you typically detect the competitor in the deal.

When should I mention a competitor in a sales conversation?▼

Never name a competitor the prospect has not raised, since it risks introducing new options and looking defensive. Wait for the prospect to surface them, then ask discovery questions about how far along the evaluation is.

How often should battlecards be updated?▼

Review a battlecard whenever the competitor appears in a deal and update it with any new intel learned. Run a scheduled review every 90 days and flag battlecards not updated in over 90 days as stale.