Files
pm-claude-skills/exports/cursor/pm-gtm/competitor-teardown/competitor-teardown.mdc
T
mohitagw15856 05b6d799f0 SkillCheck validator, Cursor exports, and per-agent installers (#27)
Three more learnings from alirezarezvani/claude-skills, applied:

1. SkillCheck validator (scripts/skillcheck.mjs) — validates every SKILL.md
   against the authoring standard (frontmatter, name/folder match, trigger +
   produces clauses, required headings) plus tier referential integrity.
   Errors fail CI; --strict fails on warnings too. New skillcheck.yml workflow
   and a SkillCheck status badge in the README. Current: 0 errors / 14 advisory
   warnings across 172 skills.

2. Cursor export platform — build-exports.mjs now generates
   exports/cursor/<bundle>/<skill>/<skill>.mdc rule files. The PLATFORMS
   registry now supports per-skill filenames (file as a function).

3. Per-agent installers — scripts/install.sh unifies install for
   claude/hermes/codex/openclaw/cursor (--link, --target, --dry-run, --list).
   Curl-able one-liners codex-install.sh, openclaw-install.sh, and
   cursor-install.sh clone the library and install in a single command.

README documents the one-line installs and Cursor exports; CHANGELOG and the
authoring standard updated.


Claude-Session: https://claude.ai/code/session_016JWn5jRD5tcEFKrubjQ6Px

Co-authored-by: Claude <noreply@anthropic.com>
2026-06-17 13:38:31 +01:00

87 lines
4.2 KiB
Plaintext
Raw Blame History

This file contains ambiguous Unicode characters
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
---
description: "Produce a structured competitive analysis for any product or market. Use when asked for a competitor analysis, competitive teardown, market comparison, SWOT, or positioning map. Generates a structured teardown with positioning map, feature comparison, messaging gaps, and strategic recommendations."
globs:
alwaysApply: false
---
# Competitor Teardown Skill
This skill produces a complete competitive analysis document — structured for use in strategy decks, investor materials, sales enablement, or product planning sessions.
## Required Inputs
Ask the user for these if not provided:
- **Your product** (name + one-line description)
- **Competitors to analyse** (list 25 names; if not provided, ask)
- **Analysis depth** (quick overview / detailed teardown)
- **Primary use case for this analysis** (e.g. sales enablement, investor deck, internal strategy, product planning)
## Output Structure
### 1. Competitive Landscape Overview
One paragraph summarising the market dynamic: who the key players are, how the market is segmented, and where the white space sits. Keep this under 150 words — it's the exec summary.
### 2. Positioning Map
Describe a 2x2 positioning map in text form (since you can't render images):
- Define the two axes relevant to this market (e.g. "Ease of Use vs. Depth of Features" or "Price vs. Enterprise Readiness")
- Place each competitor in one quadrant with a one-sentence rationale
- Place the user's product and highlight the strategic implication
### 3. Feature Comparison Table
| Feature / Capability | [Your Product] | [Competitor A] | [Competitor B] | [Competitor C] |
|---|---|---|---|---|
| [Feature] | ✅ / ❌ / 🟡 Partial | | | |
Use ✅ (has it), ❌ (doesn't have it), 🟡 (partial/limited). Add a "Strategic Notes" column for features where the difference is a significant selling point or risk.
Include 1015 rows. If user hasn't provided feature details, note which cells need to be verified.
### 4. Messaging Analysis
For each competitor, analyse their public-facing messaging (website headline, tagline, primary value prop):
**[Competitor Name]**
- **Their primary claim:** [what they say they do]
- **Target audience signal:** [who they seem to be targeting based on language/imagery]
- **Emotional hook:** [fear / aspiration / authority / speed / simplicity]
- **Gap or weakness in their messaging:** [what they don't address that your product could own]
### 5. SWOT Summary
Produce a clean SWOT for the user's product in the context of this competitive landscape:
- **Strengths:** [23 genuine differentiators]
- **Weaknesses:** [23 honest gaps or vulnerabilities]
- **Opportunities:** [23 market gaps or competitor weaknesses to exploit]
- **Threats:** [23 competitor moves or market shifts to watch]
### 6. Strategic Recommendations
35 actionable recommendations based on the analysis. Frame each as: **"Given [observation], [your product] should [action] to [outcome]."**
## Quality Checks
- [ ] Axes on positioning map are meaningful and specific to this market
- [ ] Feature table includes strategic notes on key differentiators
- [ ] Messaging analysis covers all named competitors
- [ ] SWOT is honest — Weaknesses and Threats should not be softened
- [ ] Recommendations are specific and actionable, not generic strategy advice
## Anti-Patterns
- [ ] Do not mark feature presence as equivalent across competitors without noting quality differences — both products may have "reporting" while one's is meaningfully better
- [ ] Do not position the user's product in the most favourable quadrant without justification — a self-serving positioning map that ignores real competitive pressure provides no strategic value
- [ ] Do not soften Weaknesses or Threats in the SWOT — a SWOT that only celebrates strengths is a marketing document, not a strategy tool
- [ ] Do not include unverifiable claims about competitor capabilities without flagging them as assumptions — presenting rumours as facts damages analytical credibility
## Example Trigger Phrases
- "Do a competitor analysis of [Product] vs [Competitor A] and [Competitor B]"
- "Tear down [Competitor]'s positioning"
- "Give me a competitive landscape for [market]"
- "Build a SWOT for our product against [competitor]"