CtrlK
BlogDocsLog inGet started
Tessl Logo

slab-construction-and-surface-modeling

Use this skill for slab construction, vacuum and layer choices, surface supercell setup, and atom-fixing strategy in heterogeneous catalysis workflows.

66

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

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 instruction-only skill body: it names the exact tools and parameters, sequences the workflow with an explicit destructive-operation guardrail, and defines a concrete output contract. The only notable gap is the absence of example tool invocations for the common cases.

DimensionReasoningScore

Conciseness

The body is lean and assumes domain competence: no padding, no explanation of what slabs or catalysis are, and every line carries tool-specific guidance. It matches the 'every token earns its place' anchor.

5 / 5

Actionability

Guidance is concrete — named tools (build_slab, fix_atoms_by_layers, fix_atoms_by_height, supercell) with specific parameters (slab_thickness, layer_tol, z_ranges, centralize) and real behavioral constraints ('freeze_layers must not exceed the detected layer count'). It is not a 5 because there are no example invocations or command lines a user could copy-paste for the common cases.

4 / 5

Workflow Clarity

A clear three-step sequence with ordering rationale ('Expand cells only after fixing policy is understood') and a guardrail for the destructive operation ('supercell … drops all selective-dynamics information, so do not call it after you have already finalized atom constraints'). The Output Contract also requires reporting whether supercell invalidated prior flags, which serves as a verification checkpoint, so the destructive/batch cap at 3 does not apply; it misses 5 only because there is no explicit validate-and-retry loop.

4 / 5

Progressive Disclosure

The skill is under 50 lines, needs no external reference files (none exist in the bundle), and is organized into well-labeled sections (Overview, Quick Start, Suggested tools, Workflow, Output Contract, References) with a clean hand-off to the adsorption-site-screening skill. This matches the rubric's simple-skill guideline for a full score.

5 / 5

Total

18

/

20

Passed

Description

75%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 solid, domain-pinned description that names concrete capabilities and includes an explicit use-trigger clause. Its main gaps are missing synonym/variation trigger terms and a when-clause phrased as topics rather than as things a user would actually say.

Suggestions

Rewrite the trigger clause in user-phrase form, e.g. 'Use when the user asks to build a slab, choose vacuum or slab thickness, fix/freeze slab atoms, or make a surface supercell' to reach the completeness anchor 5.

Add natural synonym triggers such as 'Miller index', 'surface termination', 'freeze atoms', and 'surface model' that users would plausibly say when they need this skill.

Mention termination/Miller-index selection in the capability list so the description covers what the body actually does and further distinguishes it from generic structure-manipulation skills.

DimensionReasoningScore

Specificity

The description names the domain and four concrete action areas — 'slab construction, vacuum and layer choices, surface supercell setup, and atom-fixing strategy' — matching the 'several specific actions; minor gaps in coverage' anchor. It falls short of 5 because it omits capabilities the body actually covers, such as termination selection and Miller-index handling.

4 / 5

Completeness

Both what and when are present: 'Use this skill for slab construction, … atom-fixing strategy in heterogeneous catalysis workflows' gives capabilities plus an explicit trigger clause, so it clears the 3-cap for missing 'Use when' guidance. It is not a 5 because the when-clause is a topic list rather than concrete user-phrase triggers like 'when the user asks to build a slab or fix slab atoms'.

4 / 5

Trigger Term Quality

Good natural keyword coverage for the domain: 'slab construction', 'supercell', 'atom-fixing', 'heterogeneous catalysis' are phrases users would say. It is not a 5 because common variations like 'Miller index', 'surface model', or 'freeze atoms' are missing.

4 / 5

Distinctiveness Conflict Risk

The 'in heterogeneous catalysis workflows' qualifier gives it a clear niche with distinct triggers, but 'supercell' and 'vacuum' overlap slightly with closely related structure-editing and adsorption skills. It is mostly distinct rather than minimal-conflict, so 4 rather than 5.

4 / 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

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
fernandezbaptiste/CatMaster
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.