agentleFS
Sign inStart free
cihantopaccihantopac/searvex/skills/monitor/SKILL.md

monitor

Skill4 starsChanged 13 days agoApache-2.0View on GitHub

Single step 3 of the /searvex workflow - Re-audit a website with Searvex and compare against the previous run to find regressions and improvements; optionally include Search Console data (read-only).

30 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use spec and debug.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    spec

    Produce a verified spec — problem, desired outcome, and acceptance criteria — before building. Use when given a GitHub/Linear issue link, when starting from a fuzzy in-conversation idea, or asked to "figure out what to do" / "scope this" / "what should I build" — whenever the *what* isn't yet pinned down. Grills the ambiguities, checks the premise against the code, and produces acceptance criteria you sign off on — then hands to design-first.

    Also in 3 projects that use this

  • AnthropicSkill

    debug

    Structured debugging session — reproduce, isolate, diagnose, and fix. Trigger with an error message or stack trace, "this works in staging but not prod", "something broke after the deploy", or when behavior diverges from expected and the cause isn't obvious.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 26 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Run node "${CLAUDE_PLUGIN_ROOT}/dist/searvex.mjs" monitor $ARGUMENTS and read monitor.md.

    line 7
  2. Very specific:

    If the user has Search Console access, run node "${CLAUDE_PLUGIN_ROOT}/dist/searvex.mjs" gsc report <property> --audit latest (after a …

    line 9
  3. Very specific:

    If none is configured, say performance was not measured.

    line 19

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

Run node "${CLAUDE_PLUGIN_ROOT}/dist/searvex.mjs" monitor $ARGUMENTS and read monitor.md.

If the user has Search Console access, run node "${CLAUDE_PLUGIN_ROOT}/dist/searvex.mjs" gsc report <property> --audit latest (after a one-time gsc auth --client <their Desktop OAuth client JSON>, which the user runs in their own terminal), or gsc import <export.zip> --audit latest for a Performance CSV export; for Bing use bing report <siteUrl> after the user stored a key with searvex bing auth in their own terminal (never ask for the key in chat). These give verified queries, striking-distance opportunities, low-CTR pages and queries shared by several pages — present them as verified data, separately from heuristics.

Report in 80–150 words: score change, new and worsened issues (regressions first), resolved issues, and — only if real data was provided — Search Console clicks/impressions/CTR/position. Link monitor.html (and the audit's report.html, whose "Changes" tab shows the same comparison) instead of listing every change. Search Console data comes from SEARVEX_GSC_TOKEN + SEARVEX_GSC_SITE (read-only OAuth token) or --import of a Performance CSV export. If none is configured, say performance was not measured; never estimate traffic. For recurring checks, suggest running the same command on a schedule (CI or cron) with --fail-on high.

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