create-verifier

• SKILL.mdcore · 8,011 bytes

# Create a verifier

## Goal

Every rule that no test can check still gets checked on every verification round, by a fresh-context agent that sees only the artifact and returns a binary verdict with a location. Tone, fit to the owner's taste, whether a scene reads as intended, whether a summary is faithful: these are judgments, and a judgment made by the same context that produced the artifact is not a check. A verifier is narrow on purpose, one rule family per file, so that a change to one rule does not disturb the others and a failing verdict names one thing. It never sees the conversation, so it cannot be argued into a pass. A verifier is the second choice after a test, because it costs a model call per round and can disagree with itself, and it is retired the moment a mechanical proxy for the rule appears. Its verdict is PASS or FAIL, never a score, because a score invites the generating agent to call seven out of ten good enough. The measure of this skill is that the owner's judgment calls are enforced as reliably as their mechanical rules.

## Objective

Confirm that no deterministic check covers the property, so a verifier is not written where a test would do. Copy the template and write a verifier prompt for one rule family or one kind of artifact, naming the rule ids it enforces, the examples it may read, what counts as a failure and what does not. Register its trigger in the verifier index so the verify-generation skill runs it on matching artifacts. Add a verification entry only when the verifier checks a kind of claim no existing entry describes. Report the file path so the orchestrator can set `verified-by` on the entry. The verifier is done when a fresh agent given only its file and an artifact can reach a defensible verdict without asking anything.

## Tasks

1. Confirm with `skills/create-test/SKILL.md` that no deterministic check covers the property, by walking the catalog once more and recording why each item fails to apply. A property that splits into a mechanical part and a judgment part gets a test for the first and a verifier for the second only.
2. Copy `verifiers/_template.md` to `verifiers/<slug>.md`, named for the rule family, and fill every section. Name the rule ids it enforces, restate each rule in one line so the verifier does not need to open memory, name the approved examples under `memory/examples/` it may read, and describe what counts as a failure and what does not in observable terms.