Content
92%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 tight, well-sequenced install workflow: concrete commands, lockfile-derived runner selection, explicit stop-and-ask checkpoints for risky operations, and a verify-and-report step with real gate results. Its only notable gap is the undefined `<docs-slug>` placeholder in the docs-fetch step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and imperative throughout — every line instructs an action ("Grep the catalog case-insensitively", "Never pass --overwrite unless the user asked"), and even the brief rationales ("because init rewrites config and global CSS") are decision-relevant rather than padding. Not below 5 because no section explains concepts Claude already knows or could be tightened without losing information. | 5 / 5 |
Actionability | Guidance is almost fully executable: an explicit runner-selection table from lockfiles, a concrete install command template, a retry-by-URL fallback, and a docs URL pattern. Not 5 because the `<docs-slug>` placeholder in the fetch URL is never defined (its source in the catalog is not stated), leaving a minor gap; not 3 because the guidance is concrete and executable, not pseudocode or high-level hints. | 4 / 5 |
Workflow Clarity | Six clearly sequenced sections with explicit checkpoints and feedback loops: ask before `shadcn init`, ask on ambiguous name matches, show the diff before overwriting, retry by URL on unknown namespace, consult the troubleshooting table on CLI failure, and run type check/build/lint/test gates while "reporting the real results". This matches the top anchor of explicit validation with error recovery. | 5 / 5 |
Progressive Disclosure | The skill is under 50 lines with well-organized numbered sections and no bundle of its own to disclose; the two referenced files (the cult-ui catalog and setup guide) are one level deep, purpose-labeled, and given a clear path-resolution fallback (Glob pattern when the plugin-root path fails). Not below 5 because nothing that belongs in a separate file is inlined and navigation is unambiguous. | 5 / 5 |
Total | 19 / 20 Passed |