Content
63%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 skill body is highly actionable — complete templates, validation tools, checklists, and a worked example — but it is severely over-inflated relative to its own reference files: ~785 lines that largely duplicate references/schema-templates.md, with four overlapping tables and a promotional nav block. Corrupted "~~" placeholders and broken relative links further degrade workflow and navigation quality.
Suggestions
Remove the eight full inline JSON-LD template blocks from SKILL.md and replace them with brief per-type summaries that point to ./references/schema-templates.md, which already contains the same templates.
Consolidate the four overlapping tables (Schema Type Quick Reference, Decision Tree, Industry-Specific Recommendations, Implementation Priority) into one compact mapping table, moving the rest into a reference file.
Fix the corrupted "~~" placeholders ("~~schema validator", "~~search console", "~~web crawler") with the real tool names, and repair or remove the broken relative links ../../CONNECTORS.md and ../../references/core-eeat-benchmark.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~785-line body inlines complete JSON-LD templates for 8 schema types that substantially duplicate references/schema-templates.md, plus a library cross-promotion nav block and four overlapping tables (Quick Reference, Decision Tree, Industry-Specific, Implementation Priority). This is noticeably verbose with several padded/duplicated sections rather than only minor over-explanation, fitting the 2 anchor. | 2 / 5 |
Actionability | Complete copy-ready JSON-LD templates with bracketed values, concrete validation URLs (validator.schema.org, rich results test), HTML implementation placement options, and a fully worked executable FAQPage example cover the common cases end to end, matching the 5 anchor. | 5 / 5 |
Workflow Clarity | The 10-step sequence (identify content type → map schema → generate → implement/validate) is clear with explicit Input/Output validation checklists, but there is no error-recovery loop after validation failures and the validator names are corrupted placeholders ("~~schema validator", "~~search console"), so it falls short of the 5 anchor. | 4 / 5 |
Progressive Disclosure | References are one level deep and clearly signaled in a "Reference Materials" section, but the template content that belongs in those files is duplicated inline in SKILL.md, and two referenced paths (../../CONNECTORS.md, ../../references/core-eeat-benchmark.md) do not resolve from this bundle — "content that should be separate is inline" matches the 3 anchor. | 3 / 5 |
Total | 14 / 20 Passed |