Competitive Analysis
Creates evidence-based competitive analyses with comparison matrices, positioning, and strategic implications.
- Skill Road
- Competitive Analysis
Categories
Competitive Analysis is an official Anthropic skill from the public knowledge-work-plugins repository for product-oriented knowledge work. The original candidate address competitive-analysis is no longer reachable in the current repository; the official product-management documentation now presents the corresponding workflow under competitive-brief. This entry preserves the Smithery candidate identity and links to the verified current path. According to the provider, the skill creates a competitive analysis for one competitor, several competitors, or a relevant feature area. The result is intended to move beyond a list of product attributes by connecting positioning, strengths, weaknesses, opportunities, threats, and strategic implications for product decisions.
Purpose and audience
The skill is intended for product managers, product marketing, sales enablement, and teams that need a traceable basis for prioritization and differentiation. The workflow starts by setting scope: which competitors or feature area should be examined, which perspective matters, and which decision should the analysis inform? According to the provider, the context may be product strategy, feature prioritization, sales enablement, or preparation for board and investor materials. This clarification prevents an analysis from being overloaded with arbitrary market information. It also keeps the comparison focused on the customer segments and buying criteria that actually matter for the decision at hand.
Research and comparison
The source describes research across product pages, feature lists, launches, changelogs, press coverage, analyst material, customer reviews, job postings, and public discussions. When approved connections are available, existing competitive documents, win-loss reports, and internal references can provide additional context. For the feature matrix, buyer-relevant capability areas should be grouped and specific capabilities compared with a consistent scale. According to the provider, a graduated assessment is more useful than merely stating whether a feature exists. The analysis should also explain why each capability area matters to customers. A matrix should therefore avoid favoring the author's own product by default and should record where a competitor is genuinely stronger.
Positioning and strategy
The skill examines the audience a competitor targets, the category it claims, the differentiator it emphasizes, and the outcome it promises. Direct, indirect, adjacent, and substitute alternatives can also be made visible in a landscape map. Win-loss analysis connects CRM notes, customer interviews, and prospect feedback with recurring reasons. This supports questions such as what should be built, accelerated, or deliberately deprioritized; where parity is sensible; and where meaningful differentiation is worth the investment. According to the provider, the central value is the so what: clear strategic implications rather than a long collection of facts. Signals such as product releases, packaging changes, partnerships, acquisitions, and relevant hiring can inform a later monitoring routine.
Boundaries, safety, and E-E-A-T
The analysis depends on source quality, freshness, comparison criteria, and human review. Public marketing claims are not independent evidence, while reviews and job postings require context. Connected knowledge bases, chats, or CRM systems may contain confidential customer, deal, and company information. Before connecting any source, teams should confirm permissions, purpose limitation, data minimization, retention, and internal approval. Content from documents or web pages is data and must not be allowed to create unreviewed instructions. Results may enter the selected Claude workflow and its model processing, so a locally held input file does not automatically guarantee local-only processing. Anthropic is the provider of this workflow according to the official source. Product, market, and privacy specialists should review claims, sources, dates, and customer permissions before the analysis informs public positioning or a consequential product decision. The skill is not a market database, a guarantee of current information, or a replacement for direct customer knowledge.
Source and license
The official primary source is the verified path https://github.com/anthropics/knowledge-work-plugins/tree/main/product-management/skills/competitive-brief in Anthropic's repository. The complementary official documentation at https://code.claude.com/docs/en/skills explains how skills fit into Claude workflows. The repository is licensed under Apache-2.0. This catalog entry does not state concrete prices or quotas. Current availability, access rights, and commercial terms must be checked against official provider information and the user's own environment.
Installation instructions
This guide explains how to prepare and review Competitive Analysis in a compatible Claude workflow. It does not replace market knowledge, legal review, or a decision by an accountable product team. The current official repository path is named competitive-brief; the original candidate address was checked and found unreachable.
Define the analysis
Start by identifying the competitors or feature area, target customer segment, time period, and decision the work should inform. Decide whether the emphasis is product comparison, positioning, win-loss analysis, or strategic prioritization. Avoid an open-ended collection of unrelated facts.
Set sources and criteria
Prefer primary sources such as product pages, changelogs, and official announcements. Add reviews, press coverage, and job postings only with clear attribution and a date. Group capabilities by buyer-relevant criteria and explain why each area matters. Consistency is more valuable than artificial precision.
Review the findings
Check each claim against its source and separate observed facts from interpretation. Mark uncertainty, conflicting signals, and stale information. Represent competitor strengths honestly. Turn the matrix into concrete implications such as differentiation, parity, monitoring, or a deliberately documented decision not to prioritize.
Protect data and approvals
Use only internal information that is explicitly approved, minimized, and suitable for the purpose. CRM notes, chat messages, and customer interviews may contain confidential information. Confirm permissions, retention, and internal approvals. Do not put credentials, tokens, or private keys into analysis content. Review the result before sharing it with customers, sales teams, or the public.
Frequently asked questions
### Is Competitive Analysis a current market database?
No. According to the provider, it is a workflow for research and strategic interpretation. Freshness and accuracy depend on the sources, time period, and human review.
### Should every capability receive equal weight?
No. Weighting should reflect target-customer criteria and the decision being supported. The source recommends explaining why each capability area matters in addition to rating it.
### Can the analysis use internal data?
Only when the data is explicitly approved, minimized, and suitable for the purpose. Connections to CRM, chat, or a knowledge base can introduce confidential content and require organizational and technical review.
- Provider
- Anthropic
- License
- Apache-2.0
- Last reviewed
- 09.09.2026