Name: ac-criteria-validator
Rating: 65.60000000000001 (1 reviews)
Author: fernandezbaptiste

ac-criteria-validator

Validate acceptance criteria and feature completion. Use when checking if features pass, validating test results, verifying acceptance criteria, or determining feature completion status.

Quality

82%

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

The canonical home for this skill is ac-criteria-validator in fernandezbaptiste/Skrillz

Quality

Content

78%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.

A well-organized body with executable quick-start code, concrete validation rules, and a correctly structured single-script bundle. The main gaps are minor: undefined `project_dir` in the example, no explicit error-recovery guidance for failed test runs, and small redundancy between the intro and Purpose sections.

Suggestions

Show how `project_dir` is obtained (e.g., `project_dir = Path('/repo')`) in the Quick Start so the snippet is fully copy-paste ready.

Add a short error-handling note to the Workflow or State Transition section (e.g., what `criteria_results` looks like and what to report when the test suite crashes or coverage is below 80).

Merge the intro line into the Purpose section to remove the duplicated statement of the skill's function.

Dimension	Reasoning	Score
Conciseness	The body is efficient with terse bullets and code blocks, but the intro line "Validate acceptance criteria and determine feature completion" duplicates the Purpose section, and the 27-line JSON example could be trimmed. Anchor 4 (efficient, minor trimmable instances) fits; not 5 because not every token earns its place, and not 3 because there is no real padding.	4 / 5
Actionability	Quick Start provides near copy-paste-ready code ("from scripts.criteria_validator import CriteriaValidator", "result = await validator.validate_feature('auth-001')") matching the real script, and the YAML validation rules are concrete. Minor gaps: `project_dir` is undefined in the snippet and workflow steps are labels rather than commands. Anchor 4, not 5.	4 / 5
Workflow Clarity	The five-step Workflow (Load/Discover/Execute/Analyze/Report) is a clear sequence, and the Validation Rules thresholds plus the State Transition guardrail ("passes can ONLY transition false → true") supply most checkpoints. Not 3 because checkpoints are more than implicit; not 5 because there is no explicit error-recovery loop for failed or partial test runs.	4 / 5
Progressive Disclosure	The ~115-line body is cleanly sectioned, the Quick Start import path matches the actual bundle file (scripts/criteria_validator.py), and implementation detail is delegated via a clearly signaled one-level-deep pointer ("See scripts/criteria_validator.py for full implementation"). Matches anchor 5: clear overview, well-signaled references, easy navigation.	5 / 5
	Total	17 / 20 Passed

Description

78%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.

A well-structured description with an explicit when-clause and natural trigger phrases. Its main weakness is that the capability list is narrow — trigger phrases restate one core action rather than enumerating the skill's distinct capabilities (test execution, coverage thresholds, lint/type checks).

Suggestions

Broaden the what-statement to enumerate distinct capabilities, e.g. "Validate acceptance criteria by running test suites, checking coverage thresholds, and verifying code analysis; determine feature completion status."

Add common synonyms to the trigger clause such as "AC", "tests pass", or "definition of done" to improve both specificity and trigger coverage.

Clarify what "validating test results" means (running the associated test suite) to reduce overlap with a generic test-execution skill.

Dimension	Reasoning	Score
Specificity	"Validate acceptance criteria and feature completion" names the domain with two concrete actions, but the when-clause phrases ("checking if features pass, validating test results") are restatements of the same action rather than distinct capabilities; actual capabilities like coverage threshold checks are absent. Matches anchor 3 (1-2 concrete actions, not comprehensive), not 4, since several distinct actions are not listed.	3 / 5
Completeness	Explicitly answers what ("Validate acceptance criteria and feature completion") and when ("Use when checking if features pass, validating test results, verifying acceptance criteria, or determining feature completion status") with concrete trigger phrases. This matches the anchor 5 example structure exactly.	5 / 5
Trigger Term Quality	Natural phrases like "checking if features pass", "validating test results", and "verifying acceptance criteria" match what users would say, but common synonyms ("AC", "tests pass", "definition of done") are missing. Anchor 4 (good coverage, a few natural terms missing) fits better than 5's comprehensive coverage.	4 / 5
Distinctiveness Conflict Risk	The acceptance-criteria/feature-completion niche is mostly distinct, but "validating test results" risks overlap with a generic test-execution skill. Anchor 4 (mostly distinct, minor overlap risk) fits better than 5's minimal conflict risk.	4 / 5
	Total	16 / 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: fernandezbaptiste/Skrillz
Path: .claude/skills/ac-criteria-validator/SKILL.md
Commit: 93ed392

Reviewed: 14 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.