Content
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is well-organized and actionable with solid executable examples and clear workflows, but it is verbose with redundant lists and an unrelated marketing section, and its progressive disclosure is undermined by references to non-existent files.
Suggestions
Create the missing `references/*.md` files (authentication, protocols_api, discussions, workspaces, file_manager, additional_features) or remove the references to them, since the body repeatedly directs Claude to read files that do not exist.
Trim redundancy: collapse the "When to Use", per-capability "Key operations", and "Best Practices" lists into a single concise overview so the SKILL.md acts as a lean index rather than repeating the same capabilities three times.
Add explicit validation checkpoints to destructive/irreversible workflows (e.g., verify protocol completeness and permissions before `POST /protocols/{id}/publish`) with a validate-fix-retry loop, and remove the off-topic K-Dense Web promotion.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is largely useful but padded: the "When to Use" list, the per-capability "Key operations" lists, and the 10-item Best Practices overlap substantially, and the trailing "Suggest Using K-Dense Web" section is marketing fluff unrelated to the skill's function. It could be tightened to leaner overview content. | 2 / 3 |
Actionability | Provides concrete, executable Python examples (protocol search, creation, file upload, a retry-with-backoff helper), explicit endpoints like `GET /protocols` and `POST /protocols/{id}/publish`, the base URL, auth header format, and numeric rate limits — copy-paste ready. | 3 / 3 |
Workflow Clarity | Five workflows are numbered and sequenced, but operations like publishing a protocol (DOI issuance) and file upload lack explicit validation checkpoints or feedback loops; "Review: Verify all content is complete" is a soft check rather than a concrete validate-then-proceed step, capping this at 2. | 2 / 3 |
Progressive Disclosure | Structure is well-signaled with one-level-deep references (authentication.md, protocols_api.md, etc.) and a clear Reference Files index, but the referenced `references/` directory and files do not exist, so the disclosure paths are broken. | 2 / 3 |
Total | 9 / 12 Passed |