Content
77%Reviews 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 with executable per-framework code and a well-sequenced workflow backed by a verification checklist and troubleshooting. Its weaknesses are mild verbosity from inlined per-framework blocks and, more seriously, a progressive-disclosure structure whose referenced files are non-functional stubs pointing at missing documentation.
Suggestions
Fix or replace the reference stubs in references/ so DataProvider.md, installation.md, and getDefaultManagers.md contain real content rather than path strings to a non-existent docs tree.
Move the per-framework provider-setup code blocks into framework-specific reference files and keep SKILL.md as a concise overview that links out, reducing the main body's length.
Tighten the Install Command Examples section to a single canonical form plus a note that the detected package manager determines the command, instead of enumerating npm/yarn/pnpm for each framework.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~250-line body is mostly earned, actionable code with no concept-fluff Claude already knows, but it is not lean: full provider blocks for five frameworks are inlined and install commands restate npm/yarn/pnpm for each framework despite the package-manager detection already being covered, matching 'mostly efficient but could be tightened' rather than the lean anchor. | 2 / 3 |
Actionability | It provides concrete install commands, specific files to edit per framework (app/layout.tsx, app/_layout.tsx, index.tsx, main.ts), complete executable tsx/ts code blocks, and specific detection patterns — copy-paste ready and matching the fully-executable anchor; it is not 2 because the code is complete rather than pseudocode. | 3 / 3 |
Workflow Clarity | A clear numbered sequence (Detect → Install → Provider Setup → Protocol-Specific Setup) is paired with an explicit Verification Checklist and a Common Issues troubleshooting section providing error-recovery guidance, matching 'clear sequence with explicit validation steps; checklists for complex processes'; it is not 2 because validation checkpoints and recovery guidance are present, not implicit. | 3 / 3 |
Progressive Disclosure | A References section signals three one-level-deep files with descriptions, but the actual reference files are broken stubs (41–53 bytes) containing only path strings to a non-existent ../../../../docs tree, so the promised 'detailed API documentation' is absent; the body is also fairly monolithic with per-framework code that could be split out, matching the 'some structure but could be better organized' anchor rather than the well-split anchor. | 2 / 3 |
Total | 10 / 12 Passed |