CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

adsorbate-and-intermediate-generation

Use this skill for generating adsorbates and reaction intermediates, standardizing molecular inputs, and preparing structures for adsorption placement.

Quality

80%

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 ./skills/adsorbate-and-intermediate-generation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 tight, well-structured body that delegates to the create_molecule_from_smiles tool with concrete parameter and return-contract guidance. Adding a worked example invocation and a quick output sanity check would round out actionability and workflow clarity.

DimensionReasoningScore

Conciseness

The 37-line body is lean and assumes Claude's competence: no basic-concept explanations, no padding, and every section carries operational information (parameter choices, return contract, handoff). The only near-redundancy (Quick Start step 1 vs. Workflow step 1) is a summary-versus-detail pattern, not over-explanation.

5 / 5

Actionability

Concrete, executable guidance is present: fmt values ("fmt=poscar writes a boxed .vasp"), output_path as a prefix, box_padding semantics, and the full return-field contract (formula, natatoms, xyz_file_rel, poscar_file_rel, box_size). It falls short of 5 because no example tool invocation or worked SMILES-to-output example is shown, leaving a minor gap in copy-paste readiness.

4 / 5

Workflow Clarity

The sequence is clear (normalize chemistry → generate one canonical file → hand off returned paths) with an explicit pre-flight checkpoint ("Resolve ambiguous protonation, charge, or radical assumptions before calling the tool") and an unresolved-assumptions report in the Output Contract. It stops short of 5 because there is no post-generation verification step (e.g., sanity-check natatoms/formula against the expected species).

4 / 5

Progressive Disclosure

The skill is under 50 lines with no external references needed and no bundle files present; sections (Overview, Quick Start, Suggested tools, Workflow, Output Contract, References) are well-organized and the single cross-skill pointer is one level deep and clearly signaled, satisfying the simple-skill case for a top score.

5 / 5

Total

18

/

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.

A specific, domain-appropriate description with good natural keywords, but it lacks the explicit 'when to use' trigger clause that the rubric requires for full completeness. Adding a 'Use when...' sentence naming concrete triggers (SMILES, adsorbate, intermediate, .xyz/POSCAR) would lift both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g., "Use when the user asks to create an adsorbate or reaction intermediate from a SMILES string, or to prepare molecule files (.xyz/POSCAR) for adsorption placement on a slab."

Include the concrete input/output vocabulary users would naturally mention — "SMILES", "molecule", ".xyz", "POSCAR" — to broaden trigger-term coverage.

Tighten "standardizing molecular inputs" and "preparing structures" into more distinct, format-level actions so the 'what' reads as comprehensive rather than overlapping.

DimensionReasoningScore

Specificity

The description lists three domain-specific actions ("generating adsorbates and reaction intermediates, standardizing molecular inputs, and preparing structures for adsorption placement"), matching the several-specific-actions anchor with minor gaps — it names no concrete input formats or outputs (e.g., SMILES, .xyz, POSCAR) that would push it to comprehensive coverage.

4 / 5

Completeness

The 'what' is clear (generate/standardize/prepare adsorbate structures), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric explicitly caps at 3. The 'when' is only weakly implied by the domain framing.

3 / 5

Trigger Term Quality

Natural niche keywords are present ("adsorbates", "reaction intermediates", "adsorption placement"), which users in this domain would actually say. It falls short of 5 because common variations like "SMILES", "molecule", or file extensions (.xyz, POSCAR) are absent, but keyword coverage is noticeably better than the missing-common-variations level of 3.

4 / 5

Distinctiveness Conflict Risk

"Adsorbates", "reaction intermediates", and "adsorption placement" carve out a distinct catalysis-preparation niche, but the description overlaps minorly with general molecule-generation skills and with the adjacent adsorption-site-screening handoff it feeds, so it is mostly distinct rather than a clear 5.

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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/CatMaster

Path

skills/adsorbate-and-intermediate-generation/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.