Content
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A dense, highly actionable skill body with strong workflows and executable code, weakened only by some rhetorical padding and a monolithic single-file structure that doesn't offload detail to reference files. The lowest dimensions are conciseness and progressive_disclosure.
Suggestions
Trim motivational restatement: state the 'map the computed value back to option letters' rule once instead of repeating it across the computational-procedures intro and the interpretation section.
Move the long Python procedure blocks (ORF counting, restriction digest, gamete ratios) into a scripts/ or references/ file referenced one level deep, keeping SKILL.md as an overview + routing table.
Tighten RULE ZERO and the intro paragraph to a single directive sentence each; the hallucination risk is already implied by the 'never guess' mandate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient and packed with genuinely non-obvious content (tool names, MSigDB set-name conventions), but it repeats the 'final-answer discipline / map computed value to options' point and leans on motivational prose ('RULE ZERO', 'this is exactly what models hallucinate') that could be trimmed. Not the level-3 lean baseline because some tokens are rhetorical reinforcement rather than instruction. | 2 / 3 |
Actionability | Highly actionable: a concrete routing table mapping question patterns to specific tools and parameters, plus complete, copy-paste-ready Python for ORF counting, restriction digests, and gamete ratios with named functions and example calls. | 3 / 3 |
Workflow Clarity | Clear numbered sequences (Parse → Resolve → Query → Check → Answer; the 6-step 'in X but not Y' recipe) with explicit error-recovery feedback loops ('If a tool errors on a name, re-derive the name', 'If RestrictionBatch raises... re-run') and a checkpoint for 'Insufficient information' only on a genuine empty result. | 3 / 3 |
Progressive Disclosure | No bundle files exist, so all content sits inline in one ~16KB SKILL.md. Sections are well-organized and references are not nested, but the detailed computational code blocks and per-database recipes are content that could be split into one-level-deep reference files, matching the 'content that should be separate is inline' anchor. Not level 1 because structure is genuinely clear; not level 3 because nothing is offloaded to references. | 2 / 3 |
Total | 10 / 12 Passed |