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 workflow-sound: exact tool signatures, explicit fallbacks, numeric thresholds, and a mandatory pre-report checklist make the 5-phase process easy to execute correctly. Weaknesses are efficiency and packaging — a redundant restatement of the description, a digressive TDC anecdote, and 300+ lines of inlined reference detail in a single file with no external references.
Suggestions
Delete the restated summary sentence after the 'LOOK UP DON'T GUESS' section (it duplicates the frontmatter description) and trim the TDC oracle verification anecdote to the essential facts: which oracles exist, the SA/Chem_sa_score duplication caveat, and that TDC_load_dataset is broken.
Move stable reference material — the toxicity endpoint glossary, the physicochemical ideal-range table, and the per-phase tool-call listings — into a references/ file (e.g., references/tool-reference.md) and keep SKILL.md as the workflow overview with clearly signaled one-level-deep links.
Compress the opening 'ADMET reasoning' paragraph to its two operative rules (evidence-tier priority and FAIL-is-program-limiting) — the pharmacokinetic first principles ('a drug fails if it can't be absorbed...') are background Claude can be assumed to know.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The bulk is efficient domain-specific operational knowledge (exact tool signatures, thresholds, failure modes Claude cannot be assumed to know), but there is removable padding: line 13 ('Comprehensive pharmacokinetic and toxicity profiling integrating AI-based ADMET predictions, rule-based drug-likeness filters, and experimental benchmarks from curated databases.') restates the frontmatter description verbatim in substance, the opening 'ADMET reasoning' paragraph is partly philosophical, and the TDC oracle section carries a long live-verification anecdote. This fits the level-3 anchor ('mostly efficient but includes some unnecessary explanation or could be tightened') better than level 4, where over-explanation would be only minor. | 3 / 5 |
Actionability | Fully executable guidance throughout: exact call signatures with parameter types flagged ('ADMETAI_predict_physicochemical_properties(smiles=["<SMILES>"])', 'SwissADME_check_druglikeness(operation="check_druglikeness", smiles="<SMILES>")'), a copy-paste install command ('uv pip install \'tooluniverse[ml]\''), concrete numeric verdict rules ('LD50 < 50 mg/kg (FAIL: GHS 1-2)'), and known-failure guidance (TDC_load_dataset 'is currently broken'). Matches the level-5 anchor: copy-paste ready commands covering the common cases. | 5 / 5 |
Workflow Clarity | The 5-phase workflow is clearly sequenced with per-phase goals, explicit error-recovery fallbacks (ADMETAI import failure -> SwissADME; PubChem lookup failure -> user-provided SMILES), a diagnostic ('tooluniverse-doctor'), guidance distinguishing benign console noise from real failures, and a mandatory 10-item completeness checklist before reporting. This matches the level-5 anchor (explicit validation steps, feedback loops, checklists); operations are read-only so the destructive/batch cap does not apply. | 5 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are all absent), so the entire ~314-line skill lives inline in SKILL.md. Section headers and the phase structure are good, but detail that would naturally live in one-level-deep reference files — the toxicity endpoint glossary, per-phase tool reference, and TDC oracle notes — is inlined, matching the level-3 anchor ('content that should be separate is inline'). Not level 2 because structure is strong, not minimal; not level 4 because essentially nothing is offloaded, and a skill of this length would benefit from splitting reference material out of the overview. | 3 / 5 |
Total | 16 / 20 Passed |