yaml-master
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill yaml-masterExecute proactive YAML intelligence: automatically activates when working with YAML files. Use when appropriate context detected. Trigger with relevant phrases based on skill purpose.
Validation
81%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 13 / 16 Passed | |
Implementation
57%This skill has good organizational structure and appropriate progressive disclosure, but lacks the concrete, executable examples that would make it truly actionable. The instructions describe processes abstractly rather than showing actual YAML code with before/after comparisons. The workflow would benefit from explicit validation checkpoints integrated into the steps.
Suggestions
Add concrete YAML code examples showing actual before/after fixes (e.g., a real mis-indented GitHub Actions workflow and its correction)
Include executable validation commands inline in the workflow steps rather than just mentioning them in the output section
Add explicit validation checkpoint in step 3-4: 'Run validation command, if errors persist, return to step 1'
Remove redundant overview text - the skill description already covers what it does
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Generally efficient but includes some unnecessary framing ('Proactive YAML intelligence' repeated, 'This skill activates when...'). The prerequisites and instructions could be tighter - Claude knows what YAML files are and doesn't need the overview restated. | 2 / 3 |
Actionability | Instructions describe what to do but lack concrete code examples. No actual YAML snippets showing before/after fixes, no executable validation commands inline. Examples section describes inputs/outputs abstractly rather than showing actual YAML. | 2 / 3 |
Workflow Clarity | Steps are numbered and sequenced logically, but validation checkpoints are implicit rather than explicit. Missing feedback loops for the edit-validate-retry cycle. Output section mentions follow-up commands but doesn't integrate them into the workflow. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections. References external detailed guide and external resources appropriately. Content is well-organized with overview, instructions, output, error handling, and examples as distinct sections. | 3 / 3 |
Total | 9 / 12 Passed |
Activation
7%This description is extremely weak, using circular meta-language instead of concrete capabilities. It fails to explain what the skill actually does with YAML files and provides no meaningful trigger guidance. The phrase 'Trigger with relevant phrases based on skill purpose' is a placeholder that provides zero value for skill selection.
Suggestions
Replace vague language with specific actions (e.g., 'Validates YAML syntax, converts between YAML and JSON, formats and lints YAML configuration files')
Add concrete trigger terms users would actually say (e.g., 'Use when working with .yml or .yaml files, configuration files, docker-compose, Kubernetes manifests, or CI/CD pipelines')
Remove circular meta-descriptions like 'appropriate context detected' and 'relevant phrases based on skill purpose' - these provide no useful information for skill selection
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'proactive YAML intelligence' and 'appropriate context detected' without describing any concrete actions. No specific capabilities are listed. | 1 / 3 |
Completeness | The 'what' is essentially missing (no concrete actions described), and the 'when' is circular and meaningless ('Use when appropriate context detected'). Neither question is answered. | 1 / 3 |
Trigger Term Quality | The only natural keyword is 'YAML files'. Phrases like 'relevant phrases based on skill purpose' and 'appropriate context detected' are meta-descriptions, not actual trigger terms users would say. | 1 / 3 |
Distinctiveness Conflict Risk | Mentioning 'YAML files' provides some specificity to the file format, but the lack of concrete actions means it could conflict with any other YAML-related skill. The vague language doesn't establish a clear niche. | 2 / 3 |
Total | 5 / 12 Passed |
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.