Content
67%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 body is a lean, highly actionable operator's guide with good phase sequencing and effective parameter-gotcha coverage, but its progressive disclosure is fundamentally broken: all six referenced detail files are missing from the bundle, and the one bundled script is orphaned. The strongest fix is to ship the referenced files (or remove the dead links) and surface the GDSC script.
Suggestions
Ship the six referenced files (TOOLS_REFERENCE.md, API_USAGE_PATTERNS.md, TREATMENT_ALGORITHMS.md, REPORT_TEMPLATE.md, EXAMPLES.md, CHECKLIST.md) or delete the References section — dead links break every path from the overview to the detail layer.
Move the biomarker-to-drug mapping blocks and resistance-mutation frequency tables out of SKILL.md into TREATMENT_ALGORITHMS.md (which already claims to cover 'cancer type mappings'), keeping only a pointer in the body.
Reference scripts/gdsc_drug_response.py from the body — it is the only real bundle file, covers GDSC drug-sensitivity data the workflow otherwise lacks, and is currently undiscoverable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and operational throughout — tool names, exact parameters ('ensemblId, camelCase', 'condition, NOT disease', 'variant_id (numeric, e.g., 4170)'), a WRONG/CORRECT table, and domain facts Claude cannot reliably recall (resistance mutation frequencies, OncoKB demo-mode limits). It stays at 4 rather than 5 because the ~10-line biomarker-to-drug mapping blocks duplicate content the References section says TREATMENT_ALGORITHMS.md already contains ('cancer type mappings'), which is inlining that could be trimmed. | 4 / 5 |
Actionability | Guidance is highly concrete: exact MCP tool names per phase, parameter gotchas with example values ('molecular_profile="EGFR C797S"'), and 'LOOK UP DON'T GUESS' rules naming the exact tool to call per fact type. It falls short of the copy-paste-ready 5-anchor because the body shows no literal example tool calls or code — those are deferred to API_USAGE_PATTERNS.md — and several phases list tools without stating the query to issue. | 4 / 5 |
Workflow Clarity | A clear phase sequence (Phase 0 verification → Phase 6 report) with per-phase tool lists, a tool-verification table, mandatory checkpoints ('You MUST call FAERS... before finalizing the report'), and fallback guidance (OncoKB demo mode → use CIViC). It does not reach 5 because per-phase validation/feedback loops are implicit rather than explicit — the checklist lives in CHECKLIST.md rather than as inline verify steps, and there is no stated error-recovery path when a lookup returns nothing. | 4 / 5 |
Progressive Disclosure | The References section signals six one-level-deep files (TOOLS_REFERENCE.md, API_USAGE_PATTERNS.md, TREATMENT_ALGORITHMS.md, REPORT_TEMPLATE.md, EXAMPLES.md, CHECKLIST.md), but none of them exist in the bundle — every link is dead, so the entire detail layer is unreachable. Additionally, content that the references say belongs in those files (treatment mappings, examples) is inlined, and the one real bundle file, scripts/gdsc_drug_response.py, is never referenced from the body. This matches the 2-anchor (inlined content that belongs in separate files; navigation broken) rather than the 3-anchor, which assumes references are at least present. | 2 / 5 |
Total | 14 / 20 Passed |