agentleFS
rasulshaikhrasulshaikh/fde-desk/.claude/skills/competitor-teardown/SKILL.md

competitor-teardown

Skill0 starsChanged 48 days agoMITView on GitHub

Produce a focused competitor brief for FDE conversations, not a market encyclopedia. Call-prep when a competitor is named, or when signal-scout sees displacement cues. Do not invent win rates or customer names. Cite public pages or operator notes.

15 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Call-prep when a competitor is named, or when signal-scout sees displacement cues.

    line 7
  2. Distinctive:

    Do not invent win rates or customer names.

    line 19

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Skill: competitor-teardown

Produce a focused competitor brief for FDE conversations, not a market encyclopedia.

When to use

Call-prep when a competitor is named, or when signal-scout sees displacement cues.

Steps

  1. Name the competitor and the displacement hypothesis.
  2. Capture: positioning one-liner, likely champion, landmine objections, proof they win on, proof we win on (operator-supplied only).
  3. List 5 discovery questions that surface the real evaluation criteria.
  4. Note pricing model only if sourced; otherwise mark unknown.
  5. Write ops/<slug>/competitors/<name>.md.

Guardrail

Do not invent win rates or customer names. Cite public pages or operator notes.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.