agentleFS
alexzhu0alexzhu0/agent-ready-skills/skills/competitive-research-brief/SKILL.md

competitive-research-brief

Skill0 starsChanged 5 months agoMITView on GitHub

Use when summarizing competitor research, product pages, feature comparisons, sales notes, or market observations into a concise brief with positioning, gaps, claims, and watch items.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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:

    Use when competitor material needs to become evidence-backed positioning or roadmap input.

    line 14
  2. Distinctive:

    Do not use when the task requires live market claims that have not been sourced or dated.

    line 15
  3. Distinctive:

    Create a watchlist for claims that need follow-up.

    line 29
  4. Distinctive:

    Every strong claim has evidence or is marked unverified.

    line 45

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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

Competitive Research Brief

Purpose

Turn scattered competitor notes into a grounded research brief for product, sales, or strategy.

Fit

  • Use when competitor material needs to become evidence-backed positioning or roadmap input.
  • Do not use when the task requires live market claims that have not been sourced or dated.

Inputs

  • Competitor notes, pages, screenshots, feature lists, pricing notes, or sales feedback.
  • Target market, customer segment, and current product positioning if available.
  • Claims that need verification.

Workflow

  1. Separate observed facts from interpretation.
  2. Identify competitor strengths, gaps, target users, and likely positioning.
  3. Compare only features or claims supported by evidence.
  4. Highlight risks for sales, roadmap, or messaging.
  5. Create a watchlist for claims that need follow-up.

Output

Produce Markdown with:

  • Research Snapshot
  • Competitor Positioning
  • Feature And Claim Comparison
  • Product Gaps
  • Strategic Risks
  • Watchlist
  • Open Questions

Validation

  • Every strong claim has evidence or is marked unverified.
  • Pricing and availability are dated when possible.
  • The brief avoids hype and attack language.
  • Gaps distinguish customer impact from internal preference.
  • Watch items are actionable.

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.