competitive-battlecard

competitive-battlecard is a skill for Claude Code from killvxk/pm-skills-zh. It costs 77 tokens per session (848 once invoked), scanned A, original, MIT.

A guide for making a competitive battlecard: a short reference that compares your offering with a named competitor for sales conversations.

In plain words
What is it for?
Use it to create a concise Markdown battlecard with comparisons, responses to common objections, discovery questions, and competitive lessons.
Why use it?
It organizes current competitor research, pricing, positioning, strengths, weaknesses, objections, and win-or-loss patterns in one place.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution.

Part of the pm-go-to-market plugin — 6 skills, 3 commands shipped together

Good fit Use it to create a concise Markdown battlecard with comparisons, responses to common objections, discovery questions, and competitive lessons.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/killvxk/pm-skills-zh/competitive-battlecard
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add killvxk/pm-skills-zh --skill competitive-battlecard
Clone the repo
git clone --depth 1 https://github.com/killvxk/pm-skills-zh

Made for: Claude Code.

Or install pm-go-to-market, the plugin that ships this one along with the rest of its 6 skills, 3 commands.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for competitive-battlecard

README.md
[![agentmods](https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/competitive-battlecard/github.svg)](https://agentmods.dev/skills/killvxk/pm-skills-zh/competitive-battlecard)
Your own site
<a href="https://agentmods.dev/skills/killvxk/pm-skills-zh/competitive-battlecard"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/competitive-battlecard/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for competitive-battlecard

Your own site · 80×15
<a href="https://agentmods.dev/skills/killvxk/pm-skills-zh/competitive-battlecard"><img src="https://agentmods.dev/badge/skills/killvxk/pm-skills-zh/competitive-battlecard.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 77 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 848 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00077 $0.00848
Opus 5 $0.00039 $0.00424
Sonnet 5 $0.00015 $0.00170
Haiku 4.5 $0.00008 $0.00085

Measured 11d ago against content hash ef2ed59a136c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

competitive-battlecard scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

pm-go-to-market/skills/competitive-battlecard/SKILL.md · 78 lines

What it actually says

竞争作战卡

为特定竞争对手制作一份简洁、可直接用于销售的竞争作战卡。

背景

你正在为 $ARGUMENTS 制作竞争作战卡。

使用网络搜索调研竞争对手的当前产品、定价、定位和近期动态。如果用户提供了文件(功能清单、赢单/败单数据、销售通话记录),请先阅读这些材料。

操作指引

  1. 调研竞争对手(使用网络搜索):

    • 当前产品功能和产品线
    • 定价层级和模式
    • 目标市场和产品定位
    • 近期产品发布或功能变化
    • 已知优势和劣势
    • 用户评价和口碑(G2、Capterra、Reddit)
  2. 按以下结构制作竞争作战卡

    公司概况

    • 成立时间、总部、融资/营收(如为公开信息)
    • 目标市场和 ICP(理想客户画像)
    • 一句话定位

    快速对比

    能力维度 我们 他们 优势方
    [功能领域 1] [我们的方案] [他们的方案] [我们/他们/持平]
    [功能领域 2] ... ... ...
    定价 ... ... ...
    支持服务 ... ... ...

    我们的优势所在

    • [优势 1]:[佐证材料或客户引言]
    • [优势 2]:[他们所不具备的具体能力]
    • [优势 3]:[更好的方案及理由]

    他们的优势所在

    • [他们的强项 1]:[我们的对位策略]
    • [他们的强项 2]:[我们如何弥补这一差距]

    常见异议与应对话术

    客户说 如何回应
    "竞争对手 X 有 [功能]" "[我们的替代方案及为何更适合他们]"
    "他们更便宜" "[价值框架:总拥有成本(TCO)、ROI、隐性成本]"
    "他们更成熟" "[我们的优势:速度、创新、专注度、支持服务]"

    埋雷问题(Landmines)

    引导潜在客户主动暴露竞争对手弱点的问题:

    • "对你们团队而言,[我们擅长的领域] 有多重要?"
    • "你们评估过 [他们所缺乏的具体能力] 吗?"

    赢单/败单规律

    • 我们倾向于赢单的情况:[规律]
    • 我们倾向于败单的情况:[规律]
    • 竞争商机中的关键差异化点:[能扭转局面的因素]
  3. 保持一目了然:销售代表需要在通话时随时查阅。请使用表格、加粗文字和简短的要点。

保存为 Markdown 格式。适配 Notion/Confluence 中的打印或分享需求。


延伸阅读

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 11d ago First seen · 78 lines · 77 tokens per session scan A ef2ed59a136c

Subscribe to this mod's changes

competitive-battlecard is a skill published in the GitHub repository killvxk/pm-skills-zh (159 stars, last pushed 5mo ago), licensed MIT. It adds 77 tokens to every session and 848 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens