Competitor Teardown

SKILL.md Preview

---
name: competitor-teardown
description: Use this skill when the user asks Claude to analyze a competitor, reverse-engineer an offer, break down a rival funnel, or figure out what a competitor is doing and how. Trigger when the user mentions studying a competitor, tearing down a launch, or phrases like 'break down what this person is doing.' This skill helps produce a structured teardown report with a confidence label on every claim.
compatibility: Claude.ai, Claude Desktop
---

# Competitor Teardown

## Purpose
Produce a teardown on one fixed structure, with a confidence label on every factual claim, so the analysis is consistent and the user can tell what is verified from what is inferred. The labeling keeps the teardown honest enough to base decisions on.

## When to Use This Skill
Use it to study a competitor's offer, funnel, positioning, or frameworks before adjusting strategy.

## When Not to Use This Skill
Do not use it to fabricate intelligence or to write the user's own copy. Do not present inference as fact.

## Required Inputs
- The competitor and any links or materials available.
- What the user wants to learn (offer, funnel, positioning, frameworks).
- Whether research tools are available to verify claims.

## Workflow
1. Apply a confidence label to every factual claim: Confirmed, Likely, Disputed, or Cannot confirm.
2. Document who they are and their positioning.
3. Document the offer and pricing, then the funnel and traffic.
4. Identify the frameworks and mechanisms they lean on.
5. Assess strengths, weaknesses and gaps, and the takeaways for the user.

## Output Format
Return the teardown: Positioning, Offer and Pricing, Funnel and Traffic, Frameworks and Mechanisms, Strengths, Weaknesses and Gaps, Takeaways. Apply a confidence label inline on each claim, and summarize the highest-confidence takeaways.

## Quality Standards
- Every factual claim carries a confidence label.
- Observation is distinguished plainly from inference.
- If research tools are available, findings are cited; gaps are not filled with assumptions.
- Uses contractions, no em dashes, no hype.

## Edge Cases
If no reliable evidence exists for a claim, label it 'Cannot confirm' and state it as unknown rather than guessing. If sources conflict, label 'Disputed' and present both.

## Safety and Limitations
Do not invent intelligence or scrape private data. Use only available public information, and never present a guess as a confirmed fact.

## Test Prompts
1. Tear down this competitor's $2,000 course launch. Here's their sales page and funnel. I want positioning, offer, frameworks, and where they're weak, with confidence labels.
2. Reverse-engineer how this agency positions and prices against the market. Label what's confirmed versus inferred so I know what I can rely on.
3. Break down this creator's lead funnel and email strategy from what's publicly visible. Be honest about what you can't confirm.

Skill Details

Package Preview

Trigger Phrases

• "Tear down this competitor's $2,000 course launch. Here's their sales page and funnel. I want positioning, offer, frameworks, and where they're weak, with confidence labels."
• "Reverse-engineer how this agency positions and prices against the market. Label what's confirmed versus inferred so I know what I can rely on."
• "Break down this creator's lead funnel and email strategy from what's publicly visible. Be honest about what you can't confirm."