CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

yaml

Create and review YAML files with safe indentation, schema-aware structure, and low-surprise serialization. Use when editing YAML config or workflow files.

Quality

71%

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/agent-ops/yaml/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

61%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, token-efficient overview that correctly pushes detail to a one-level-deep reference file. Its weakness is execution concreteness: no runnable validation command and no fix-and-revalidate loop for an operation where silent scalar coercion is the primary risk.

Suggestions

Add one concrete, copy-paste validation command (e.g., yamllint or a python -c 'yaml.safe_load(...)') to the Validation section so the 'run the relevant parser checks' instruction is executable.

Extend the Procedure with an explicit feedback loop: if validation fails, fix the specific scalar or indentation issue and re-run the same check until it passes before closeout.

Add an inline read-when condition to the References pointer (e.g., 'Read when scalar coercion or cross-tool compatibility is risky') so readers can decide whether to open deep-guidance.md without loading it.

DimensionReasoningScore

Conciseness

The body is lean bullet-style guidance with almost no explanation of concepts Claude already knows. Minor over-head exists: a 15-entry table of contents on a ~90-line document and a 'When to use' section that largely restates the frontmatter description. Not level 5 because those few padded sections could be trimmed.

4 / 5

Actionability

Rules like 'Use spaces only; never use tabs' and 'Quote values that could be misread as booleans, numbers, dates, or null' are concrete, but there is no executable command anywhere. Validation is directed abstractly ('Run the relevant parser/schema/tool checks for touched files') without a copy-paste example such as a yamllint or python yaml.safe_load check, leaving key execution details missing.

3 / 5

Workflow Clarity

The three-step Procedure is sequenced and a validation checkpoint is named ('Validate before closeout', 'Fail fast: stop at the first failed gate'), but the validation is never made concrete and there is no fix-and-revalidate feedback loop. Because YAML editing risks silent scalar-coercion errors, the missing explicit recovery loop caps this at the 'validation gaps' anchor rather than level 4.

3 / 5

Progressive Disclosure

The SKILL.md is a genuine overview with the deep material correctly split into references/deep-guidance.md (verified to exist, one level deep, with its own 'Read when' condition). It falls short of level 5 because the in-body pointer is a bare one-liner ('Deep guidance: references/deep-guidance.md') that does not state when to consult it, forcing the reader to open the file to learn its purpose.

4 / 5

Total

14

/

20

Passed

Description

70%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 description that clearly states what the skill does and when to use it in third person with explicit YAML triggers. The main gaps are limited action coverage (only create/review) and a when-clause that omits extension names and synonyms.

Suggestions

Expand the what-clause with more specific actions (e.g., fix indentation errors, migrate flow-style to block-style, validate against schemas) to move specificity from 2 named actions toward comprehensive coverage.

Broaden the trigger terms with file extensions (.yml, .yaml) and natural synonyms such as CI pipelines, docker-compose, or Kubernetes manifests, and cover 'creating' and 'reviewing' not just 'editing'.

DimensionReasoningScore

Specificity

The description names the YAML domain and exactly two concrete actions ('Create and review YAML files'), with the rest being quality modifiers ('safe indentation, schema-aware structure, low-surprise serialization') rather than additional actions. It sits at the 'domain plus 1-2 concrete actions' anchor, below level 4 which requires several listed specific actions.

3 / 5

Completeness

Both 'what' (create/review YAML with safe indentation and schema-aware structure) and an explicit 'Use when editing YAML config or workflow files' clause are present. Level 5 is not reached because the when-clause covers only editing, omitting triggers for creating or reviewing YAML even though both are claimed capabilities.

4 / 5

Trigger Term Quality

Natural phrases like 'editing YAML config or workflow files' would be said by real users, giving good keyword coverage. It falls short of level 5 because file extensions (.yml, .yaml) and common synonyms (e.g., CI pipelines, compose files) are missing.

4 / 5

Distinctiveness Conflict Risk

YAML is a clear niche and both the what and when clauses explicitly name it, keeping conflict risk low. Minor overlap remains with closely related config-format skills (TOML, JSON serialization) that could also trigger on generic 'config files' phrasing, so it does not reach the fully minimal-conflict level 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

jscraik/Agent-Skills

Path

Skills/agent-ops/yaml/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.