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.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Risky

Do not use without reviewing

Quality

Content

57%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-organized with a clear 5-step workflow, error handling, and an appropriately split one-level reference file, scoring well on progressive disclosure. It loses points for vague described-only examples, an implicit rather than explicit validation loop, and mild Overview redundancy.

Suggestions

Replace the abstract 'Input:/Output:' examples with an actual YAML before/after snippet (e.g. a mis-indented 'steps:' block and the corrected version).

Embed an explicit validate-fix-retry checkpoint in the Instructions, e.g. 'Run the target linter/dry-run; if it fails, fix and re-run before outputting the patch.'

Trim the Overview, which duplicates the opening line and the Instructions, or fold it into the Instructions to remove redundancy.

Dimension	Reasoning	Score
Conciseness	The body is lean and does not re-explain YAML concepts, but the Overview restates the description/Instructions and the Examples section adds little value, so it could be tightened.	2 / 3
Actionability	Concrete numbered steps and a real follow-up command ('kubectl apply --dry-run=client') are present, but the Examples are described input/output with no actual YAML shown, leaving guidance incomplete.	2 / 3
Workflow Clarity	A clear 5-step sequence exists with a validation checklist and error-handling recovery, but validation is described as an output ('a short validation checklist') rather than explicit gated checkpoints inside the flow.	2 / 3
Progressive Disclosure	The SKILL.md is a concise, well-sectioned overview that points to one real, one-level-deep reference (references/SKILL.full.md, verified to contain actual content), with the link clearly signaled as 'Full detailed guide (kept for reference)'.	3 / 3
	Total	9 / 12 Passed

Description

50%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly identifies the YAML domain but relies on abstract buzzwords ('proactive YAML intelligence') and generic placeholder trigger language rather than concrete capabilities and natural triggers. It answers what and when only weakly, capping every dimension at 2.

Suggestions

Replace the placeholder clause 'Use when appropriate context detected. Trigger with relevant phrases based on skill purpose' with concrete natural triggers such as 'Use when validating, formatting, or fixing .yml/.yaml files, or when working with Kubernetes, GitHub Actions, or Docker Compose configs.'

Add concrete actions to the opening sentence, e.g. 'Validate YAML syntax, normalize formatting, and fix schema mismatches in Kubernetes, GitHub Actions, and Docker Compose files.'

Cover common term variations users would actually say ('validate yaml', 'fix yaml syntax', 'yml', 'config lint').

Dimension	Reasoning	Score
Specificity	The description names the YAML domain ('working with YAML files') but 'Execute proactive YAML intelligence' is abstract buzzword phrasing with no concrete actions like validate, format, or fix listed.	2 / 3
Completeness	A 'when' is present ('when working with YAML files') but the 'Use when...' clause is generic placeholder rather than explicit trigger guidance, and the 'what' is vague, so completeness caps at 2.	2 / 3
Trigger Term Quality	'YAML files' is a natural keyword, but the 'Use when appropriate context detected. Trigger with relevant phrases based on skill purpose' is generic placeholder boilerplate missing common variations like 'validate yaml', '.yml', or 'Kubernetes'.	2 / 3
Distinctiveness Conflict Risk	YAML is a reasonably distinct niche, but the generic trigger language ('appropriate context detected') means it could still overlap with general config-format skills.	2 / 3
	Total	8 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 3022dd3

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.