mcpField
S
score

score

github.com/hainrixzMarketing & growth79209 installsUpdated 3d ago
Repository

About score

score is a scoring skill in the Claude SEO AI plugin that recalculates and displays Search SEO and AI Visibility scores from existing audit results. Its script makes scoring reproducible and distinguishes incomplete coverage and unscored cases.

Key features

  1. 01Recalculates both scores
  2. 02Reads run directories or findings files
  3. 03Shows bands and category breakdowns
  4. 04Reports caps and unscored states
  5. 05Shows coverage and review counts

Use cases

  1. 01Recompute site scores after an audit
  2. 02Inspect category scores and severity caps
  3. 03Check partial coverage or unscored pages

MCP support

The input does not describe MCP integration.

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/hainrixz/claude-seo-ai --skill score

After installing, type/scorein Claude Code to confirm it loaded.

Details

From the project README

/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.

Comments

Markdown supported