# Maintain Verification Skill

Periodic pass that keeps a project's verification skill and feature map honest...

- Repository: https://github.com/nightly-labs/openbot (4509 stars)
- Category: Git and review
- License: see repository
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add nightly-labs/openbot --skill maintain-verification-skill -g -a claude-code -y`
Codex: `npx skills add nightly-labs/openbot --skill maintain-verification-skill -g -a codex -y`
Cursor: `npx skills add nightly-labs/openbot --skill maintain-verification-skill -g -a cursor -y`
Gemini CLI: `npx skills add nightly-labs/openbot --skill maintain-verification-skill -g -a gemini-cli -y`

## Description

Periodic pass that keeps a project's verification skill and feature map honest: parallel source readers per feature, one live session driving every feature, at most one PR of proven corrections. Use for /maintain-verification-skill or \"audit the verify skill\".

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

# Maintain a verification skill

A feature map rots the moment the app changes. This skill is the upkeep loop for a skill generated by `/create-verification-skill` (or any project-local verification skill with a feature map). The unit of rigor is the feature, not every sentence: cover every feature file from source and exercise every feature live, without terminalising every bullet.

## Outcomes

Pick one, and say which:

- **clean**, every feature got source and live coverage; nothing worth shipping. No branch, no PR.
- **changed**, one PR ships proven doc, harness, or map corrections.
- **blocked**, coverage could not finish or a proven fix could not ship safely. Say exactly what blocked it.

## Edit scope

Only edit the verification skill's own directory (its SKILL.md, features/, and any harness scripts it owns). Never edit product code during a run: a behavior the map describes that the app no longer does is either doc drift (fix the map) or a product regression (report it, don't paper over it in docs).

## Pass

0. **Locate the target.** Find the verification skill to maintain: the project-local skill whose body has launch/drive sections and a feature map (usually `.cursor/skills/verify-*/`). Several candidates → ask which one; none → stop and point at `/create-verification-skill` instead of inventing a target.

1. **Index hygiene.** Read the feature map README and glob its sibling files. Fix missing, extra, duplicate, or dead entries. Lightweight; no generated inventory.

2. **Source wave.** One read-only subagent per feature file, launched concurrently. Each explains "how does this user-facing feature work?" from source, flags likely doc drift with citations, and returns one concise live-verification recipe. Children never drive the app and never edit files. Return shape: feature summary / source entry points / likely drift or none / one recipe.

The rest: https://github.com/nightly-labs/openbot/blob/HEAD/marketplace/production-catalog/bundles/pstack/skills/maintain-verification-skill/SKILL.md