Content
50%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 core Usage section is genuinely executable and the bundle structure (script plus one clearly linked reference) is sound, but the body is padded with generic template sections that add no GEO-specific value and contains a broken internal cross-reference and a fabricated expected-output block. Trimming the boilerplate and fixing the validation example would substantially improve it.
Suggestions
Cut the generic template sections ("Key Features", "Output Contract", "Validation and Safety Rules", "Failure Handling", "Required Inputs") or rewrite each to contain GEO-specific guidance; the current text is boilerplate that restates the description and adds no actionable detail.
Fix the "Example Usage" section: replace "See `## Usage` above" with a correct forward reference (Usage appears below), remove the hardcoded "20260316/scientific-skills/..." cd path, and replace the fabricated "Expected output format" under Quick Validation with the actual output of "python scripts/search_geo.py --help".
Consolidate the overlapping workflow guidance ("Example Usage" run plan, "Recommended Workflow", "Quick Validation") into one concrete sequence: build the query from references/query_fields.json, run the script, and inspect the actual JSON/markdown output it produces.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Roughly half the body is generic template boilerplate — "Use this skill when the request matches its documented task boundary", "Prefer this skill for repeatable, checklist-driven execution rather than open-ended brainstorming", "Output Contract", "Validation and Safety Rules", "Failure Handling" — none of it GEO-specific, and the frontmatter description is restated verbatim inside "Key Features". This is noticeably verbose with several padded sections (anchor 2), not merely trimmable at the margins (anchor 4). | 2 / 5 |
Actionability | The Usage section provides concrete, copy-paste-ready guidance: a full argument list, an executable example ("python scripts/search_geo.py \"diabetes\" --filters '{\"Organism\": \"Mus musculus\"...}' --limit 5"), and a compile/help check. It falls short of anchor 5 because the "Expected output format" block describes a result-file summary that "--help" would not actually produce, and no real sample search output is shown. | 4 / 5 |
Workflow Clarity | A sequence exists (validate inputs, run script, review output) and a "Quick Validation" step is included, but the checkpoints are generic template text rather than skill-specific ones, and the stated expected validation output does not match what the check command produces. This matches anchor 3 (steps present, checkpoints missing or implicit) rather than anchor 4's concrete validated sequence. | 3 / 5 |
Progressive Disclosure | The bundle split is appropriate and the single reference is well signaled ([query_fields.json](references/query_fields.json), one level deep), but the body inlines substantial boilerplate that belongs in no file at all, duplicates content (description repeated in "Key Features"), and contains a broken cross-reference ("See `## Usage` above" when the Usage section appears below "Example Usage"). Organization gaps are more than minor, so anchor 3 fits better than anchor 4. | 3 / 5 |
Total | 12 / 20 Passed |