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 highly actionable with concrete, executable tool calls and a clearly sequenced 9-phase workflow, but it is an oversized monolith that would benefit from splitting reference material into separate files and adding explicit validation/feedback loops between phases.
Suggestions
Split the Phase 0 tool-parameter reference, gene-ID tables, and scoring tables into reference files (e.g. TOOL_PARAMS.md, GENE_IDS.md, SCORING.md) and link to them from a leaner SKILL.md overview.
Add explicit validation checkpoints between phases (e.g. verify EFO/gene resolution succeeded before Phase 2, confirm at least one genetic layer returned data before scoring) with retry guidance on failure.
Tighten prose and consolidate duplicated guidance-category tables to reduce the 1143-line footprint and respect the context-window budget.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Most content is operational reference (exact tool parameters, response JSON paths, score-component tables) that earns its place, but at 1143 lines the sheer volume strains the token budget and several reference blocks could be tightened or moved out, matching the mostly-efficient-but-could-be-tightened anchor. | 2 / 3 |
Actionability | Provides abundant copy-paste-ready Python with exact tool calls, required parameters, and response-structure parsing (e.g. tu.tools.OpenTargets_get_disease_id_description_by_name(diseaseName='breast cancer') with the nested response path), matching the fully-executable anchor. | 3 / 3 |
Workflow Clarity | The 9 phases are clearly sequenced and there is a Phase 0 parameter-verification step plus a completeness checklist, but explicit per-phase validation gates and validate->fix->retry feedback loops are largely absent, so checkpoints are present yet incomplete. | 2 / 3 |
Progressive Disclosure | The skill is a 1143-line monolithic file with no bundle files; large reference blocks (Phase 0 tool-parameter table, gene-ID tables, scoring tables) that should live in separate files are inline, matching the structure-present-but-content-should-be-separate anchor. | 2 / 3 |
Total | 9 / 12 Passed |