CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

tooluniverse-chemical-safety

Chemical safety and toxicology assessment integrating ADMET-AI predictions, CTD toxicogenomics, PubChemTox experimental data, GHS/IARC hazard classification, and exposure-context analysis. Use for chemical hazard identification, occupational/consumer-product toxicity, dose-response evaluation, and acute (LD50) vs chronic toxicity assessment. Distinguishes drug toxicity from environmental chemical toxicity.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers a well-sequenced, highly actionable 8-phase workflow with tool parameters, fallbacks, evidence grading, and a completeness checklist. Its weaknesses are redundant framing/summary sections that pad the token cost, and progressive disclosure that is well designed on paper but broken in practice because every referenced detail file is missing from the bundle.

Suggestions

Ship the referenced bundle files (phase-procedures-detailed.md, report-templates.md, evidence-grading.md, phase-details.md, test_skill.py) or remove/trim the dangling references so progressive disclosure actually works.

Delete the redundant framing: the generic "Comprehensive chemical safety analysis integrating..." sentence, the "When to Use This Skill" triggers section (duplicates the frontmatter description), and the closing Summary section — this tightens conciseness without losing guidance.

Add an explicit validation step to the batch screening workflow (e.g., check SMILES validity in Phase 0 before batch prediction), since invalid SMILES are called out as a known ADMET-AI failure mode under Limitations.

DimensionReasoningScore

Conciseness

Mostly dense and useful (tool signatures with parameter types, fallbacks, limitations), but there is noticeable slack: the generic sentence "Comprehensive chemical safety analysis integrating predictive AI models, curated toxicogenomics databases, regulatory safety data, and chemical-biological interaction networks" restates the frontmatter description, the "When to Use This Skill" triggers section largely duplicates the description's triggers, and the closing "Summary" section (Total tools / Best for / Outputs) repeats earlier content. Fits 'mostly efficient but includes some unnecessary explanation or could be tightened' better than the score-4 'minor instances' anchor, though not the 'several padded sections' of score 2.

3 / 5

Actionability

Concrete, executable guidance throughout: tool calls with exact parameter names and types ("ADMETAI_predict_toxicity (`smiles`: list[str])"), install dependency note ("pip install tooluniverse[ml]"), fallback tools for failures, and live-verified response shapes for DrugProps tools. Minor gaps keep it below the copy-paste-ready score-5 anchor: some tool names are elided with shorthand ("FDA_get_boxed_warning_info_by_drug_name / _contraindications_ / _adverse_reactions_"), and there is no worked end-to-end example for a common case.

4 / 5

Workflow Clarity

The 8-phase sequence is explicit (ASCII pipeline plus per-phase tool lists) with real checkpoints: Phase 0 disambiguation always first, a Mandatory Completeness Checklist, "No data" handling, and fallback strategies for failed tools (STITCH → STRING, ADMET-AI unavailable → CTD/PubChemTox). Below score 5 because full decision logic and error-recovery detail is delegated to phase-procedures-detailed.md, and the batch screening pattern has no explicit validation step despite "Invalid SMILES cause ADMET-AI failures" being a known failure mode listed under Limitations — minor validation gaps matching the score-4 anchor.

4 / 5

Progressive Disclosure

The design is good — an overview body with clearly signaled one-level-deep references ("See phase-procedures-detailed.md", a dedicated Reference Files section) — but the bundle contains no reference files at all: phase-procedures-detailed.md, report-templates.md, evidence-grading.md, phase-details.md, and test_skill.py are all absent, so the references dangle and the disclosure structure cannot actually function. Per the guideline to score against the actual bundle structure, this falls to 'some structure but could be better organized' rather than the score-4 'most content appropriately placed' anchor.

3 / 5

Total

14

/

20

Passed

Description

88%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: third-person voice, explicit 'Use for' triggers, concrete action and data-source enumeration, and a deliberate drug-vs-environmental boundary. Weaknesses are limited to a few missing natural synonyms and minor overlap risk with adjacent ADMET/drug-safety skills.

DimensionReasoningScore

Specificity

Multiple concrete actions are named — "chemical hazard identification", "occupational/consumer-product toxicity", "dose-response evaluation", "acute (LD50) vs chronic toxicity assessment" — alongside the specific data sources integrated (ADMET-AI, CTD, PubChemTox, GHS/IARC). Coverage of the skill's capabilities is comprehensive; the score-4 anchor ('minor gaps in coverage') fits less well than the score-5 'multiple specific concrete actions; comprehensive coverage'.

5 / 5

Completeness

The 'what' is explicit ("Chemical safety and toxicology assessment integrating ADMET-AI predictions, CTD toxicogenomics, PubChemTox experimental data, GHS/IARC hazard classification, and exposure-context analysis") and the 'when' is an explicit trigger clause ("Use for chemical hazard identification, occupational/consumer-product toxicity, dose-response evaluation, and acute (LD50) vs chronic toxicity assessment"). Both are answered concretely, matching the score-5 anchor; the score-4 anchor's 'when could be more explicit' does not apply since the trigger phrases are enumerated.

5 / 5

Trigger Term Quality

Natural terms are well covered — "chemical safety", "toxic", "toxicity", "hazard", "LD50", "dose-response", "occupational" — but common synonyms users would say are missing (e.g., "poison/poisonous", "safety data sheet/SDS", "exposure limits", "carcinogen"). This matches 'good keyword coverage; a few natural terms missing' rather than the fully comprehensive score-5 anchor.

4 / 5

Distinctiveness Conflict Risk

The toxicology/chemical-safety niche is clear and it actively draws a boundary with adjacent skills ("Distinguishes drug toxicity from environmental chemical toxicity"), but "ADMET-AI predictions" and drug-safety language overlap with drug-development/ADMET-profiling skills. This is 'mostly distinct; minor overlap risk with closely related skills' rather than the minimal-conflict score-5 anchor.

4 / 5

Total

18

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

mims-harvard/ToolUniverse

Path

plugin/skills/tooluniverse-chemical-safety/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.