agentleFS
letscooktech-studioletscooktech-studio/outcomelab/skills/competitor-analyzer/SKILL.md

competitor-analyzer

Skill7 starsChanged 6 days agoMITView on GitHub

Analyze direct, adjacent, and substitute competitors using verifiable evidence. Use for positioning, pricing, feature strategy, market-entry research, win/loss review, or identifying strategic whitespace.

5 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

1 rule. 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    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:

    Do not infer revenue, users, or roadmap from weak signals.

    line 26

“Common” is measured: kept by at least 6 in 10 of the 3 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

Competitor Analyzer

Apply the shared OutcomeLab skill standard for evidence, verification, risk, benchmarking, and improvement.

Build a decision-ready view of customer alternatives, not a feature checklist.

Workflow

  1. Define the buyer, job, geography, segment, and decision context; include “do nothing” and internal build as competitors.
  2. Assemble dated, attributable evidence from product docs, pricing, changelogs, customer reviews, demos, and interviews.
  3. Compare alternatives across job completion, switching cost, distribution, integration depth, pricing metric, trust, and defensibility.
  4. Identify gaps that buyers demonstrably value; distinguish a temporary feature gap from a durable wedge.
  5. Recommend one positioning claim, one proof mechanism, and one experiment per opportunity.

Output contract

Return a market definition, evidence ledger, competitor matrix, battlecards, opportunity ranking (demand, differentiation, reachability, execution cost, durability), and a recommendation. Attach a source and date to each external claim.

Quality gates

  • Do not infer revenue, users, or roadmap from weak signals.
  • Flag stale pricing and feature evidence.
  • Include disconfirming evidence for the favored strategy.
  • Say “unknown” rather than manufacturing precision.

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.