agentleFS
nesnilnehcnesnilnehc/ai-cortex/skills/competitive-research/SKILL.md

competitive-research

Skill8 starsChanged 2 months agoMITView on GitHub

Compare a dated competitor set by capabilities, positioning, pricing, and evidence quality without treating undocumented features as absent.

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 4 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:

    Every non-Unknown matrix cell has an exact source locator and date.

    line 27

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

Purpose

Compare products using consistent criteria and dated evidence. Apply deep-research and preserve the Research Report as the evidence core. This Skill can identify strategic implications, but it does not decide whether to build a product.

Procedure

  1. Fix competitors, category, geography, product edition or plan, comparison criteria and as-of date. Include substitutes where they address the same user job.
  2. Inspect official current product docs, release notes and price pages, then independent implementation evidence or reviews. Attribute marketing claims. Record version, region and plan restrictions.
  3. Build a matrix whose populated cells contain a classification, date and finding ID. Use Unknown when evidence is absent or inaccessible; do not label a feature absent solely because docs are silent. State if pricing is historical, quote-based or unverified.
  4. Compare like with like. Explain gaps caused by edition or regional differences and preserve contradictory sources. Tie any positioning or differentiation inference to specific findings.
  5. Emit a concise narrative and JSON report. Add domain: "competitive" and domain_details only if useful; keep the shared evidence fields intact.

Self-check

Every non-Unknown matrix cell has an exact source locator and date. Contradictory capability claims remain visible. An empty source search never becomes a negative feature claim.

Examples

Comparable editions

Input: compare the current paid plans of two products in one region. Output: produce a dated capability and pricing matrix whose supported cells cite exact official plan pages and finding IDs.

Undocumented feature

Input: one vendor has no public document about an export feature. Output: mark that cell Unknown, record the search gap, and avoid claiming the feature is absent. If a review claims it exists, retain the conflict and its date.

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.