agentleFS
Sign inStart free
ianklassenianklassen/ai-pm-system/skills/competitor-tracker/SKILL.md

competitor-tracker

Skill1 starsChanged 7 months agoMITView on GitHub

Maintain and query a living competitive landscape. Use when discussing competitors, analyzing competitive moves, or preparing competitive positioning for stakeholders.

2 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

6 rules. About 0 are common, 4 are distinctive, and 2 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.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Before strategy sessions, PRDs, or positioning work

    line 16
  2. Distinctive:

    When a stakeholder asks "what about [competitor]?"

    line 17
  3. Very specific:

    Read knowledge/competitive/ for existing competitor profiles:

    line 31
  4. Distinctive:

    If the competitor doesn't have a profile yet, create one.

    line 35
  5. Distinctive:

    Add new intelligence to the competitor's profile.

    line 48
  6. Very specific:

    Should this trigger a what-if analysis?

    line 85

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Competitor Tracker

Maintain a living competitive intelligence layer that grows over time. Every time competitors come up in conversation, this skill captures the signal and connects it to strategy.

When to Use

  • "[Competitor] just launched X"
  • "How do we compare to..."
  • "Competitive analysis for..."
  • "What's [competitor] doing?"
  • Before strategy sessions, PRDs, or positioning work
  • When a stakeholder asks "what about [competitor]?"

Process

1. Identify the Trigger

Determine what kind of competitive question this is:

  • News/update — competitor did something new → capture it
  • Comparison — how do we stack up? → pull landscape + analyze
  • Positioning — how should we differentiate? → strategy work
  • Threat assessment — should we be worried? → what-if analysis

2. Load Existing Intelligence

Read knowledge/competitive/ for existing competitor profiles:

  • knowledge/competitive/landscape.md — overview of the market
  • knowledge/competitive/[competitor-name].md — per-competitor profiles

If the competitor doesn't have a profile yet, create one.

3. Capture New Intelligence

For any new competitive signal, extract:

  • What happened — the specific move (launch, pricing change, funding, hire, pivot)
  • Date — when
  • Source — where you heard it (article, user feedback, app store, etc.)
  • Impact assessment — how does this affect our product/strategy?
  • Response needed? — ignore / monitor / respond / urgent

4. Update the Profile

Add new intelligence to the competitor's profile. Keep profiles structured:

# [Competitor Name]

**Last updated:** YYYY-MM-DD
**Category:** Direct / Indirect / Adjacent
**Threat level:** High / Medium / Low

## Overview
[What they do, who they serve, how they position]

## Strengths
- [strength]

## Weaknesses
- [weakness]

## Recent Moves
| Date | Move | Our Assessment |
|------|------|---------------|
| YYYY-MM-DD | [what they did] | [what it means for us] |

## Feature Comparison
| Capability | Us | Them | Notes |
|-----------|-----|------|-------|
| [feature] | ✅/❌/🟡 | ✅/❌/🟡 | [context] |

## How We Win Against Them
[Our differentiation and positioning]

5. Connect to Strategy

After updating intelligence:

  • Does this change any priorities? Reference knowledge/products/*/roadmap.md
  • Does this affect positioning? Reference knowledge/competitive/landscape.md
  • Should this trigger a what-if analysis? (→ use what-if skill)

Output (for competitive analysis requests)

## Competitive Analysis: [Topic/Competitor]

**Date:** YYYY-MM-DD

### Market Landscape
[Brief overview of competitive dynamics]

### Head-to-Head: Us vs. [Competitor]
| Dimension | Us | Them | Verdict |
|-----------|-----|------|---------|
| [dimension] | [our position] | [their position] | [who wins and why] |

### Their Recent Moves
- [move + our assessment]

### Our Differentiation
- [what makes us different and why it matters to users]

### Recommended Response
- [ignore / monitor / counter-position / build / accelerate]
- [specific action if needed]

Principles

  • Accumulate, don't restart — every competitive mention adds to the knowledge base
  • Users > features — compare user outcomes, not feature checklists
  • Don't panic-react — most competitor moves don't require a response
  • Differentiation > parity — winning isn't about matching features

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.

Check your setup, free