Content
82%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-built analysis skill: highly actionable checks, explicit error-handling checkpoints, and a specified output format. Its weaknesses are modest — some cross-section repetition of statistics and an implied rather than explicitly numbered workflow.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with non-obvious domain knowledge (2026 factor weights, dated policy changes, sourced statistics) and contains no explanations of concepts Claude already knows. However, several facts are repeated across sections (ChatGPT conversion stats appear in both the stats table and the AI section; "Bing Places powers ChatGPT, Copilot, Alexa" appears three times; the local-schema-types.md load instruction appears four times), so it could be tightened. | 4 / 5 |
Actionability | Checks are concretely executable: exact search patterns (`site:yelp.com "Business Name"`), exact schema properties with constraints ("geo (minimum 5 decimal places)", "priceRange <100 chars"), per-dimension scoring guides, a numbered 11-part output template, and prioritized action lists. As an instruction-only analysis skill, its guidance is copy-paste actionable and covers the common cases. | 5 / 5 |
Workflow Clarity | A clear gated sequence is present — business type detection "before analysis", vertical detection routing, six weighted dimensions, then a specified report — and the Error Handling table provides explicit failure checkpoints with recovery actions (unreachable URL, NAP absent, 50+ pages hard stop). It falls short of anchor 5 only because the workflow is implied by section order rather than stated as an explicit ordered procedure. | 4 / 5 |
Progressive Disclosure | A dedicated "Reference Files" section lists four one-level-deep, clearly signaled references with per-file descriptions ("Load on-demand as needed"), plus explicit cross-skill boundaries (seo-maps, /seo geo). The minor gap: per-vertical schema patterns are inlined in section 5 while simultaneously being delegated to local-schema-types.md, and the stat-heavy sections could arguably live in the reference files. | 4 / 5 |
Total | 17 / 20 Passed |