CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

medchem

Medicinal chemistry screening filters for compound prioritization; use when you need to apply drug-likeness rules, PAINS/structural alerts, and complexity metrics to triage or optimize libraries.

Quality

70%

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

Fix and improve this skill with Tessl

tessl review fix ./scientific-skills/Evidence Insight/medchem/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

53%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.

A well-organized overview with a solid runnable example, but it underuses its own bundle: 40+ KB of references and a ready-made CLI script are never referenced, and the batch workflow lacks any validation or error-recovery steps. Implementation Details also carries hedge-worded prose that could be trimmed.

Suggestions

Add a pointer section so the bundle is discoverable, e.g. "## References" with "Full API details: [references/api_guide.md](references/api_guide.md)", "Complete rule and alert catalog: [references/rules_catalog.md](references/rules_catalog.md)", and "For batch/CLI filtering, see scripts/filter_molecules.py".

Add a validation checkpoint to the example workflow: guard against None molecules from dm.to_mol (e.g. filter or report unparseable SMILES) before running filters, and show an if-error-then-fix-retry loop per the rubric's feedback-loop requirement for batch operations.

Trim hedged prose in Implementation Details ("typically including", "a common convention is", "commonly via") and delete conceptual explanation Claude already knows, replacing it with the concrete API facts from api_guide.md.

DimensionReasoningScore

Conciseness

The body is mostly efficient (lean feature bullets, one focused example), but the Implementation Details section contains explanation Claude could infer — e.g. "Complexity scores approximate synthetic difficulty / structural intricacy using established heuristics" and "Use constraints to encode target-specific design hypotheses... rather than universal 'good/bad' judgments" — plus hedged filler ("typically including", "commonly via", "a common convention is") that adds tokens without adding instruction. Not a 2 because there is no tutorial-style padding and the example is tight; not a 4 because several prose passages could simply be deleted.

3 / 5

Actionability

The Example Usage section is concrete and appears executable end-to-end: real imports, real calls (mc.rules.RuleFilters(rule_list=["rule_of_five", "rule_of_veber"]), mc.structural.CommonAlertsFilters(), mc.complexity.ComplexityFilter(max_complexity=500)), and a CSV export. Not a 5 because only the rules/alerts/complexity path is demonstrated — constraints, groups, catalogs, and the query language get no runnable example, and the bundled CLI script is never shown.

4 / 5

Workflow Clarity

The example lays out a clear numbered sequence (load → rules → alerts → complexity → decide → export), but this is a batch filtering operation with zero validation checkpoints: no handling of unparseable SMILES (dm.to_mol can return None and would crash the pipeline), no verification of filter outputs before export, and no error-recovery loop. The rubric explicitly caps batch-operation workflows without validation at 3; it is not a 2 because the sequence itself is coherent and well-ordered.

3 / 5

Progressive Disclosure

The bundle contains references/api_guide.md, references/rules_catalog.md, and scripts/filter_molecules.py, yet the body never mentions or links to any of them — the full rule catalog needed to populate rule_list and the production CLI script are undiscoverable from SKILL.md. Internal section structure is good, but navigation to the bundle is entirely absent (references buried to the point of nonexistence), which anchors at 2 rather than 3's "references present but not clearly signaled".

2 / 5

Total

12

/

20

Passed

Description

73%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 focused, domain-specific description with good trigger vocabulary and explicit when-guidance. Its main weaknesses are the second-person trigger phrasing ("use when you need") and a when-clause that largely restates the what rather than naming user scenarios.

Suggestions

Rewrite the trigger clause in third person with concrete scenarios, e.g. "Use when screening compound libraries, applying PAINS or structural-alert filters, or enforcing property constraints during lead optimization."

Add widely-used synonyms as trigger terms, such as "Lipinski", "Rule of Five", "SMILES", "toxicophores", and "reactive groups", so the description matches how users naturally phrase these requests.

Mention additional concrete capabilities (functional-group matching, property-window constraints) to round out coverage beyond rules, alerts, and complexity.

DimensionReasoningScore

Specificity

"apply drug-likeness rules, PAINS/structural alerts, and complexity metrics to triage or optimize libraries" names several concrete actions, which would rate 4, but the rubric requires a 1-point reduction for second-person voice: the trigger clause "use when you need to apply..." addresses the reader as "you". Result: 4 - 1 = 3; it is not a 2 because the domain and multiple concrete actions are explicitly named, unlike the minimal "Processes PDF files" anchor.

3 / 5

Completeness

Both parts are present: what ("Medicinal chemistry screening filters for compound prioritization") and when ("use when you need to apply drug-likeness rules, PAINS/structural alerts, and complexity metrics"). Not a 5 because the when-clause is circular — it restates the capabilities rather than giving concrete user scenarios or trigger phrases; not a 3 because the when-guidance is explicit, not merely implied.

4 / 5

Trigger Term Quality

Strong natural domain terms users would actually say: "drug-likeness rules", "PAINS", "structural alerts", "screening", "triage", "compound", "libraries". Not a 5 because common synonyms and concrete handles like "Lipinski", "Rule of Five", "SMILES", "RDKit", or "toxicophores" are absent.

4 / 5

Distinctiveness Conflict Risk

Clear niche with distinctive vocabulary ("PAINS", "drug-likeness rules", "complexity metrics", "compound prioritization") that no general-purpose or adjacent skill would share; conflict risk with other skills is minimal.

5 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

aipoch/medical-research-skills

Path

scientific-skills/Evidence Insight/medchem/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.