agentleFS
khadinakbarlabskhadinakbarlabs/competition-analyzer-tracker/skills/competitive-battlecards/SKILL.md

competitive-battlecards

Skill0 starsChanged 33 days agoMITView on GitHub

Create source-linked sales battlecards, competitor profiles, positioning matrices, SWOT analyses and feature comparisons from verified competitive research. Use for competitive enablement, sales objections and differentiation. Separate advertised claims and observed evidence from hypotheses; keep balanced strengths and fit.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. mvfernando/founder-sales-skills★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository6 other files it gives its agents.

The file

Files
SKILL.md

Competitive battlecards

Convert accepted competitor research into a compact, balanced decision aid. Start from existing profiles, prices, reviews and SEO evidence. Do not recollect every source for a writing-only task. If fresh facts are required, route to the smallest collection skill and execution.md.

Use report-templates.md. For each direct rival include buyer/use-case fit, advertised positioning, supported capabilities, comparable offer details, defensible strengths, evidence-backed limitations, discovery questions and objection responses. Each material factual statement needs a dated source. A vendor feature claim is a claim; "not found in our sample" is unknown, not proof of absence.

Cross-check claims against relevant contrary evidence. Distinguish the target's established advantages from proposed differentiation hypotheses. If the target's own capability is unverified, use a neutral discovery question instead of asserting it wins. Do not invent testimonials, customer names, market share, revenue, growth or product tests.

For a feature matrix, define the same use case and acceptance criterion for every product. Use supported, partial, advertised, unknown or verified absent only where the evidence supports that label. Explain the research basis. Positioning maps are qualitative interpretations with stated axes; they are not measured rankings. SWOT recommendations must cite the underlying observation and give a test or owner action.

Deliver one concise battlecard per important rival and a shared source appendix. Include "when this rival is a good fit" so sales guidance remains credible. Draft external comparison pages or sales messages only when asked; publishing and sending require the specified destination and authorization. Preserve the evidence snapshot date and an update checklist for competitor-tracking.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.