CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chemical-structure-converter

Convert between IUPAC names, SMILES strings, molecular formulas, and common names for chemical compounds. Supports SMILES validation, batch processing, structure standardization, and cheminformatics database preparation for drug discovery workflows.

Quality

69%

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/Other/chemical-structure-converter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 is well-structured with executable code, an accurate CLI reference, and thoughtful domain-specific error handling (no-fabrication rule, PubChem fallback URLs, batch summary requirement). Its main weaknesses are token padding that duplicates the description and teaches known concepts, and three factually inaccurate claims about the bundled script (DB_VERSION, CSV batch input, automatic PubChem lookup) that undermine trust in the guidance.

Suggestions

Fix the inaccuracies against scripts/main.py: DB_VERSION does not exist (either add it or remove the maintenance instruction), there is no CSV/batch CLI flag, and the script does not query PubChem — rephrase as a manual fallback or implement it.

Delete the duplicate intro/Key Capabilities prose and the SMILES Quick Reference section; Claude already knows SMILES syntax and the frontmatter already carries the capability summary.

Replace the generic workflow step "Return a structured result separating assumptions, deliverables, risks, and unresolved items" with a concrete description of the actual conversion output (or drop it).

DimensionReasoningScore

Conciseness

Mostly efficient (tables, tight code blocks, CLI examples), but the intro paragraph and "Key Capabilities" list restate the frontmatter description, and the "SMILES Quick Reference" ("C = aliphatic carbon, = = double bond") teaches syntax Claude already knows. Not 2: the padding is limited to a few sections and the bulk is lean.

3 / 5

Actionability

Concrete, copy-paste-ready Python and CLI examples and an accurate parameter table — but several executable claims don't match the bundle: "DB_VERSION" does not exist in scripts/main.py, "Batch input via CSV or plain text list is also supported" has no corresponding CLI support, and "The script should automatically query this endpoint" (PubChem) is not implemented. Not 4: these are more than minor gaps; a user following the maintenance and batch instructions would fail.

3 / 5

Workflow Clarity

The 5-step workflow is sequenced with checkpoints: a "Quick Check" verification step, an explicit fallback message for missing identifiers, and per-failure-mode error handling. Batch-mode validation is present (per-compound warnings plus the required "X/N converted, Y failed" summary line), so the batch cap does not apply. Not 5: step 4 ("Return a structured result separating assumptions, deliverables, risks, and unresolved items") is generic template language rather than a concrete action.

4 / 5

Progressive Disclosure

Well-sectioned single-file skill with clear headers; the one referenced bundle path (scripts/main.py) exists and external references are flat, clearly-listed URLs one level deep. Not 5: at ~170 lines, content like the SMILES Quick Reference, Common Pitfalls, and References lists is inlined rather than split, and the guideline's 5-with-sections-only exception applies only to skills under 50 lines.

4 / 5

Total

14

/

20

Passed

Description

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

The description answers "what" concretely with strong domain-specific trigger terms (IUPAC, SMILES, molecular formula), but entirely lacks a "when to use" trigger clause, and omits InChI and other synonym coverage. It is third-person, appropriately concise, and clearly distinguishable from neighboring skills.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user mentions chemical compounds, SMILES strings, IUPAC names, molecular formulas, or needs to convert or validate chemical identifiers."

Include missing synonyms and formats to broaden triggering: InChI, InChIKey, CAS numbers, and "chemical structure" as a natural phrase.

Trim the trailing scope claim ("cheminformatics database preparation for drug discovery workflows") or make it concrete, since it broadens the skill's apparent scope and raises overlap risk with other cheminformatics skills.

DimensionReasoningScore

Specificity

"Convert between IUPAC names, SMILES strings, molecular formulas, and common names" plus "Supports SMILES validation, batch processing, structure standardization" lists several concrete actions with named formats. Not 5: minor coverage gaps — InChI (supported per the body) and identifier lookup are absent from the description.

4 / 5

Completeness

The "what" is clear (interconversion of chemical identifiers plus validation/batch support), but there is no "Use when..." clause; "for drug discovery workflows" only weakly implies when. Per the rubric guideline, a missing explicit trigger clause caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms users would say are present: "IUPAC names", "SMILES", "molecular formulas", "chemical compounds", "convert". Not 5: misses common synonyms and variations such as InChI, CAS numbers, "chemical structure", or file formats like .smi.

4 / 5

Distinctiveness Conflict Risk

A clear niche (chemical identifier conversion) with distinct triggers (IUPAC, SMILES, molecular formula). Not 5: the tail "structure standardization, and cheminformatics database preparation" broadens scope and creates minor overlap risk with other cheminformatics/registration skills.

4 / 5

Total

15

/

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/Other/chemical-structure-converter/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.