Content
81%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 highly actionable and workflow-clear, with concrete commands, validation loops, and error recovery guidance that assume Claude's competence. Its main weakness is redundancy of the hard rules across multiple sections and the absence of bundle files for reference material.
Suggestions
Consolidate the repeated 'never guess the port' and 'never spawn vite/npm run dev' rules into the Hard rules section and reference it once elsewhere instead of restating.
Move the error-code table and state-files table into a references/ bundle file (e.g. REFERENCE.md) and link to it, reducing the SKILL.md to a lean overview and improving progressive disclosure.
De-duplicate the two-stage save→deploy explanation so it appears fully once, with the Hard rules entry pointing to it rather than re-describing it.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and free of concept-explanation padding, but several operational rules are repeated across sections — 'never guess the port / 17173..17272' (lines 109-110, 176-177, 241-242), 'never spawn npm run dev / vite' (108, 257-258), and the two-stage save→deploy flow (179-205, 273-276) — which could be consolidated. | 3 / 5 |
Actionability | Provides copy-paste-ready CLI subcommands with flags, exact MCP tool call shapes with parameters, concrete file paths, and a full error-code table with recovery actions covering the common cases. | 5 / 5 |
Workflow Clarity | Sequenced workflows with explicit validation checkpoints and feedback loops — the 'When the user just walked in' checklist (read status, check preview.json, do not re-init), the two-stage save→deploy with env pre-flight and retry, and JSON-stdout parsing with logPath surfacing on failure. | 5 / 5 |
Progressive Disclosure | Well-organized single-file structure with clear section headers and one-level-deep, clearly signaled references to fetched CloudBase domain skills; minor gap is that reference-style content (error-code and state-file tables) is inlined in a 316-line file rather than split into bundle files. | 4 / 5 |
Total | 17 / 20 Passed |