Content
78%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.
A tight, executable skill: the detection and installation commands are copy-paste ready and the workflow has an explicit decision branch plus a confirmation step. The main gaps are the Cursor-hardcoded success check, no client-detection command despite a detection table, and no error-recovery guidance for failed installs.
Suggestions
Make the post-install confirmation client-generic (e.g., re-run the detection command from the first section and assert the output is a file path, rather than the hardcoded '.cursor/...' ls).
Add a brief failure path for Installation: what to do if the clone/checkout fails or the canary file is still missing after copying (e.g., report the exact directory used and suggest re-running detection).
Provide a one-line command for client detection (e.g., ls -d .cursor .claude .agents ... 2>/dev/null) so the Client Detection table is actionable rather than only descriptive, and drop the duplicated per-client comments in the Installation block to remove redundancy.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean — copy-paste bash with terse comments and no explanations of concepts Claude already knows. Not a 5: the client→directory mapping appears twice (per-client comments in the Installation block and again in the Client Detection table), and the opening line restates the frontmatter description. | 4 / 5 |
Actionability | The detection command and sparse-checkout install block are fully executable and copy-paste ready. Not a 5: the success-confirmation step hardcodes the Cursor path ("ls .cursor/skills/tooluniverse-drug-research/SKILL.md") and doesn't generalize to the other seven clients, and there's no command to detect which client config directory exists. | 4 / 5 |
Workflow Clarity | Clear sequence — detect (with an explicit branch: file path → stop; NOT_INSTALLED → install), install, then confirm — with a post-install verification checkpoint, so the destructive/batch cap does not apply. Not a 5: no error-recovery loop for likely failures (clone fails, canary still missing after install, ambiguous client when multiple config dirs exist). | 4 / 5 |
Progressive Disclosure | A single-page, single-purpose skill (~70 lines, mostly code) that needs no external references, with four well-organized sections (Detection, Installation, Client Detection, After Installation). Per the rubric's simple-skill guidance, well-organized sections with no reference indirection earns the top anchor. | 5 / 5 |
Total | 17 / 20 Passed |