# Impl Validator

Independently check whether an implementation matches its stated goal and return...

- Repository: https://github.com/Ar9av/obsidian-wiki (3650 stars)
- Category: Engineering
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add Ar9av/obsidian-wiki --skill impl-validator -g -a claude-code -y`
Codex: `npx skills add Ar9av/obsidian-wiki --skill impl-validator -g -a codex -y`
Cursor: `npx skills add Ar9av/obsidian-wiki --skill impl-validator -g -a cursor -y`
Gemini CLI: `npx skills add Ar9av/obsidian-wiki --skill impl-validator -g -a gemini-cli -y`
Claude Code plugin marketplace: `/plugin marketplace add Ar9av/obsidian-wiki`

## Description

Independently check whether an implementation matches its stated goal and return PASS/WARN/FAIL with actionable issues. Use for second-opinion validation of an implementation or generated output.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Implementation 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:

1. **Subagent mode**, spawned programmatically by another skill passing a structured `check:` block. Read the block, run the checks, return structured output.
2. **User mode**, the user invokes `/impl-validator` directly, 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):

The rest: https://github.com/Ar9av/obsidian-wiki/blob/HEAD/.skills/impl-validator/SKILL.md