Content
71%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 is a maximally lean delegation stub with a genuinely useful instruction (resolving the target's relative references against its own directory), but its entire value depends on `../../seo/ecommerce-seo/SKILL.md`, which is not part of this skill's bundle and cannot be verified to exist from the skill's location. As written, the skill is a well-formed pointer with no reachable substance — excellent conciseness, but incomplete actionability and a broken progressive-disclosure chain.
Suggestions
Inline a minimal fallback outline of the core audit steps (or a short summary of the delegated workflow) so the skill remains useful when the referenced file is absent.
Fix or verify the delegation path: either bundle the target under this skill's directory (e.g. references/ecommerce-seo/SKILL.md) or reference it by resolvable skill name, since `../../seo/ecommerce-seo/SKILL.md` does not exist relative to this SKILL.md.
Add a checkpoint step confirming the target file was successfully read before proceeding to follow it, with an error path if it is missing.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is two sentences: "Read [`../../seo/ecommerce-seo/SKILL.md`](../../seo/ecommerce-seo/SKILL.md) completely, then follow it as the active workflow. Resolve every relative reference from that file against `../../seo/ecommerce-seo/`." Every token carries instruction — no concept explanations, no padding. Matches anchor 5 (lean and efficient; assumes Claude's competence); there is nothing to trim, so level 4's "minor instances of over-explanation" does not apply. | 5 / 5 |
Actionability | The directive itself is precise and executable in form — a specific file path, an explicit rule for resolving that file's relative references — but the entire workflow delegates to `../../seo/ecommerce-seo/SKILL.md`, which does not exist in this skill's bundle (no references/, scripts/, assets/, and no such file reachable from the skill's directory). This matches anchor 3 (some concrete guidance but incomplete; missing key details): the actual audit steps are entirely absent from what can be read here. Not level 4, because a dangling delegation target is more than a minor gap; not level 2, because the instruction given is specific and self-contained in form rather than a vague hint. | 3 / 5 |
Workflow Clarity | As a single-purpose redirect skill the sequence is unambiguous — read the target completely, follow it as the active workflow, resolve its references against the stated base directory — and the reference-resolution rule preempts a real failure mode. Not level 5 because there is no checkpoint verifying the target file exists/loaded before proceeding (and in this environment it would fail immediately); not level 3 because the sequence that is written is fully coherent with only that minor validation gap, matching anchor 4. | 4 / 5 |
Progressive Disclosure | The single reference is clearly signaled and only one level deep, which is the right structure for a proxy skill — but the referenced path points outside the skill's own directory (`../../seo/ecommerce-seo/`) to a file not present in the bundle, so navigation leads nowhere and content is not appropriately split across actual files. Matches anchor 3 (references present but the structure does not hold up against the actual bundle). Not level 4: the broken/unresolvable target is more than a minor organization gap; not level 2, because what little exists is well signaled rather than buried or monolithic. | 3 / 5 |
Total | 15 / 20 Passed |