Content
65%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable with executable code and a clear phased workflow, but it is over-long for a SKILL.md and monolithically inline with weak validation checkpoints. Splitting reference material into bundle files and adding explicit validation feedback loops would lift the lower dimensions.
Suggestions
Move the chromosome-length tables, the ToolUniverse tool-parameter reference, and the full function library into separate files under references/ and link to them one level deep, keeping SKILL.md a concise overview.
Add explicit validate -> fix -> retry checkpoints in the batch/destructive workflows (e.g. differential methylation, peak overlap) and require verification before reporting results.
Trim the restated Summary and the duplicate intro paragraph, and tighten inline function definitions, to reduce token cost while preserving the actionable code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient executable code rather than concept-explanation Claude already knows, but it is padded with full chromosome-length tables for three builds (~80 lines of literals), a Summary that restates the intro, and inline function implementations that could be tightened. Not the lean level above; not verbose-with-concept-fluff below. | 2 / 3 |
Actionability | Provides concrete, runnable Python with real imports and pandas/scipy/statsmodels usage, plus a tool-parameter reference table with required params; the local-computation code is copy-paste ready rather than pseudocode. Not the incomplete/pseudocode level below. | 3 / 3 |
Workflow Clarity | Phases (0-7), a decision tree, and numbered use-pattern flows give a clear sequence, but there are no explicit validate-then-fix-then-retry checkpoints for batch/destructive operations, which the rubric caps at 2. Not the missing-sequence level below; not the explicit-checkpoint level above. | 2 / 3 |
Progressive Disclosure | No bundle/reference files exist and the entire body is inline in one monolithic file; content such as chromosome-length tables, the tool reference, and the function library would be better split into referenced files. Well-sectioned but content that should be separate is inline, matching the 2 anchor; not the well-signaled one-level-deep references above. | 2 / 3 |
Total | 9 / 12 Passed |