Content
77%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.
Highly actionable and well-sequenced content with strong validation and fallback guidance, weakened by general oncology education that pads the context budget and by a monolithic single-file structure with no progressive disclosure to supporting reference files.
Suggestions
Trim or relocate the general oncology primers (staging vs grading, biomarker definitions, histological vs molecular basics) — Claude already knows these; keep only skill-specific interpretation guidance tied to the tools.
Extract the 'Common OncoTree Codes' table and the 'Tumor Classification Reasoning' framework into a reference file (e.g., references/oncotree-codes.md) referenced from SKILL.md to improve progressive disclosure.
Move the detailed biomarker interpretation strategy into a separate reference, keeping the SKILL.md body focused on tool invocation patterns and validation steps.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Tool-specific guidance (param tables, code patterns, verified codes) is efficient, but the 'Tumor Classification Reasoning' section pads with general oncology education Claude already knows — e.g., TNM staging definitions, Grade 1-3 explanations, and biomarker primers (HER2, ER/PR, Ki67, TMB, MSI) — that could be trimmed without losing skill value. | 3 / 5 |
Actionability | Provides copy-paste-ready code patterns with concrete params (e.g., OncoTree_search(query='pancreatic ductal adenocarcinoma')), a tool parameter reference with required/optional columns, a verified-working codes table, and example return payloads — fully executable and covering common cases. | 5 / 5 |
Workflow Clarity | Four-phase workflow (Discovery → Validation → Tissue Exploration → Downstream Use) is clearly sequenced with explicit validation checkpoints ('Always validate via OncoTree_get_type before using in downstream tools', status-check before OncoKB) and a Fallback Chains table providing error-recovery feedback loops. | 5 / 5 |
Progressive Disclosure | Sections are well-organized with clear headers, but ~200 lines are entirely inline with no external reference files; content like the detailed oncology reasoning framework and the common-codes table could be split into separate reference files for easier navigation, and no bundle files exist to offload it. | 3 / 5 |
Total | 16 / 20 Passed |