agentleFS
Kuan-AI-comKuan-AI-com/agent-skills/skills/competitor-analysis/SKILL.md

competitor-analysis

Skill0 starsChanged 6 days agoMITView on GitHub

Analyze and compare competitors of a product or business. Use when the user asks "who are my competitors", "compare us with X and Y", "how do we position against", "competitive landscape", or is setting pricing or positioning for a product.

66 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use seo-project-setup, app-marketing-context and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JwuthriSkill

    seo-project-setup

    Set up a durable local SEO workspace with project context, notes, goals, positioning, preferences, MCP checks, and Search Console data intake.

    Also in 11 projects that use this

  • appeekySkill

    app-marketing-context

    When the user wants to create or update their app marketing context document. Also use when the user mentions "app context", "marketing brief", "app positioning", or when starting any ASO or app marketing project. This is the foundation skill — all other skills check for this context first.

    Also in 6 projects that use this

  • appeekySkill

    metadata-optimization

    When the user wants to optimize App Store metadata — title, subtitle, keyword field, or description. Also use when the user mentions "optimize my title", "ASO metadata", "keyword field", "character limits", "app description", or "write my subtitle". For keyword discovery, see keyword-research. For full ASO audits, see aso-audit.

    Also in 6 projects that use this

  • JwuthriSkill

    openseo-release-notes

    Cut an OpenSEO release — bump the version, draft user-facing release notes from commits since the last tag, run a review + subagent-verification pass, and open a "release: vX.X.X" PR. Use when the user asks to prepare a release, bump the version, or write release notes.

    Also in 6 projects that use this

  • akii-technologies-ltdSkill

    keyword-clustering

    Cluster and organize keywords into topical groups for SEO. Use when the user asks to "cluster keywords", "group keywords", "organize keywords", "keyword mapping", "topic clusters", "keyword grouping", "build a content plan", "pillar pages", "topical authority", "semantic clustering", or pastes a list of keywords.

    Also in 11 projects that use this

  • MicrosoftSkill

    competitive-landscape

    Use when a branch manager asks something like \"Who are we up against in each metro\"

    Also in 11 projects that use this

  • +5 more from Jwuthri
  • +1 more from appeeky

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 55 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Not found -> n/a, never a guess.

    line 22
  2. Distinctive:

    Do not copy competitors' marketing claims as facts ("the #1 platform").

    line 47
  3. Distinctive:

    Keep the user's product row honest: fill it from what the user told you, not from assumptions.

    line 48

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

1. Pin down the product

Product, target customer, market/country and price range. Ask if missing; the competitor set depends on all four.

2. Pick competitors

  • Direct: same customer, same job, similar price. Up to 6; fewer is fine if the market is small.
  • Alternatives: what customers use instead (spreadsheets, an agency, hiring someone, doing nothing). At least one.
  • Include competitors the user names even if you would not pick them.
  • Without web access: list only companies you are confident exist, mark the whole analysis "from model knowledge, verify before use", and leave prices blank. Never invent a company, price or feature.

3. Gather per competitor (with source URL and date for each)

  • Who they sell to (from their homepage, case studies, customer logos)
  • Pricing: plan names, entry price, billing unit (per seat, per usage), free tier/trial. "Contact sales" is a valid answer.
  • The 3 things they lead with on the homepage (their claimed positioning)
  • Customer voice: recurring praise and complaints from review sites (G2, Capterra, Trustpilot, app stores), Reddit or forums. Only patterns seen in several reviews, with one short example quote and link. Not found -> n/a, never a guess.

4. Table

UsComp AComp B...
Target customer
Entry price
Pricing model
Leads with
Praised for
Complaints
Source / date

5. Gaps (each backed by evidence from step 3)

  • Complaints that recur across competitors and nobody fixes.
  • Customer segments served badly (too expensive, too complex, wrong language or region).
  • Price points nobody covers. Separate evidence from your inference.

6. Recommendation

  • One positioning statement: "For [customer] who [need], [product] is the [category] that [difference], unlike [main alternative]." The difference must come from a gap in step 5.
  • The 2-3 risks: which competitor could copy it fastest and why.

Rules

  • Date the analysis at the top; prices and plans change.
  • Do not copy competitors' marketing claims as facts ("the #1 platform"); attribute them.
  • Keep the user's product row honest: fill it from what the user told you, not from assumptions.

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.