Content
73%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.
The body delivers a thorough, well-sequenced audit workflow with strong validation checkpoints and copy-paste report templates. Its main weaknesses are token padding from the duplicated 80-item table and cross-skill promotional blocks, plus reliance on an external reference file for per-item criteria.
Suggestions
Remove the inlined 80-item reference table (lines 213–254) and rely on the one-level-deep link to references/core-eeat-benchmark.md to cut significant duplicated tokens.
Drop or collapse the 'SEO & GEO Skills Library' and 'Browse all 20 skills' promotional blocks, which do not advance the audit task and consume context budget.
Bundle references/core-eeat-benchmark.md inside ./references/ (or inline the per-item Pass/Partial/Fail criteria) so the skill is self-contained without an external repo-level dependency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient but carries padding — the inlined 80-item reference table (lines 213–254) duplicates content already promised in references/core-eeat-benchmark.md, and the promotional 'Browse all 20 skills' / 'SEO & GEO Skills Library' blocks add tokens that do not serve the audit task. | 3 / 5 |
Actionability | Concrete, copy-paste-ready report templates, explicit scoring rules (Pass=10/Partial=5/Fail=0), weighted-score formulas, and a worked example give mostly executable guidance; the minor gap is that the per-item evaluation criteria themselves are deferred to the external benchmark reference rather than inlined. | 4 / 5 |
Workflow Clarity | A clear four-step sequence (Preparation → CORE Audit → EEAT Audit → Scoring & Report) with a veto emergency-brake, dedicated Input/Output validation checklists, and an N/A re-normalization feedback loop for insufficient data, matching the top anchor. | 5 / 5 |
Progressive Disclosure | Well-sectioned overview (When to Use, What It Does, How to Use, Instructions, Validation, Example) with one-level-deep, clearly signaled references; the primary benchmark reference is repo-level external and no bundle files ship in ./references, so structure is good but not perfectly self-contained. | 4 / 5 |
Total | 16 / 20 Passed |