Content
77%Reviews 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 local-SEO analysis skill with clear workflow sequencing and validation checkpoints. Its main weaknesses are conciseness (heavy dated-statistics load not isolated in a deprecated section) and progressive disclosure (dense inline reference-grade detail rather than split into local bundle files).
Suggestions
Move dated/time-sensitive statistics (the 'Key Statistics' table and inline year-stamped citations) into a dedicated reference file or a clearly marked 'current benchmarks' section, and add a deprecated/old-patterns section for superseded figures, to improve conciseness.
Extract the per-industry schema patterns and per-vertical citation/detection tables into local reference files under ./references/ so the body reads as an overview pointing one level deep to detail, strengthening progressive disclosure.
Tighten the inline benchmark citations (e.g. consolidate repeated 'Whitespark 2026'/'BrightLocal 2026' attributions) to reduce token load without losing the actionable thresholds.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is information-dense and assumes Claude's competence (no basic SEO concept explanations), but it is padded with time-sensitive dated statistics scattered throughout — 'March 2026', 'July 2025', 'March 2024 Core Update', 'Oct 2025', 'Whitespark 2026' — plus a large 'Key Statistics' table, none placed in a deprecated/old-patterns section, which the guideline says should penalize conciseness; it is not a 1 because there is no conceptual fluff, but not a 3 because the dated-stat load is not tightened. | 2 / 3 |
Actionability | Highly actionable guidance for an instruction-only analysis skill: concrete thresholds ('18-day rule', '10 reviews', '4.5+ stars', '>60% unique content', '5 decimal places'), specific site: search operators ('site:yelp.com "Business Name"'), enumerated schema properties, and per-dimension Full/Partial/Low scoring guides; absence of code is not penalized since the guidance is actionable. | 3 / 3 |
Workflow Clarity | Clear sequence of detect business type → detect industry vertical → six numbered weighted dimensions → 11-section output template, with explicit validation checkpoints (multi-location WARNING at 30+ / HARD STOP at 50+ pages requiring user justification; 'industry vertical unclear → ask the user to confirm') and an error-handling table acting as feedback loops; not capped at 2 because this is not a destructive/batch operation. | 3 / 3 |
Progressive Disclosure | References are well-signaled and one level deep ('Load on-demand as needed' pointing to ../seo/references/local-schema-types.md and local-seo-signals.md), but the body is fairly monolithic — a large statistics table, per-vertical detection tables, and per-industry schema patterns are inline rather than split out, and the two referenced files are cross-skill external paths with no local bundle files for this skill; not a 3 because content that could be separate is inline and not a 1 because references are clearly signaled and only one level deep. | 2 / 3 |
Total | 10 / 12 Passed |