Content
88%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 highly actionable, well-sequenced install guide: every operation is a copy-paste command, verification steps state expected outputs, and the diagnosis section provides a genuine check→fix→restart feedback loop. It is slightly over-inclusive for its stated user-facing purpose — the maintainer section and thrice-repeated cache-clean advice are the main trimmable tokens, and the one external reference points into another skill's bundle.
Suggestions
Move the "For plugin maintainers" section into a separate reference file (e.g. MAINTAINERS.md) — it targets a different audience than the user-facing install flow and adds ~10 lines of off-purpose context to the main skill body.
Deduplicate the `uv cache clean tooluniverse` advice, which appears in Updates, Troubleshooting, and step 7 of the diagnosis script — keep one canonical mention and cross-reference it from the other two spots.
Make the API_KEYS_REFERENCE.md pointer resolvable within this skill's own bundle (or inline the few most common keys like NCBI_API_KEY), since it currently depends on the separate setup-tooluniverse skill being installed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is command-first and tight — every step is a copy-paste block or a dense table, with no explanation of concepts Claude already knows. It falls short of 5 because the "For plugin maintainers" section (~10 lines about sync-skills.sh and release scripts) serves a different audience than the stated user-facing install flow, and `uv cache clean tooluniverse` is repeated in three places (Updates, Troubleshooting, and step 7 of the diagnosis script). Not 3: the redundancy is deliberate triage structure, not padded prose, and the bulk of the document is lean. | 4 / 5 |
Actionability | Fully executable throughout: "codex plugin marketplace add mims-harvard/ToolUniverse", "codex plugin add tooluniverse -m tooluniverse", "codex plugin list --json", the export block with "...then start codex from that same shell", the pin snippet with the exact "args": ["tooluniverse@1.3.0"] line and where to find the file, and a 7-step diagnosis script with inline FIX commands. Not 4: even edge cases (shadowing global install, Python too old, air-gapped install) get exact commands rather than hints. | 5 / 5 |
Workflow Clarity | Clear sequence — Prerequisites ("check once") → Install (two numbered commands) → restart → "Verify it worked" with expected output ("expect: tooluniverse (enabled)") — plus an explicit error-recovery feedback loop in "Automated diagnosis & repair": "apply the `FIX` for whatever fails, then restart Codex". Not 4: validation checkpoints state expected results, and recovery is a numbered check→fix→retry checklist rather than an implicit step. | 5 / 5 |
Progressive Disclosure | No bundle files exist for this skill (no references/, scripts/, or assets/), so this scores structure alone: a single ~163-line file with well-labeled sections, and the one deferred item is clearly signaled — "Full key list: the bundled `setup-tooluniverse` skill → `API_KEYS_REFERENCE.md`" — keeping a long key list out of the main file. Not 5: that pointer targets another skill's bundle rather than a file in this skill, the maintainer section is inlined content that belongs in a separate reference, and the single file carries more than a lean overview needs. Not 3: navigation is easy, sections are well-organized, and the one reference is one level deep and explicit. | 4 / 5 |
Total | 18 / 20 Passed |