Skill Market

competitive battlecard

Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'

GitHub
githubcommunityagent-skill-repositoryagent-skillsagentic-skillsclaude-code-marketplaceclaude-code-pluginsclaude-cowork-plugin
0.0
0 installs26.6K GitHub starsby phuryn

Skill Introduction

Overview
Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'

Core value

Turns reusable Development know-how into an installable skill, helping users complete github, community, agent-skill-repository, agent-skills work faster.

Target users

  • Developers, testers, and maintainers who handle Development tasks in Focus Code.
  • Teams that already trust workflows or content from phuryn.
  • Users who want standardized prompts, steps, or conventions instead of repeating setup work.

Best practices

  • Read the skill content first to confirm required inputs, expected outputs, and dependencies.
  • Try it on a small task before relying on it for critical work.
  • Add project-specific constraints such as coding style, target platform, test expectations, and delivery format.
  • For external sources, verify the source link, version, and recent maintenance activity.

Best use cases

  • Tasks related to github, community, agent-skill-repository, agent-skills that need a reusable execution flow.
  • Converting a community repo, team convention, or personal workflow into day-to-day assistance.
  • Starting from a proven skill instead of writing prompts or procedures from scratch.

Limits and boundaries

  • Results depend on the quality of the original skill content and may need human correction.
  • It does not replace code review, tests, security review, or professional judgment.
  • External tools, APIs, account permissions, and local dependencies still need separate setup.

Differentiation

  • Structured around Development, making it easier to discover and reuse than loose prompt snippets.
  • Marked as GitHub, which helps users judge trust and maintenance expectations.
  • Keeps the original source link available for repository, documentation, or discussion follow-up.
  • Tagged with github, community, agent-skill-repository, agent-skills, so it can be filtered by concrete task intent.

Install and use

Install
Copy Install Command
focus install competitive-battlecard-26f515
View source

Detail Preview

SKILL.md

Primary filemarkdown3 KB

name: competitive-battlecard description: "Create sales-ready competitive battlecards comparing your product against a specific competitor — positioning, feature comparison, objection handling, and win/loss patterns. Use when preparing sales teams, creating competitive materials, or responding to 'why not competitor X?'"

Competitive Battlecard

Create a concise, sales-ready battlecard for use against a specific competitor.

Context

You are creating a competitive battlecard for $ARGUMENTS.

Use web search to research the competitor's current product, pricing, positioning, and recent changes. If the user provides files (feature lists, win/loss data, sales call notes), read them first.

Instructions

  1. Research the competitor (use web search):

    • Current product offerings and features
    • Pricing tiers and model
    • Target market and positioning
    • Recent product launches or changes
    • Known strengths and weaknesses
    • Customer reviews and sentiment (G2, Capterra, Reddit)

  2. Create the battlecard with these sections:

    Company Overview

    • Founded, HQ, funding/revenue (if public)
    • Target market and ICP
    • Positioning in one sentence

    Quick Comparison

    CapabilityUsThemWinner
    [Feature area 1][Our approach][Their approach][Us/Them/Tie]
    [Feature area 2].........
    Pricing.........
    Support.........

    Where We Win

    • [Advantage 1]: [Proof point or customer quote]
    • [Advantage 2]: [Specific capability they lack]
    • [Advantage 3]: [Better approach with reasoning]

    Where They Win

    • [Their strength 1]: [Our counter-positioning]
    • [Their strength 2]: [How we mitigate this gap]

    Common Objections & Responses

    Prospect SaysRespond With
    "Competitor X has [feature]""[Our alternative approach and why it's better for them]"
    "They're cheaper""[Value framing: total cost of ownership, ROI, hidden costs]"
    "They're more established""[Our advantages: speed, innovation, focus, support]"

    Landmines to Plant

    Questions to ask the prospect that highlight competitor weaknesses:

    • "How important is [area where we excel] to your team?"
    • "Have you evaluated [specific capability they lack]?"

    Win/Loss Patterns

    • We tend to win when: [pattern]
    • We tend to lose when: [pattern]
    • Key differentiator in competitive deals: [what tips the scale]

  3. Keep it scannable: Sales reps need to reference this during calls. Use tables, bold text, and short bullets.

Save as markdown. Format for easy printing or sharing in Notion/Confluence.

Further Reading

Reviews

Overall rating

0.0
0.0

0 comments

No reviews yet