Content
71%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 dense, actionable, well-sequenced clinical workflow with concrete tool+parameter guidance and a mandatory safety gate. Its chief weakness is progressive disclosure: the six referenced detail files are missing from the bundle, breaking the navigation the overview promises.
Suggestions
Ship the six referenced files (TOOLS_REFERENCE.md, API_USAGE_PATTERNS.md, TREATMENT_ALGORITHMS.md, REPORT_TEMPLATE.md, EXAMPLES.md, CHECKLIST.md) or remove their links — dead references undermine the overview's promised navigation.
Move the full biomarker-to-drug and resistance-mapping tables into TREATMENT_ALGORITHMS.md and keep only a compact pointer in SKILL.md to remove the duplication noted in TREATMENT_ALGORITHMS.md's own description.
Add at least one inline validate->fix->retry feedback loop (e.g. OncoKB token missing -> fall back to CIViC as primary evidence) to raise workflow clarity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Dense and information-rich with no padding about basic biology, assuming Claude's competence; however the inline biomarker-to-drug and resistance tables duplicate content the body itself says lives in TREATMENT_ALGORITHMS.md ('cancer type mappings'), a minor instance of over-inlining that could be trimmed. | 4 / 5 |
Actionability | Gives concrete tool names with correct parameters (e.g. civic_search_evidence_items with molecular_profile="EGFR C797S", search_clinical_trials with condition, OpenTargets ensemblId camelCase) plus specific drug regimens; full worked call sequences are deferred to EXAMPLES.md, leaving a minor gap versus copy-paste-ready completeness. | 4 / 5 |
Workflow Clarity | A clear Phase 0–6 sequence with a diagram, per-phase tool mapping, a Phase 0 tool-verification table, and an explicit MANDATORY FAERS gate before finalizing; lacks explicit validate->fix->retry feedback loops, a minor validation gap. | 4 / 5 |
Progressive Disclosure | The References section is well-signaled and one-level-deep across six files, but none of those referenced files (TOOLS_REFERENCE.md, API_USAGE_PATTERNS.md, TREATMENT_ALGORITHMS.md, REPORT_TEMPLATE.md, EXAMPLES.md, CHECKLIST.md) actually exist in the bundle, so navigation leads to dead links; the present scripts/gdsc_drug_response.py is unreferenced and the cross-skill pharmacology_ref.py path is also absent. | 3 / 5 |
Total | 15 / 20 Passed |