Content
57%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 content is highly actionable with copy-paste-ready commands and configs covering four project types, but it is held back by generic boilerplate sections, redundant config dumps duplicating what scaffold commands generate, an unscaffolded CLI project type, and a complete absence of validation checkpoints. No progressive disclosure is used — everything is inlined in one 355-line file. The strong description (0.84 normalized) is let down by mediocre body quality (0.58 normalized).
Suggestions
Add validation checkpoints to the workflow: after scaffolding, instruct running 'pnpm install', then 'pnpm type-check' and 'pnpm test', and to fix and re-run if either fails before presenting the project as complete.
Move the per-project-type templates (Next.js/Node API/library package.json, tsconfig.json, directory trees) into separate reference files (e.g., templates/nextjs.md, templates/nodejs-api.md) and keep SKILL.md as a concise overview linking to them — this would also cut most of the redundant config duplication.
Remove the generic 'Use/Do not use this skill when', 'Context', and 'Requirements' filler sections and either scaffold the CLI project type promised in step 1 or drop it from the project-type list; also strip pinned version numbers in favor of '@latest' or a note on checking current versions.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly concrete rather than explanatory, but it is padded in several places: generic 'Use this skill when / Do not use this skill when / Context / Requirements' boilerplate lines, and complete package.json/tsconfig.json dumps (~55 lines) that the cited 'pnpm create next-app' command already generates automatically. Version-pinned dependencies ('next: ^14.1.0', 'vitest: ^1.2.0', 'eslint: ^8.56.0') add time-sensitive content that will age. Not a 2 because no space is spent explaining concepts Claude already knows; not a 4 because the boilerplate sections and redundant config dumps are clearly trimmable. | 3 / 5 |
Actionability | Highly executable throughout — 'pnpm create next-app@latest . --typescript --tailwind --app --src-dir', complete vite.config.ts, a working createApp() Express example, and copy-paste-ready package.json/tsconfig/eslint/vitest configs. Falls short of 5 because 'CLI: Command-line tools' is listed as a project type in step 1 but no CLI structure is ever generated, and the React+Vite section lacks the package.json and test detail given for other project types. | 4 / 5 |
Workflow Clarity | Steps 1–7 form a coherent sequence (analyze type → init with pnpm/git → generate structure per type → configure tools → output format), but there are no validation checkpoints anywhere: the skill never instructs running 'pnpm install', verifying 'pnpm type-check' or 'pnpm build' succeeds, or running the test suite after scaffolding a multi-file project. This matches the anchor 'steps listed but validation gaps; checkpoints missing or implicit'. | 3 / 5 |
Progressive Disclosure | Headers are clear and sections are logically ordered, but the bundle contains no reference files at all, and ~300 lines of per-project-type templates (Next.js package.json/tsconfig, Node.js API tree + app.ts, library configs) that clearly belong in separate reference files are inlined in SKILL.md. This fits 'content that should be separate is inline'; it is not a 2 because the section structure itself is good and navigable. | 3 / 5 |
Total | 13 / 20 Passed |