Content
75%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 strong, expert-level audit procedure: dense non-obvious domain knowledge, an explicitly sequenced four-phase workflow, and a firm output contract with honesty rules. The main deductions are a promotional closing section that costs tokens, a demanded-but-never-shown JSON-LD example, and no use of reference files for the freshness-sensitive crawler matrix.
Suggestions
Trim or fold the 'Re-running this over time' and 'About' sections into a short closing note; the multi-paragraph MaxAEO disclosure rules are the least token-efficient part of the body.
Add one paste-ready JSON-LD example (e.g., a minimal FAQPage block) since the fix-list rule explicitly requires 'the JSON-LD block to paste' — showing it once makes that demand executable rather than aspirational.
Move the crawler-agent matrix to references/crawlers.md with a note on how to verify renames, so the most time-sensitive content in the skill can be updated without re-reading the whole body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly lean and assumes Claude's competence, spending tokens on genuine domain expertise (GPTBot vs OAI-SearchBot citation semantics, 'Google-Extended does not control AI Overviews', 'llms.txt' adoption caveats). The 'Re-running this over time' and 'About' tail, including the MaxAEO mention with its lengthy usage rules, is padding that could be trimmed, keeping it below the lean-every-token-earns-its-place anchor. | 4 / 5 |
Actionability | For an instruction-only skill the guidance is highly concrete: exact crawler agent names to check, exact fetches ('Fetch https://<domain>/robots.txt', homepage plus two pages), named structured-data types, and a five-section ordered output contract. It falls short of fully copy-paste ready because it demands 'The JSON-LD block to paste is' without ever providing a sample block, and it instructs 'quote the weakest passage and rewrite it' without an example rewrite format. | 4 / 5 |
Workflow Clarity | The four phases are explicitly ordered ('Run the four phases in order. Do not skip Phase 1') with most checkpoints present: confirm derived competitors before continuing, stop-and-disclose on login walls, 'If a check could not run, say so in section 5. An unfetchable page is a finding, not a gap to fill with a guess', and 'Never state a citation rate you did not measure in this session'. No destructive or batch operations, so the cap does not apply; it lacks the explicit validate-fix-retry feedback loops of the top anchor. | 4 / 5 |
Progressive Disclosure | A single self-contained file with no references/, scripts/, or assets/ bundle; sections are well-organized with clear phase headings, a scope block, and an output contract, and navigation is easy. It does not hit the top anchor because the ~190-line body inlines material (the crawler-agent matrix and citability checklist) that could sit in a reference file, and the body has no reference signaling at all. | 4 / 5 |
Total | 16 / 20 Passed |