agentleFS
Sign inStart free
cobusgreylingcobusgreyling/grok-bot-templates/skills/diff-competitors/SKILL.md

diff-competitors

Skill14 starsChanged 3 months agoMITView on GitHub

Paste this into Grok Bot after a successful run: Save the process we just used as a skill called “Diff Competitors”. A useful skill states the six fields from Skills and routines. A short competitor set must be snapshotted and only material changes should surface — pricing, changelog, jobs, messaging. Every change has before/after and a URL. No "they seem to be focusing on". Baseline or diff memo. Unchanged competitors listed in one line so the owner knows they were…

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Write the material-change memo with URLs and dates.

    line 25
  2. Distinctive:

    Every change has before/after and a URL.

    line 29
  3. Distinctive:

    Do not scrape behind logins the owner did not authorize.

    line 39

≈ “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

Diff Competitors

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Diff Competitors”.

A useful skill states the six fields from Skills and routines.

1. When to use it

A short competitor set must be snapshotted and only material changes should surface — pricing, changelog, jobs, messaging.

2. Required inputs and access

  • Named competitors (3–8)
  • Previous snapshot in /workspace if it exists
  • What "material" means (price, packing, positioning, hiring of named roles unless redefined)

3. Sequence of work

  1. Load last snapshot. If none, take a baseline and stop after writing it.
  2. Fetch current public pages. Quote, do not paraphrase numbers.
  3. Diff. Stay quiet on unchanged properties.
  4. Write the material-change memo with URLs and dates.

4. How to validate the result

Every change has before/after and a URL. No "they seem to be focusing on".

5. What to return

Baseline or diff memo. Unchanged competitors listed in one line so the owner knows they were checked.

6. What requires approval

Do not scrape behind logins the owner did not authorize. Do not post the memo to Slack or X.

Type / in the composer to reference a saved skill. If it does not appear, open Settings → Plugins → Yours and enable it for this Bot.

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