agentleFS
cobusgreylingcobusgreyling/grok-bot-templates/skills/watch-aeo/SKILL.md

watch-aeo

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 “Watch AEO”. A useful skill states the six fields from Skills and routines. A pinned query set must be rerun across public answer engines and AI overviews as a standing visibility program, not a one-off chatbot check. Every citation was seen this run. Missing engines are named, not guessed. No page was published. Queries match the pinned set. AEO brief with…

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 an unpublished writing brief for gaps.

    line 26
  2. Distinctive:

    Every citation was seen this run.

    line 30
  3. Distinctive:

    Do not publish or update pages.

    line 40

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

Watch AEO

Paste this into Grok Bot after a successful run:

Save the process we just used as a skill called “Watch AEO”.

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

1. When to use it

A pinned query set must be rerun across public answer engines and AI overviews as a standing visibility program, not a one-off chatbot check.

2. Required inputs and access

  • Pinned query set and competitor set
  • Public answer engines the browser can reach
  • Prior AEO brief in /workspace when it exists

3. Sequence of work

  1. Load the saved query set. If it is missing, ask and stop. Do not freelance new queries.
  2. Rerun each query with the same wording on the named engines. Timestamp fetches.
  3. Record who is cited (us vs competitors) with verbatim snippets and URLs.
  4. Diff against last brief. Label unverified appearances.
  5. Write an unpublished writing brief for gaps. Do not publish pages. Do not substitute a one-off chatbot paste.

4. How to validate the result

Every citation was seen this run. Missing engines are named, not guessed. No page was published. Queries match the pinned set.

5. What to return

AEO brief with reruns, citations, gaps, unpublished writing brief, and action log of engines and timestamps.

6. What requires approval

Do not publish or update pages. Do not pay for placements. Do not contact an answer-engine vendor as the brand.

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.