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 highly actionable, well-sequenced domain skill: every tool has concrete parameters, ID-format gotchas, executable examples, retry loops, and an evidence-tier integration framework. Its weaknesses are redundancy — textbook histone-mark biology, a duplicated tool entry, and repeated reasoning logic — and a monolithic structure that inlines the entire API reference rather than splitting it into reference files.
Suggestions
Cut or compress the 'Reasoning: Histone Marks' dictionary to only the non-obvious guidance (bivalent promoter reporting rule, inference rule); Claude already knows that H3K4me3 marks active promoters and H3K27me3 marks Polycomb repression.
Move the Phase 0–7 tool parameter reference into a references/ file (e.g., references/tool_reference.md) and keep only the question-type classification, reasoning rules, key format gotchas, and fallback table in SKILL.md.
Deduplicate the overlapping guidance: ReMap_get_transcription_factor_binding is documented in both Phase 2 and Phase 6, and the cCRE-overlap/motif-disruption steps appear in both 'eQTL Interpretation' and 'Variant Regulatory Impact' — consolidate into one cross-referenced section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient — tool parameters, ID-format notes, and tight code examples are high-value — but it includes unnecessary explanation Claude already knows (the histone-mark dictionary: "H3K4me3 = active promoter", "H3K27me3 = Polycomb repression"), documents ReMap_get_transcription_factor_binding twice (Phase 2 and Phase 6), and repeats cCRE-overlap/motif-disruption logic across the eQTL and variant-impact reasoning sections. More than minor trimming is needed, so not 4; the bulk of the doc is tool-specific rather than padded, so not 2. | 3 / 5 |
Actionability | Fully executable guidance: copy-paste-ready calls with real values (tu.tools.UCSC_get_encode_cCREs(chrom="chr17", start=7668421, end=7687490), RegulomeDB_query_variant(rsid="rs4994")), exact parameter names for every tool, required-ID formats (ENSG00000012048.20, chr17_43705621_T_C_b38), and output-parsing snippets covering the common cases. | 5 / 5 |
Workflow Clarity | Clear sequence: classify the question first (types a–d), then Phase 0–8, with error-recovery feedback ("If 0 results, retry with assay_type='polyA plus RNA-seq'", anatomy-term fallbacks, "first hit may not match" filter warning) and a fallback-strategy table. Falls short of 5 because validation checkpoints are embedded in prose rather than explicit validate-before-proceed gates; well above 3 given the systematic retry and fallback structure. | 4 / 5 |
Progressive Disclosure | Sections are well-organized with clear headers, but the ~230-line body inlines the full tool-parameter API reference (Phases 0–7) in SKILL.md with no reference files at all — matching the anchor example of ~200 lines of API reference that belongs in a separate file. Not 4 because the bulk reference content is not split out; not 2 because structure and navigation within the file are solid. | 3 / 5 |
Total | 15 / 20 Passed |