git:20261024.28dc5ee to git:20261024.6cc488e

---

name: create-verification-skill

description: >-

Create or maintain a repository-local skill for repeatedly verifying real project

behavior through its supported browser/app, HTTP/service/API, or CLI/process

surfaces. Use when the user explicitly asks for a project verification skill,

verification capability, reusable verification journeys, or maintenance of an

existing repo-local verification skill. Do not use for ordinary test writing,

one-off app runs, or automatically scaffolding a harness because coverage is absent.

---

# Create a Project Verification Skill

Produce a reusable project-owned verification skill, not generic test advice. The result is an

actual `SKILL.md` plus only the approved helpers required to operate it. Prefer the project's

existing commands and harnesses over a new control layer.

## Workflow

### 1. Establish the owner

Inspect the repository before proposing files. Read `references/discovery-and-safety.md` and

complete its discovery pass.

Find the owning package, repository instructions, installed versions and tools, command help,

test support, existing local skills, and any established skill location. Reuse or deliberately

update an existing verification skill or harness rather than creating a parallel one.

If the repository has no established location, propose

`.agents/skills/<unique-project-verification-name>/SKILL.md`. Use a portable project-local path;

do not impose a host-specific directory.

**Complete when:** the project owner, skill owner/location, current verification assets, exact

working directories, and relevant commands are evidenced from the repository.

### 2. Define the recurring job

Name the precise job the generated skill will repeat. Select only the applicable product surfaces:

- browser or app interaction;

- HTTP, service, or API behavior;

- CLI, TUI, or process behavior.

Define named journey contracts with preconditions, public actions, observable completion, and any

Read `references/generated-skill-contract.md` before designing the artifact.

**Complete when:** every proposed journey states what real behavior it proves, at which boundary,

and what remains unsupported.

### 3. Present a bounded proposal

Before any durable write, package/config change, stateful journey, or unsafe action, show the user:

- the exact write set and owner of every artifact;

- substantive generated sections and exact repository commands;

- setup, start, doctor, actions, observations, evidence, and cleanup;

- behavior claims each journey can and cannot prove;

- any new dependency, fixture, credential mechanism, process, port, data, or external side effect;

- which actions are safe to generate versus separately gated to execute.

Ask for explicit approval of that bounded proposal. Generator invocation is permission to inspect

and propose, not blanket permission to modify the target project or drive it.

**Complete when:** the user has approved the exact durable writes and any separately scoped

execution. Stop if a required file or action lies outside that approval.

### 4. Generate the smallest durable capability

Create or update the project-local `SKILL.md` and only necessary approved helpers. Use existing

scripts, runners, fixtures, and tools where possible. Give tool-neutral roles alongside actual

commands supported by the host and repository; never invent an interface or require one browser

library everywhere.

Resolve helper paths from the generated skill directory. State the correct repository or monorepo

Use `references/examples.md` only when a concrete browser, API, CLI, or blocked-case pattern would

help shape the project-specific result.

### 5. Check the artifact

Run the repository's focused formatting, skill syntax, reference, or registration checks. Inspect

Classify the result as:

- **proposed** — described but not written;

- **generated** — written and structurally checked;

- **exercised** — run against the authorized target with the required observations;

- **blocked** — a named requirement could not be proved, with the missing capability recorded.

**Complete when:** structural checks pass or their exact failures are reported, and the status does

not overstate operational proof.

### 6. Exercise only authorized safe journeys

When the user separately approved execution, establish target identity and readiness before

If authentication, a browser, infrastructure, target identity, or another required capability is

unavailable, report **blocked**. Do not install replacements, weaken acceptance, or label the

artifact tested. Preserve sanitized evidence after cleanup.

### 7. Report

Return the generated paths, owner, journeys and supported surfaces, structural commands/results,

exercise status, evidence locations, cleanup result, omissions, source provenance, and version

uncertainty.

**Complete when:** another agent can distinguish what was proposed, generated, exercised, and

blocked without inference.

## Reference routing

| Priority | Load when | Reference |

|---|---|---|

| 1 — Required | Inspecting a target repository, choosing ownership/location, proposing writes, or preparing execution | `references/discovery-and-safety.md` |

| 1 — Required | Designing, generating, checking, or reporting the project-local verification artifact | `references/generated-skill-contract.md` |

| 2 — Conditional | A small browser, API, CLI, or safe-failure pattern would clarify the project-specific design | `references/examples.md` |

## Boundaries

`test` owns ordinary test creation, regression coverage, TDD, and executable test evidence.

Browser or runner specialists own one-off interaction and tool syntax. This skill owns the distinct

recurring job of creating or maintaining a repository-local verification skill and its approved

helpers. Missing tests alone do not trigger this skill.