impl-validator

Validate implementations against stated goals and return structured pass/warn/fail verdicts.

Updated Nov 9, 2023
One-click install
npx skills add https://github.com/oresttokovenko/dot-files --skill impl-validator-oresttokovenko
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: impl-validator
Source: https://github.com/oresttokovenko/dot-files/tree/main/chezmoi/dot_agents/skills/impl-validator
Command: npx skills add https://github.com/oresttokovenko/dot-files --skill impl-validator-oresttokovenko

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When an AI agent or skill produces output, there is no built-in way to verify the work actually matches the stated goal before the user sees it. This skill acts as a critical second reviewer that catches placeholder text, missing fields, logical contradictions, and convention violations before they reach the user. ## Core Features & Use Cases - Dual-mode operation: Runs as a subagent spawned by other skills via a structured check: block, or directly by the user with a natural-language description of what was done. - Four-step validation protocol: Restates the goal, checks each artifact for existence, completeness, correctness, and convention compliance, then evaluates every provided check explicitly. - Structured verdict report: Produces a table of PASS/WARN/FAIL results per check plus an overall verdict with specific actionable issues, including file paths and line references. - Use Case: After a skill generates a new SKILL.md file, spawn impl-validator with the goal and artifact list to confirm the frontmatter contains name and description, no placeholder text remains, and conventions are followed. ## Quick Start Ask the agent to validate the implementation it just produced by describing the goal and the files it created.

Frequently Asked Questions about impl-validator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I validate an AI agent's output before showing it to the user?

Spawn impl-validator as a subagent with a structured check block containing the goal, the list of artifacts produced, and specific checks to run. It returns a structured report with PASS, WARN, or FAIL per check plus an overall verdict.

What does the impl-validator check in generated files?

It checks existence, completeness, correctness, and convention compliance. This includes detecting placeholder text, copy-paste errors, logical contradictions, missing required frontmatter fields, and violations of project conventions like shebang lines in shell scripts.

Can impl-validator be invoked directly by a user?

Yes, it supports a user mode where you describe what was just done and it infers the goal and artifacts from context. If the goal is ambiguous for critical checks, it asks one clarifying question before proceeding.

What is the difference between PASS, WARN, and FAIL verdicts?

PASS means the check is verified true, WARN means probably fine but worth noting, and FAIL means definitively wrong or missing. Any FAIL makes the overall verdict FAIL; WARNs without FAILs produce an overall WARN.

What issues does impl-validator not check?

It does not check style preferences, performance, whether the goal itself is a good idea, or hypothetical future problems. It only verifies the implementation against the stated goal, flagging actual issues in the current artifacts.