yaml-master
Execute proactive YAML intelligence: automatically activates when working with YAML files. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
25
17%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Risky
Do not use without reviewing
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/productivity/002-jeremy-yaml-master-agent/skills/yaml-master/SKILL.mdQuality
Discovery
0%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 almost entirely composed of vague placeholder language and circular statements. It fails to communicate any concrete capabilities, provides no meaningful trigger terms, and offers no guidance on when to select this skill. It reads as a template that was never filled in with actual content.
Suggestions
Replace 'proactive YAML intelligence' with specific concrete actions such as 'Validates YAML syntax, converts between YAML and JSON, formats and lints YAML configuration files'.
Add explicit trigger terms users would naturally use, e.g., 'Use when working with .yml or .yaml files, Kubernetes manifests, Docker Compose files, CI/CD configs, or when the user mentions YAML parsing, validation, or formatting'.
Replace the placeholder 'Use when appropriate context detected' with a genuine 'Use when...' clause listing specific scenarios and file types.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses extremely vague language like 'proactive YAML intelligence' and 'working with YAML files' without listing any concrete actions. No specific capabilities such as parsing, validating, formatting, or converting are mentioned. | 1 / 3 |
Completeness | The 'what' is essentially absent—'YAML intelligence' is not a description of capabilities. The 'when' clause ('Use when appropriate context detected') is a vacuous tautology that provides no actionable guidance for skill selection. | 1 / 3 |
Trigger Term Quality | The phrase 'relevant phrases based on skill purpose' is a meaningless placeholder that provides zero actual trigger terms. 'YAML files' is the only natural keyword, and the rest is generic filler with no useful variations like '.yml', '.yaml', 'config files', etc. | 1 / 3 |
Distinctiveness Conflict Risk | The description is so generic that it could conflict with any skill that touches configuration files, data serialization, or file editing. There are no distinct triggers or specific use cases to differentiate it. | 1 / 3 |
Total | 4 / 12 Passed |
Implementation
35%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides a reasonable high-level framework for YAML validation and formatting but falls short on actionability — it describes what to do abstractly without providing any concrete YAML examples, executable code, or specific patterns. The workflow is logically sequenced but lacks validation checkpoints and feedback loops. The content reads more like a task description than an actionable skill that teaches Claude something it doesn't already know.
Suggestions
Add concrete, copy-paste-ready YAML examples showing actual before/after for each example scenario (e.g., show the mis-indented YAML and the corrected version with annotations).
Include specific validation commands and patterns for each target system (Kubernetes, GitHub Actions, Docker Compose) rather than just mentioning them in passing.
Add explicit feedback loops in the workflow: e.g., 'If step 3 finds schema violations, fix and re-run validation before outputting the patch.'
Remove or condense the Prerequisites section — Claude doesn't need to be told it needs the YAML file to work on YAML files.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably structured but includes some unnecessary framing (e.g., 'Proactive YAML intelligence' repeated, the Prerequisites section states obvious things like 'Permission to edit the file(s)'). The overview restates the header. Could be tightened. | 2 / 3 |
Actionability | The skill provides no executable code, no concrete YAML snippets, no actual commands beyond a brief mention of `kubectl apply --dry-run=client`. The examples are described abstractly ('a workflow with a mis-indented steps: block') rather than showing actual input/output YAML. This is vague direction, not concrete guidance. | 1 / 3 |
Workflow Clarity | Steps are listed in a logical sequence (parse → normalize → validate → identify risks → output), and there's mention of follow-up validation commands. However, there are no explicit validation checkpoints or feedback loops (e.g., 'if validation fails, fix and re-validate'). The error handling section partially compensates but lacks specificity. | 2 / 3 |
Progressive Disclosure | References a full guide at `${CLAUDE_SKILL_DIR}/references/SKILL.full.md` and external resources, which is good structure. However, no bundle files were provided, so the referenced file doesn't exist. The main content itself is somewhat thin, suggesting important detail may be missing rather than properly delegated. | 2 / 3 |
Total | 7 / 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
6e9558f
- 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.