Content
86%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.
An exemplary lean skill body: dense gotchas, concrete paths and commands, and a well-signposted collection workflow with a build validation checkpoint. The main gaps are the absence of a complete copy-paste code example for collection definitions and missing error-recovery guidance after a failed build.
Suggestions
Add a minimal copy-paste `src/content.config.ts` example using `defineCollection` + Zod schema so the collection workflow is fully executable without consulting external docs.
Extend the collection workflow with an explicit error-recovery step after the build check (e.g. "if the build fails with type errors in generated collection types, fix the Zod schema and rebuild").
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line is a gotcha, path, or directive (e.g. "`public/` serves assets as-is; `src/assets/` goes through the build pipeline. Wrong folder = no optimization, or a broken import.") with zero padding and no explanation of concepts Claude already knows — every token earns its place, matching the lean anchor rather than the minor-trim anchor below. | 5 / 5 |
Actionability | Concrete identifiers and commands throughout — `src/content.config.ts`, `glob({ pattern: '**/*.{md,mdx}', base: './src/content/blog' })`, `astro add react tailwind mdx sitemap` — but no complete copy-paste snippet (e.g. a full `defineCollection` example), so guidance is mostly executable with minor gaps rather than fully copy-paste ready. | 4 / 5 |
Workflow Clarity | "Add a collection" is a clear 4-step sequence with an explicit validation checkpoint ("The build must exit zero — collection types are generated at build time, so type errors only surface after a build"), but there is no error-recovery guidance for what to do when the build fails, keeping it below the feedback-loop anchor. | 4 / 5 |
Progressive Disclosure | The body is under 50 lines with well-organized sections (Gotchas, Layout, Add a collection), a link to official docs, and no bundle files to reference — the rubric's simple-skill exception applies, so well-organized sections alone earn the top score. | 5 / 5 |
Total | 18 / 20 Passed |