competitive-battlecard
by phuryncompetitive-battlecard helps you create a sales-ready battlecard for one named competitor, covering positioning, feature comparison, objection handling, and win/loss framing. Use it for competitive analysis, sales enablement, and internal prep when you need a practical answer to “why us instead of competitor X?”
This skill scores 78/100 and is worth listing: it gives agents a clear trigger, a concrete deliverable, and a usable workflow for building competitive battlecards. Directory users should find it helpful for sales-prep tasks, though they should expect to supply their own competitor inputs and accept some research-driven variability.
- Explicit trigger guidance for sales/competitive scenarios, including when to use it.
- Operational workflow is clear: research competitor data, then produce a structured battlecard with comparison, wins, and objections.
- Good agent leverage from a well-scoped output format that is more actionable than a generic prompt.
- No scripts, references, or support files, so the agent must rely on web research and the skill text alone.
- The skill assumes external research and user-provided materials but does not spell out edge-case handling or verification steps.
Overview of competitive-battlecard skill
The competitive-battlecard skill helps you create a sales-ready competitive battlecard for one named competitor, with practical positioning, feature comparison, objection handling, and win/loss framing. It is best for sales enablement, product marketing, and competitive analysis teams that need a usable answer to “why us instead of competitor X?” not just a generic summary.
The main value of the competitive-battlecard skill is that it forces a decision-oriented output: what the competitor sells, where you win, where they win, and what proof to use in front of buyers. That makes it more useful than a broad prompt when you need a consistent internal asset fast.
It is a good fit when the battlecard must reflect current market reality, because the workflow expects web research plus any customer files you provide. It is a weaker fit if you only need a high-level market landscape or if you do not have a specific competitor name.
What competitive-battlecard is for
Use competitive-battlecard for a single-competitor artifact that supports live selling, objection handling, and team training. The output should help a rep respond with confidence, not just describe the market.
Who should install it
Install the competitive-battlecard skill if you work on sales enablement, competitive intelligence, product marketing, or founder-led sales and need a repeatable way to turn research into a battlecard. It is especially useful when the same competitor comes up often enough that a reusable structure pays off.
What makes it different
competitive-battlecard is opinionated about research inputs and output structure. It asks for current competitor data, highlights strengths and weaknesses, and organizes the result around buyer-facing decisions, which improves the competitive analysis workflow compared with a freeform prompt.
How to Use competitive-battlecard skill
Install competitive-battlecard
Use the directory install flow for the skill:
npx skills add phuryn/pm-skills --skill competitive-battlecard
After install, open SKILL.md first. In this repository, that file is the source of truth for the competitive-battlecard usage flow.
Start with the right input
The skill works best when you give it a specific competitor and, if possible, any internal context that changes the comparison. Strong inputs look like this:
Create a competitive-battlecard for HubSpot against Salesforce. Use our sales notes, win/loss comments, and product one-pager.
Better inputs include:
- competitor name and product line
- your company or product name
- target segment or ICP
- known objections from reps
- files with feature gaps, pricing notes, or call excerpts
Read these files first
For competitive-battlecard guide work, start with:
SKILL.mdfor the required workflow and section structure- any attached source files from your workspace, especially sales notes or win/loss data
This repository does not expose extra helper folders, so there is no need to hunt through scripts or reference packs before you begin.
Best workflow for the skill
- Define the competitor and your comparison context.
- Let the skill research current product, pricing, positioning, and recent changes.
- Feed in internal evidence if you have it, especially objections and customer language.
- Review the draft for accuracy on pricing, packaging, and feature claims.
- Tighten the “where we win” and “how to answer objections” sections so the battlecard is usable in live deals.
The biggest quality jump usually comes from supplying real internal proof instead of asking the model to infer everything from public sources.
competitive-battlecard skill FAQ
Is competitive-battlecard only for sales teams?
No. The competitive-battlecard skill is also useful for product marketers, founders, and competitive analysts who need a concise competitive analysis artifact. Sales teams benefit most, but the structure also works for internal strategy work.
Does competitive-battlecard replace ordinary prompts?
It usually performs better than an ordinary prompt when you need a reusable sales battlecard because it pushes the model toward research, comparison, and objection handling. If you only need a one-off paragraph about a competitor, a normal prompt may be enough.
Is competitive-battlecard beginner-friendly?
Yes, if you already know which competitor you are targeting. The main beginner risk is under-specifying the comparison, which leads to vague output. Give the skill a named competitor, your product context, and any internal documents you trust.
When should I not use it?
Do not use competitive-battlecard when you need broad market mapping, category strategy, or multi-competitor scoring across an entire landscape. It is designed for one competitor at a time, with enough detail to support sales conversations.
How to Improve competitive-battlecard skill
Give it harder evidence, not just opinions
The fastest way to improve competitive-battlecard output is to supply concrete inputs: pricing pages, feature matrices, win/loss notes, call transcripts, and objection lists. Specific evidence makes the competitive analysis sharper and reduces generic filler.
Tell it what matters in the deal
If the buyer cares about implementation speed, compliance, integrations, or price transparency, say so up front. The competitive-battlecard skill can only prioritize the right comparisons if you state which buying criteria actually decide the deal.
Sanity-check the claims
Because the skill uses web research, the most common failure mode is stale or overstated competitive claims. Verify the competitor’s pricing, packaging, and recent launches before sending the battlecard to a sales team.
Iterate toward rep usability
After the first draft, trim anything a rep would not say in a live conversation. Strengthen short proof points, rewrite weak objections into direct answers, and remove sections that do not help someone win the deal with competitive-battlecard.