vest-error-key-lifecycle

Use when adding, removing, or renaming a Vest validation `test(...)` in this repo's suite.js / *Suite.js files, or when touching a validation error key like "team-members" / "project-officer". Maps the full producer→consumer chain (test → getErrors() → convertCodeForDisplay("validation", key) → error-list render → button gating) so a suite edit updates every dependent label, renderer, and test. Trigger on any Vest suite change.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

82%Weight 40%Scale 1-5

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

The body is highly actionable, repo-specific, and well-structured with a clear chain diagram and a checklist-style reference table, assuming Claude's competence throughout. The main gaps are minor: slightly distributed validation and a single-file layout that leaves little room for progressive disclosure.

Suggestions

Add an explicit validate→fix→retry gate after a suite edit (e.g., run the co-located suite test, then only proceed to committing the rename once all four nodes are updated and tests pass) to lift workflow_clarity to 5.

Tighten the Overview and Real-World Impact sections to a few terse lines each to move conciseness from 4 to 5.

If the Vest v6 rules grow, move them to a references/vest-v6-rules.md file and link to it, demonstrating a one-level-deep progressive-disclosure split.

Dimension	Reasoning	Score
Conciseness	Lean and focused on repo-specific knowledge Claude lacks (the producer→consumer chain, lint blind spots, Vest v6 pitfalls) with no padding about basic concepts, though the Overview and Real-World Impact narratives could be trimmed slightly.	4 / 5
Actionability	Provides copy-paste-ready commands (grep with exact flags), specific file paths for every chain node, and exact API rules (e.g. enforce(n).isNotNullish().greaterThan(0)), covering remove/add/rename cases concretely.	5 / 5
Workflow Clarity	The chain is clearly sequenced and the Quick Reference table acts as a per-node checklist with verification steps (grep, run tests, confirm no empty render), but validation is distributed rather than a single explicit validate→fix→retry gate.	4 / 5
Progressive Disclosure	Well-organized into clearly labeled sections with a single clearly-signaled cross-reference (dead-code-after-removal-sweep skill) and content appropriately inline, though at ~92 lines and with no bundle files it does not demonstrate a multi-file split.	4 / 5
	Total	17 / 20 Passed

Description

92%Weight 40%Scale 1-5

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 is highly specific, repo-grounded, and clearly distinguishes the skill's niche with explicit what/when trigger guidance. Trigger-term coverage is strong but specialized to the Vest domain rather than offering broad synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions (adding/removing/renaming tests) and maps the full producer→consumer chain across labels, renderers, button-gating, and tests, giving comprehensive domain coverage.	5 / 5
Completeness	Explicitly answers both what ("Maps the full producer→consumer chain so a suite edit updates every dependent label, renderer, and test") and when ("Use when adding, removing, or renaming..."; "Trigger on any Vest suite change") with concrete trigger phrases.	5 / 5
Trigger Term Quality	Strong, natural trigger phrasing ("adding, removing, or renaming a Vest validation test", file patterns like suite.js, example keys "team-members"/"project-officer", "Trigger on any Vest suite change") with good coverage, though all terms are within a specialized Vest domain.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear, narrow niche (Vest suite error-key lifecycle in this repo) with distinct, repo-specific triggers and minimal risk of firing for unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: HHS/OPRE-OPS
Path: .claude/skills/vest-error-key-lifecycle/SKILL.md
Commit: b61c72b

Reviewed: 19 hours 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.