agentleFS
Sign inStart free
HainrixzHainrixz/claude-seo-ai/skills/score/SKILL.md

score

Skill81 starsChanged 2 months agoMITView on GitHub

Recompute and display the two scores (Search SEO + AI Visibility) from a persisted audit run, without re-crawling. Use to re-show or refresh the scores after an audit, to score a specific run directory or host, or to score a saved findings JSON file.

15 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

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

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 0

    Distinctive

    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. Very specific:

    No argument (default): read <root>/index.json, take the host whose latest run id sorts highest (run ids are UTC YYYY-MM-DDTHH-mm-ssZ, so …

    line 15
  2. Very specific:

    If no index.json/latest.json exists, or the run has no findings.json, tell the user to run /claude-seo-ai:audit <url> first — never score …

    line 19

“Common” is measured: kept by at least 6 in 10 of the 13 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
<!-- Portions Copyright (c) 2026 Enrique Rocha (@soyenriquerocha) - see LICENSE for original authors · tododeia.com · id er-d03758e1 -->

/claude-seo-ai:score

Recompute and show the two 0–100 scores by running the seo-score skill, which uses scripts/score.mjs for a reproducible number.

Runs live under <root>/<host>/<run-id>/, where <root> is --out › $CLAUDE_SEO_AI_HOME › ${CLAUDE_PLUGIN_DATA}/runs › ~/.claude-seo-ai/runs, and <host> is the lower-cased host with : → _ (local targets become local/<basename>-<hash>). score.mjs --run takes a directory or a findings file — it does not understand the word latest, so resolve the pointer yourself with Read before you call it: <root>/<host>/latest.json is { run, path, updated_at } and path is the absolute run directory; <root>/index.json lists every host with its latest run id.

  • No argument (default): read <root>/index.json, take the host whose latest run id sorts highest (run ids are UTC YYYY-MM-DDTHH-mm-ssZ, so string order is chronological), read that host's latest.json, then node "${CLAUDE_PLUGIN_ROOT}/scripts/score.mjs" --run <path from latest.json>.
  • latest:<host> → read <root>/<host>/latest.json and pass its path to --run.
  • A run directory → node "${CLAUDE_PLUGIN_ROOT}/scripts/score.mjs" --run <run-dir> (it reads <run-dir>/findings.json).
  • A findings JSON path → node "${CLAUDE_PLUGIN_ROOT}/scripts/score.mjs" --findings <path> (add --vertical a,b, --multilingual and --environment production|preview|staging|local when the file carries no run context; --manifest <crawl.json> adds the site rollup, --strict exits 2 if any finding fails schema validation, --validate-only reports the per-finding schema verdict without scoring).
  • If no index.json/latest.json exists, or the run has no findings.json, tell the user to run /claude-seo-ai:audit <url> first — never score from memory.

Show both scores with bands, the per-category breakdown, any severity-gating cap (cap_reasons), the unscored state when no category is active, and the needs_api / manual_review / dropped counts. Two scores, never blended. When an axis comes back provisional: true (state: "partial"), say the band and its coverage % in the same sentence — a band built on a third of the model is not the same claim as a measured one, and the per-axis warnings[] name what was not measured. With a rollup, read pages_scored against pages_count: a page listed in unscored_pages[] did not answer 2xx, so it was never scored — name those pages and their status instead of letting the site score stand for a sample that was not measured.

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