Skill

competitor-teardown

read a competitor's public surface and write the honest version

A dated read of one competitor: what they say in their own words, what they demonstrably ship, and what was verified against what was only claimed. Run it before positioning work or any claim about how you differ.

structure generate skill competitor-teardown

Skill — competitor-teardown

Invoke in any agent conversation with /competitor-teardown. The steps below are a starting opinion, and they are what runs — edit them until they describe the read this company would trust.

When to use. When a competitor ships something that came up twice, before positioning work, and before any claim about how we are different.

Steps.

Name them, date the read, and list the surfaces you actually looked at. A teardown is only as good as its date.
What they say they do — quoted, in their words, not summarized into ours.
What they demonstrably ship: pricing, docs, changelog, the trial if there is one. Separate what you verified from what they claim.
Where they are better. Write this section first and finish it honestly; a teardown that finds nothing is a morale exercise.
Where we are different. Different, not better — "better" needs evidence, and this is where it gets named.
The one thing this changes for us, or "nothing, and here is why". Both are real answers; a page of implications is not.
File it dated in the department's records. It will go stale, and the date is what keeps it honest.

---
type: skill
name: competitor-teardown
description: read a competitor's public surface and write the honest version
standing: draft
owner: "{{owner}}"
updated: "{{date}}"
---

# Skill — competitor-teardown

_Invoke in any agent conversation with `/competitor-teardown`. The steps below are a starting
opinion, and they are what runs — edit them until they describe the read this company would trust._

**When to use.** When a competitor ships something that came up twice, before positioning work, and
before any claim about how we are different.

**Steps.**

1. Name them, date the read, and list the surfaces you actually looked at. A teardown is only as
   good as its date.
2. What they say they do — quoted, in their words, not summarized into ours.
3. What they demonstrably ship: pricing, docs, changelog, the trial if there is one. Separate what
   you verified from what they claim.
4. Where they are better. Write this section first and finish it honestly; a teardown that finds
   nothing is a morale exercise.
5. Where we are different. Different, not better — "better" needs evidence, and this is where it
   gets named.
6. The one thing this changes for us, or "nothing, and here is why". Both are real answers; a page
   of implications is not.
7. File it dated in the department's records. It will go stale, and the date is what keeps it
   honest.

type: skill
name: competitor-teardown
about: "A dated read of one competitor: what they say in their own words, what they demonstrably ship, and what was verified against what was only claimed. Run it before positioning work or any claim about how you differ."
version: "0.1.0"