yaml-config-validator
Yaml Config Validator - Auto-activating skill for DevOps Basics. Triggers on: yaml config validator, yaml config validator Part of the DevOps Basics skill category.
34
3%
Does it follow best practices?
Impact
90%
0.91xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/01-devops-basics/yaml-config-validator/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a placeholder that restates the skill name without providing any meaningful information about what the skill does or when it should be used. It lacks concrete actions, natural trigger terms, and explicit usage guidance, making it nearly useless for skill selection among multiple options.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Validates YAML syntax, checks configuration files against schemas, identifies formatting errors and missing required fields.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to validate YAML, check a .yml config file, lint YAML syntax, or verify configuration correctness.'
Remove the redundant duplicate trigger term and replace with diverse natural keywords users would actually say, such as 'YAML', '.yml', 'config validation', 'syntax check', 'lint YAML'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names a domain ('yaml config validator') but describes no concrete actions. There are no specific capabilities listed such as 'validates YAML syntax', 'checks schema compliance', or 'reports configuration errors'. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and there is no explicit 'when to use' guidance. The 'Triggers on' line is just the skill name repeated, not meaningful trigger conditions. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are the redundant 'yaml config validator' repeated twice. Missing natural user terms like 'YAML', 'validate YAML', 'config file', '.yml', 'syntax check', 'YAML lint', or 'configuration validation'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'yaml config validator' provides some specificity to a niche (YAML validation), but the lack of concrete actions or scope means it could overlap with general YAML editing, linting, or broader DevOps configuration skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no substantive content. It repeatedly references 'yaml config validator' without ever explaining what it does, how to do it, or providing any actionable guidance. The entire body consists of generic boilerplate that could apply to any skill topic.
Suggestions
Add concrete, executable examples of YAML validation using specific tools (e.g., `yamllint`, `yq`, Python's `pyyaml` or `strictyaml`, or `ajv` for JSON Schema-based validation of YAML).
Define a clear workflow: load YAML → validate syntax → validate against schema → report errors, with specific commands and code snippets at each step.
Include example YAML configs with common errors and show expected validation output, so Claude knows what correct vs incorrect looks like.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that describe the skill meta-information rather than providing actual technical instruction.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, repeats 'yaml config validator' excessively, and provides zero actual technical content about YAML validation. | 1 / 3 |
Actionability | There are no concrete code examples, commands, tool references, or executable guidance. The skill describes what it could do in abstract terms ('provides step-by-step guidance') without actually providing any guidance. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. There are no validation checkpoints, no sequences, and no actual instructions for performing YAML config validation. | 1 / 3 |
Progressive Disclosure | The content is a flat, uninformative page with no references to detailed materials, no links to examples or schemas, and no meaningful structure beyond generic section headers. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3076d78
- 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.