Content
53%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 skill's real workflow — PICOS extraction rules, a complete seven-database output template, and a well-integrated one-level-deep reference with executable syntax and examples — is genuinely actionable. However, the body is heavily padded with generic template boilerplate and generator artifacts that consume tokens without adding guidance, and the validation/checkpoint sections are vacuous rather than substantive.
Suggestions
Delete the boilerplate sections ('When to Use', 'Key Features', 'Dependencies', 'Example Usage', 'Implementation Details', 'Quick Validation') or replace them with a few skill-specific lines; remove generator artifacts like the 'Skill directory: 20260316/…' block.
Fix the broken cross-reference 'See `## Workflow` above for related details' (Workflow appears below Implementation Details) and reorder so the overview points forward to the real steps.
Add a concrete validation checkpoint, e.g., verify each generated query against the syntax rules in references/databases.md (field tags, quote style, boolean grouping) before returning output, ideally with a small worked example in the body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Roughly half the body is generic template filler: 'Use this skill when the request matches its documented task boundary', 'Key Features' repeating the description verbatim, 'Example Usage' leaking generator artifacts ('Skill directory: 20260316/scientific-skills/Others/meta-search-builder', 'No packaged executable script was detected'), and boilerplate 'Implementation Details'. Not 1 because the Workflow section itself is lean and every token there earns its place. | 2 / 5 |
Actionability | The core guidance is concrete and executable: PICOS extraction rules ('Limit the number of keywords to at most 5', "Simplify descriptive phrases (e.g., 'patients with ovarian cancer' -> 'ovarian cancer')"), a complete output-format template for all seven databases, and a clearly signaled pointer to references/databases.md for real syntax and examples. Below 5 because there is no worked end-to-end example in the body and 'See `## Workflow` above' points the wrong direction (Workflow is below that section). | 4 / 5 |
Workflow Clarity | The two-step sequence (extract PICOS entities, then generate per-database strategies with a defined output format) is clear, but checkpoints are vacuous or implicit: 'Quick Validation' states 'No local script validation step is required for this skill' and the validation sections are generic boilerplate with no step verifying that generated queries follow each database's syntax. | 3 / 5 |
Progressive Disclosure | Scored against the actual bundle: one reference file (references/databases.md), substantive, clearly signaled at the point of need ('See [references/databases.md](references/databases.md) for database-specific syntax and examples'), exactly one level deep. Below 5 because the body's padded boilerplate sections and one broken internal cross-reference dilute navigation. | 4 / 5 |
Total | 13 / 20 Passed |