agentleFS
Othmane-KhadriOthmane-Khadri/YALC-the-GTM-operating-system/.claude/skills/run-competitive-intel/SKILL.md

run-competitive-intel

Skill298 starsChanged 6 months agoMITView on GitHub

Pull competitive intelligence on a competitor — pricing, positioning, recent changes, customer stories — via the competitive-intel CLI. Use when the user says 'analyze this competitor', 'pull competitive intel on [company]', 'compare us to [competitor]', 'what's [company] doing differently', or 'audit [competitor] pricing'. Side-effecting — calls Firecrawl + Anthropic, writes to local cache.

  • Reads credentials

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Read-only on the user-data DB.

    line 51

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

Run Competitive Intel

I'll wrap competitive-intel. Take a competitor URL, run the analysis pipeline, and surface the comparative brief.

When This Skill Applies

  • "analyze this competitor"
  • "pull competitive intel on [company]"
  • "compare us to [competitor]"
  • "what's [company] doing differently"
  • "audit [competitor] pricing"

NOT this skill (use research-prospect instead):

  • "research this company" — that's a brief on a prospect, not a comparative analysis.

Workflow

Step 0 — Ask for the competitor URL

"What's the competitor URL?"

Step 1 — Validate URL

Step 2 — Shell out

cd ~/Desktop/gtm-os && set -a && source .env.local && set +a && \
  npx tsx src/cli/index.ts competitive-intel --competitor <url>

Step 3 — Parse output

CLI emits a markdown comparative brief: their positioning vs. ours, pricing diff, customer-story angles, recent changes detected.

Step 4 — Render the brief verbatim

Step 5 — Offer follow-ups

"Want me to (a) draft a sales battle card from this, (b) personalize an outbound message that addresses their positioning?"

Notes

  • Requires FIRECRAWL_API_KEY + ANTHROPIC_API_KEY.
  • Reads our own positioning from ~/.gtm-os/company_context.yaml.
  • Read-only on the user-data DB; writes to a competitive-intel cache.

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.