competitive-intel

Overview of competitive-intel skill

What competitive-intel is for

competitive-intel is a Claude skill for structured competitive analysis, competitor tracking, battlecard creation, win/loss review, and market positioning. It is designed for teams that need intelligence to drive decisions, not just collect competitor facts. The skill is especially relevant for CMO positioning work, CRO sales enablement, CPO roadmap tradeoffs, and founders comparing their product against alternatives.

Best-fit users and decisions

The competitive-intel skill fits users who already have a product, market, ICP, or competitor set in mind and need a repeatable way to turn scattered evidence into usable outputs. Use it when you need to identify direct, indirect, and future competitors; build a sales-ready battlecard; analyze why deals are won or lost; summarize a competitor’s recent moves; or create a competitive positioning map. It is less useful if you only want a quick web summary with no decision attached.

What makes this skill different

The repository supports a 5-layer competitive intelligence workflow rather than a single generic “analyze this competitor” prompt. Its useful assets include references/ci-playbook.md, which lists practical OSINT sources such as pricing pages, changelogs, job posts, review sites, ad libraries, keyword tools, founder interviews, and funding databases. It also includes templates/battlecard-template.md, which helps convert research into sales language with strengths, weaknesses, proof points, objections, and talk tracks.

When competitive-intel may be the wrong choice

Do not use competitive-intel as a substitute for verified market research, legal review, or private-source intelligence gathering. It works best with public information, customer evidence, sales notes, product data, and clearly stated assumptions. If your goal is confidential surveillance, scraping restricted sources, or making high-stakes claims without evidence, this skill should not be used without stronger governance and source validation.

How to Use competitive-intel skill

competitive-intel install and first files to read

Install the skill in your Claude skills environment with:

npx skills add alirezarezvani/claude-skills --skill competitive-intel

After installation, start with SKILL.md to understand the trigger phrases and supported deliverables. Then read references/ci-playbook.md for source ideas and research discipline. If your main output is for sales, open templates/battlecard-template.md early; it shows the structure the skill expects for a useful battlecard, including competitor strengths, real weaknesses, differentiated advantages, objection handling, traps to avoid, and proof points.

Inputs that produce better competitive-intel usage

The skill performs best when you provide context before asking for analysis. Strong inputs include your company name, product category, ICP, geography, pricing model, sales motion, known competitors, recent win/loss notes, customer objections, and the decision you need to make.

Weak prompt:

Build a battlecard for Competitor X.

Stronger prompt:

Use competitive-intel to build a sales battlecard for Competitor X. We sell B2B workflow automation to mid-market finance teams in the US. Our main differentiators are faster implementation and native ERP integrations. Prospects usually compare us on price, security, and reporting depth. Use public sources where possible, separate evidence from assumptions, and give sales-ready objection responses.

Practical competitive-intel guide workflow

A reliable workflow is: define the decision, identify the competitor set, collect evidence, classify competitors, analyze strengths and weaknesses, then convert findings into an output format. For landscape work, ask for direct, indirect, and future competitors separately so budget alternatives are not missed. For battlecards, require proof for each claimed advantage. For win/loss analysis, provide deal notes and ask the skill to group reasons by pattern rather than anecdote.

For recurring tracking, ask for a compact update format:

Track recent moves by Competitor X over the last quarter. Focus on pricing, product launches, hiring signals, messaging changes, partnerships, and customer complaints. Return source-linked findings, likely strategic intent, and implications for product, marketing, and sales.

Prompt patterns for Competitive Analysis outputs

Use deliverable-specific prompts. For positioning, request axes and justification, not just a 2x2 chart. For feature gaps, ask the skill to distinguish “missing feature,” “weaker implementation,” and “not strategically important.” For sales enablement, ask for talk tracks that acknowledge competitor strengths instead of dismissing them. This matters because the included battlecard template explicitly warns against wishful weaknesses and unsupported claims.

competitive-intel skill FAQ

Is competitive-intel only for sales battlecards?

No. Battlecards are one of the clearest outputs, but competitive-intel for Competitive Analysis can also support market maps, competitor identification, win/loss patterning, positioning strategy, feature gap review, and executive summaries. The best output depends on the decision: sales teams need objection handling, product teams need roadmap implications, and marketing teams need messaging contrast.

How is this better than an ordinary competitor prompt?

A normal prompt often produces a broad summary that sounds plausible but is hard to act on. The competitive-intel skill gives Claude a more specific operating model: identify competitor types, use public intelligence sources, connect findings to business decisions, and format outputs like battlecards. The extra value is not magic data access; it is better structure, source awareness, and decision-ready framing.

Can beginners use the competitive-intel skill?

Yes, but beginners should start with a narrow request. Instead of asking for a full market intelligence program, begin with one competitor and one output, such as a battlecard or recent-moves summary. The skill’s template helps new users avoid common mistakes like inventing weaknesses, over-indexing on feature lists, or ignoring indirect competitors that compete for the same budget.

Does competitive-intel provide real-time data?

The skill itself does not guarantee real-time access. Results depend on the model environment, connected browsing tools, and the evidence you provide. For current analysis, include fresh links, screenshots, notes from sales calls, review excerpts, pricing page captures, changelog entries, or dated research. Always ask the skill to label source dates and separate verified facts from inferred strategy.

How to Improve competitive-intel skill

Improve competitive-intel outputs with evidence

The most important upgrade is better source material. Provide customer quotes, CRM loss reasons, Gong or call summaries, pricing notes, implementation feedback, review snippets, and links to competitor pages. Ask the skill to tag each claim as verified, inferred, or unknown. This prevents polished but unsupported competitive narratives from entering sales or executive materials.

Avoid common competitive analysis failure modes

Common failure modes include treating all competitors as direct competitors, listing features without buyer relevance, exaggerating your advantage, ignoring competitor strengths, and turning battlecards into attack sheets. A better instruction is: “Be fair to the competitor, identify where they genuinely win, and only recommend positioning claims we can prove.” This improves trust with sales teams and executives.

Iterate from first draft to usable asset

Do not expect the first output to be final. After the initial draft, ask follow-up questions such as: “What claims need evidence?”, “Which objections are risky?”, “What should sales never say?”, “Which weaknesses are based on customer data versus assumption?”, and “What changes if the buyer is enterprise instead of mid-market?” This turns competitive-intel from a research summary into an operating asset.

Customize templates for your market

The included templates/battlecard-template.md is a strong starting point, but teams should adapt it to their sales process and category. Add fields for deal stage, buyer persona, compliance needs, pricing sensitivity, integration requirements, and proof assets. For product teams, add roadmap implications and feature parity notes. For marketing teams, add message testing hypotheses and landing page comparison angles.