Content
78%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, highly actionable CLI usage guide with clear sequencing and good error-handling guidance. Its main weakness is a dangling reference: the body points to REFERENCE.md twice but no such file ships with the skill.
Suggestions
Ship the missing REFERENCE.md (global options, environment variables, exit codes, reference URLs) or remove the two references to it — currently both links are dead ends.
Cut the repeated spec enumeration in the opening paragraph (it already appears in the frontmatter description) and collapse the "When to use" section's trigger-phrase pointer to reduce token redundancy.
Consider moving the rating-band / check-category reference (Step 7, lines 137–142) into REFERENCE.md so the main body stays a lean procedure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Largely efficient and operational — it assumes Claude knows what npm/API keys are and leads with executable commands — but the intro re-enumerates the full spec list already in the description and the "When to use" section re-points to the same triggers, minor redundancy that could be trimmed. | 4 / 5 |
Actionability | Fully executable, copy-paste-ready commands throughout (`npx agent-ready-scanner --version`, `agent-ready scan https://example.com --json | jq '.vercelScore'`, get/list/ask invocations) plus a concrete options table covering the common cases. | 5 / 5 |
Workflow Clarity | Steps 1–7 give a clear, ordered sequence with branching in Step 2 (env var → .env → ask user) and error-recovery feedback (no-wait → capture id → get; quota_exhausted → reset date → dashboard); falls short of 5 only because there is no explicit validate-then-proceed checkpoint, which this read-only scan task does not strictly require. | 4 / 5 |
Progressive Disclosure | Structure is sound and the overview correctly pushes detail (global options, env vars, exit codes, reference URLs) to a one-level-deep REFERENCE.md, but that file does not exist anywhere in the bundle — the referenced path is a dead link, so navigation is actually broken rather than merely having minor gaps. | 3 / 5 |
Total | 16 / 20 Passed |