Content
78%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-structured skill body: concrete executable examples, a clear core workflow with common recipes, and proper progressive disclosure into real reference files. The main improvement opportunity is removing the triple-repeated caveats about score interpretation and under-studied diseases, and merging the Limitations section with the Best Practices content it duplicates.
Suggestions
State the "scores are relative rankings, not confidence" and "under-studied diseases score lower" caveats once (in Evidence Interpretation or Limitations) and delete the other two repetitions.
Merge the Limitations section into Best Practices — items 2–4 of Limitations restate Score interpretation and Evidence quality guidance almost verbatim.
Fold the schema-drift error-recovery guidance into the workflow steps (e.g. as a "If a query fails" checkpoint) so validation is explicit where it will be executed.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly dense, non-generic material (API calls, field names, scoring interpretation), but the same caveats are repeated near-verbatim three times — "NOT confidence scores but relative ranking metrics" (line 220), "Scores rank relative, not absolute confidence" (line 271), and "Scores are relative, not absolute" (line 372); the "under-studied diseases score lower" point and the "no authentication" point are likewise each repeated three times, and the Limitations section largely restates Best Practices. This is more than 'minor instances' of padding, so it sits at anchor 3 rather than 4. | 3 / 5 |
Actionability | Every workflow step ships a copy-paste-ready Python call to the bundled script with real arguments (e.g. `get_target_disease_evidence(ensembl_id="ENSG00000157764", efo_id="EFO_0000249")`), the returned fields are enumerated, and the raw GraphQL endpoint is given for custom queries. This fully matches anchor 5: fully executable examples covering the common cases. | 5 / 5 |
Workflow Clarity | The 7-step core workflow and the four numbered Common Workflows give a clear, well-sequenced process, and there is an error-recovery loop ("re-check the live schema when a query fails... inspect the current schema rather than returning an empty result"). It is not 5 because validation checkpoints are stated in a separate versioning section rather than embedded as explicit validate-and-retry steps inside the workflows. | 4 / 5 |
Progressive Disclosure | The SKILL.md is a well-organized overview with clearly signaled, one-level-deep references — `references/api_reference.md`, `references/evidence_types.md`, and `references/target_annotations.md` all exist as real files, contain the bulk detail (79–401 lines), and do not nest further references; `scripts/query_opentargets.py` is likewise real and documented. Content is appropriately split and easy to navigate, matching anchor 5. | 5 / 5 |
Total | 17 / 20 Passed |