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 configuration files for syntax errors, schema compliance, and common misconfigurations.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to validate, lint, or check YAML files, .yml configs, or configuration syntax.'
Remove the redundant duplicate trigger term and replace with varied 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 criteria. | 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 YAML validation, which narrows the domain somewhat. However, without concrete actions or clear triggers, it could overlap with general YAML editing, linting, or 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/placeholder with no actual instructional content. It contains only generic boilerplate that restates the skill name in various ways without providing any concrete guidance on YAML config validation—no schemas, no validation rules, no code examples, no tool references, and no workflows.
Suggestions
Add concrete, executable code examples for YAML validation (e.g., using Python's `yamllint`, `pyyaml`, or `cerberus` with specific schemas and commands).
Define a clear workflow: load YAML → validate against schema → report errors → fix and re-validate, with explicit validation checkpoints.
Include specific YAML config validation rules, common pitfalls (indentation, type mismatches, required fields), and example valid/invalid YAML snippets.
Remove all boilerplate sections ('When to Use', 'Example Triggers', 'Capabilities') that add no actionable information and replace with actual validation patterns and tool-specific guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know and provides zero domain-specific information about YAML config validation. Every section restates the skill name without adding substance. | 1 / 3 |
Actionability | There are no concrete code examples, commands, validation rules, YAML schemas, or any executable guidance whatsoever. The content only describes what the skill supposedly does in vague, abstract terms without actually instructing Claude how to do anything. | 1 / 3 |
Workflow Clarity | No workflow steps are defined. There is no sequence of operations, no validation checkpoints, and no error handling guidance for YAML config validation tasks. | 1 / 3 |
Progressive Disclosure | The content is a flat, monolithic block of generic placeholder text with no references to detailed materials, no links to schemas or examples, and no meaningful structural organization beyond boilerplate headings. | 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
87f14eb
- 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.