Content
82%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 with executable code and a clear sequenced workflow, supported by a verification checklist. Its weak spots are some repetitive install-command verbosity and reference files that are empty stubs pointing to missing targets.
Suggestions
Collapse the per-framework install command blocks: show one example and instruct to use the detected package manager, removing the npm/yarn/pnpm triplication.
Fix the references directory: replace the path-stub files (e.g. DataProvider.md containing only '../../../../docs/core/api/DataProvider.md') with real content or correct, resolvable links.
Add an explicit validation feedback loop (e.g. after the Verification Checklist, 'If any check fails, fix and re-run before handing off to protocol setup') to strengthen workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly efficient and action-oriented with little concept-explanation padding, but install commands are repeated for npm/yarn/pnpm per framework and several large code blocks could be trimmed. | 4 / 5 |
Actionability | Provides copy-paste-ready provider code for every supported framework, concrete install commands, and exact detection patterns/tables, fully covering the common cases. | 5 / 5 |
Workflow Clarity | Clear detect → install → provider → protocol-handoff → verify sequence with a Verification Checklist and a Common Issues recovery section, though there is no explicit re-run-on-failure feedback loop. | 4 / 5 |
Progressive Disclosure | A well-structured single SKILL.md with a clearly signaled one-level-deep References section; however the three referenced files are path stubs whose ../../../../docs targets do not resolve, a minor organization gap. | 4 / 5 |
Total | 17 / 20 Passed |