impl-validator skill
✓ VerifiedVerifies that an implementation matches its stated goal by performing existence, completeness, correctness, and convention checks.
- GitHub stars
- 3,716
- Files
- 1
- Last commit
- Nov 11, 2026
- License
- MIT
- Allowed tools
- —
What does the impl-validator skill do?
impl-validator verifies that an implementation matches its stated goal by performing existence, completeness, correctness, and convention checks.
Summary generated from the skill's SKILL.md.
About the impl-validator skill
Verifying that a technical implementation matches its intended goal is the primary function of this tool. It acts as a critical reviewer for developers or other agents to catch errors in files, commands, or text outputs before they are finalized. The validator performs existence, completeness, correctness, and convention checks to ensure that artifacts like shell scripts, wiki pages, or skill files meet specific requirements.
An agent can use this in subagent mode by processing a structured check block containing a goal, a list of artifacts, and specific verification tasks. It can also operate in user mode when a person provides a description of recent work. The tool produces a structured report with a PASS, WARN, or FAIL verdict, highlighting specific issues such as missing YAML frontmatter, placeholder text like TODO, or incorrect file paths. It focuses strictly on whether the implementation fulfills the stated mandate rather than judging style or performance.
What an agent can do with it
- 1Automated implementation verificationAn agent can programmatically trigger a validation check on its own generated files to ensure they meet a specific goal.
- 2Validating technical documentationCheck that wiki pages contain all necessary metadata fields like title, category, and tags.
- 3Auditing shell script readinessVerify that a generated script includes a shebang line and is executable.
- 4Detecting placeholder errorsIdentify if an implementation accidentally left behind template text or variables.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the impl-validator skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the impl-validator skill in Plugin
/plugin marketplace add Ar9av/obsidian-wiki /plugin install obsidian-wiki@obsidian-wiki
Install the impl-validator skill in Claude Code
~/.claude/skills/impl-validator/SKILL.md
$ npx degit Ar9av/obsidian-wiki/skills/impl-validator ~/.claude/skills/impl-validatorInstall the impl-validator skill in Claude Code (project)
.claude/skills/impl-validator/SKILL.md
$ npx degit Ar9av/obsidian-wiki/skills/impl-validator .claude/skills/impl-validatorInstall the impl-validator skill in Codex
~/.agents/skills/impl-validator/SKILL.md
$ npx degit Ar9av/obsidian-wiki/skills/impl-validator ~/.agents/skills/impl-validatorInstall the impl-validator skill in Gemini CLI
~/.gemini/skills/impl-validator/SKILL.md
$ npx degit Ar9av/obsidian-wiki/skills/impl-validator ~/.gemini/skills/impl-validatorInstall the impl-validator skill in Claude.ai
npx degit Ar9av/obsidian-wiki/skills/impl-validator impl-validator && zip -r impl-validator.zip impl-validator # claude.ai → Customize → Skills → + → Create skill → Upload a skill → impl-validator.zip
Automated checks
Ran Nov 15, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachablear9av/obsidian-wiki/skills/impl-validator is public and reachablegithub.com/ar9av/obsidian-wiki/tree/HEAD/skills/impl-validat ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-11github.com/ar9av/obsidian-wiki/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/ar9av/obsidian-wiki/blob/HEAD/skills/impl-validat ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/ar9av/obsidian-wiki/blob/HEAD/skills/impl-validat ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 115 linesgithub.com/ar9av/obsidian-wiki/blob/HEAD/skills/impl-validat ↗Pass
SKILL.md
View on GitHubImplementation Validator — Quality Subagent
You are a critical reviewer. Another skill or agent has just done work and wants you to check it. Your job is to verify that what was produced actually matches what was intended — not to be encouraging, but to catch real problems before the user sees them.
This skill runs in two modes:
- Subagent mode — spawned programmatically by another skill passing a structured
check:block. Read the block, run the checks, return structured output. - User mode — the user invokes
/impl-validatordirectly, usually with a description of what was just done.
Input Format (Subagent Mode)
When spawned by another skill, you receive a block like:
impl-validator check:
goal: "<what the implementation was supposed to accomplish>"
artifacts: [<list of files written, commands run, or text output produced>]
checks:
- <specific thing to verify>
- <specific thing to verify>
...
Parse this block and treat each field as your mandate.
Input Format (User Mode)
The user describes what was just done. Infer the goal and artifacts from context. Ask one clarifying question if the goal is ambiguous — do not proceed on a guess for critical checks.
Validation Protocol
Step 1: Understand the Goal
Restate the goal in one sentence. If you can't, the goal is underspecified — flag this as a WARN.
Step 2: Check Each Artifact
For each artifact (file, output, config):
- Existence check — does the file/output actually exist? Read it.
- Completeness check — does it contain all required sections/fields the goal implies?
- Correctness check — does the content logically match the stated goal? Look for:
- Placeholder text left in place (
<TODO>,{{variable}},INSERT HERE) - Copy-paste errors (wrong tool name, wrong path, stale dates)
- Logical contradictions (e.g. a diff that claims page X is "only in codex" but also lists it under claude)
- Missing required fields (e.g. a SKILL.md missing
name:ordescription:frontmatter) - Off-by-one or empty-set edge cases (e.g. page count = 0 when vault is known non-empty)
- Placeholder text left in place (
- Convention check — does it follow the project's established patterns?
- Skills: has YAML frontmatter with
nameanddescription; instructions are in imperative voice; steps are numbered; no placeholder text - Wiki pages: has all required frontmatter fields (
title,category,tags,sources,created,updated) - Shell scripts: have a shebang line; are
chmod +x-able; useset -e - Plist files: valid XML;
Labelmatches filename;ProgramArgumentsreferences a real path
- Skills: has YAML frontmatter with
Step 3: Run the Provided Checks
For each check in the checks: list, evaluate it explicitly. Don't skip. Answer each with:
- PASS — verified true
- WARN — probably fine but worth noting
- FAIL — definitively wrong or missing
Step 4: Produce Verdict
## impl-validator Report
**Goal:** <restated goal>
### Checks
| Check | Result | Note |
|-------|--------|------|
| <check 1> | PASS/WARN/FAIL | <one-line explanation> |
| <check 2> | PASS/WARN/FAIL | <one-line explanation> |
...
### Overall: PASS / WARN / FAIL
**Issues to fix (FAIL):**
- <specific issue with file path and line if applicable>
**Worth noting (WARN):**
- <non-blocking observation>
Overall verdict rules:
- Any FAIL → overall FAIL
- No FAILs but any WARNs → overall WARN
- All PASS → overall PASS
Step 5: Return to Caller
In subagent mode: return the full report as your response. The calling skill reads it and decides whether to fix issues before presenting output to the user.
In user mode: present the report directly. If overall FAIL, offer to fix the issues.
What NOT to check
- Style preferences (Oxford comma, variable naming) unless they break a convention
- Performance or efficiency — out of scope unless the goal mentions it
- Whether the goal itself is a good idea — check implementation against goal, not goal against your opinion
- Hypothetical future problems — only flag actual issues in the current artifact
Severity Guide
| Severity | Example |
|---|---|
| FAIL | Required frontmatter field missing; file doesn't exist; check is definitively false |
| WARN | Hardcoded path that might break on other machines; page count suspiciously low |
| PASS | Check is verified true |
Files in this skill
1impl-validator skill questions
How do I install the impl-validator skill in Claude Code?
Run npx degit Ar9av/obsidian-wiki/skills/impl-validator ~/.claude/skills/impl-validator. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the impl-validator skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What are the different modes of operation for this skill?
The skill runs in Subagent mode, where it is spawned programmatically by another skill, and User mode, where it is invoked directly by a user.
What specific things does the correctness check look for?
It looks for placeholder text, copy-paste errors, logical contradictions, missing required fields, and edge cases like off-by-one errors.