Loop Change Verifier
cobusgreyling/loop-engineering
Acts as a skeptical checker for changes an implementer sub-agent made, running the tests, confirming the diff scope and returning approve, reject or escalate to a human.
Audits a project's verification skill and its feature map against the source and the live app, then ships at most one pull request of proven corrections.
Install Verification Skill Maintenance
$ npx skills add cursor/plugins --skill maintain-verification-skill -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install cursor/plugins maintain-verification-skill --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/pstack/skills/maintain-verification-skill .claude/skills/maintain-verification-skill && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "maintain-verification-skill" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/maintain-verification-skill into .claude/skills/maintain-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-verification-skill", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/cursor/plugins/tree/main/pstack/skills/maintain-verification-skillType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add cursor/plugins --skill maintain-verification-skill -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install cursor/plugins maintain-verification-skill --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/pstack/skills/maintain-verification-skill .agents/skills/maintain-verification-skill && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "maintain-verification-skill" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/maintain-verification-skill into .agents/skills/maintain-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-verification-skill", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cursor/plugins --skill maintain-verification-skill -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install cursor/plugins maintain-verification-skill --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/pstack/skills/maintain-verification-skill .cursor/skills/maintain-verification-skill && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "maintain-verification-skill" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/maintain-verification-skill into .cursor/skills/maintain-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-verification-skill", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/cursor/plugins.git --path pstack/skills/maintain-verification-skill--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add cursor/plugins --skill maintain-verification-skill -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install cursor/plugins maintain-verification-skill --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/pstack/skills/maintain-verification-skill .gemini/skills/maintain-verification-skill && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "maintain-verification-skill" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/maintain-verification-skill into .gemini/skills/maintain-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-verification-skill", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install cursor/plugins maintain-verification-skillInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add cursor/plugins --skill maintain-verification-skill -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/pstack/skills/maintain-verification-skill .github/skills/maintain-verification-skill && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "maintain-verification-skill" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/maintain-verification-skill into .github/skills/maintain-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-verification-skill", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add cursor/plugins --skill maintain-verification-skill -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install cursor/plugins maintain-verification-skill --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/cursor/plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/pstack/skills/maintain-verification-skill .opencode/skills/maintain-verification-skill && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "maintain-verification-skill" agent skill from https://github.com/cursor/plugins/tree/main/pstack/skills/maintain-verification-skill into .opencode/skills/maintain-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "maintain-verification-skill", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
maintain-verification-skill- GitHub stars
- 10k
- Used in
- 8 other repos
- Token cost
- ~1.2k tokens
- SKILL.md length
- 694 words
- Files
- 1
- Skills in repo
- 99
- Repo updated
- First seen
- Licence
- None found
At a glance
Audits a project's verification skill and its feature map against the source and the live app, then ships at most one pull request of proven corrections.
- Works in 7 steps: Locate the target. Find the verification… → Index hygiene. Read the feature map… → Source wave. One read-only subagent per… → …
- A project's verification skill or feature map may have drifted from the app
- SKILL.md covers Outcomes, Edit scope and Pass
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
A feature map goes stale as soon as the app changes, so this skill is the upkeep loop for a skill made by `/create-verification-skill`, or any project-local verification skill with a feature map. The agent locates that skill, usually under `.cursor/skills/verify-*/`, asks which one if several exist, and stops with a pointer to the creation skill if there is none. It cleans the feature index of missing, extra, duplicate or dead entries.
A source wave follows, with one read-only subagent per feature file running concurrently. Each explains how its feature works from source, flags likely documentation drift with citations and returns one recipe for live checking, and none of them drives the app or edits files. The parent reconciles recipes into as few app states as practical and looks for user-facing surfaces missing from the map. Edits stay inside the verification skill's own folder, and a behavior the app has truly lost is reported as a regression. The run ends as clean, changed or blocked.
When your agent uses it
- A project's verification skill or feature map may have drifted from the app
- Running a periodic audit of the verify skill with live coverage of every feature
- Finding user-facing features that the feature map does not mention
Example prompts
- “Audit the verify skill and open one PR if any corrections are proven.”
- “Run /maintain-verification-skill and tell me whether the result is clean, changed or blocked.”
- “Check whether our checkout and search features in the feature map still match the app.”
Requirements
- A project-local verification skill with a feature map
- A way to launch and drive the app live
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Locate the target. Find the verification skill to maintain: the project-local skill whose body has launch/drive sections and a feature map…
- Index hygiene. Read the feature map README and glob its sibling files. Fix missing, extra, duplicate, or dead entries. Lightweight; no…
- Source wave. One read-only subagent per feature file, launched concurrently. Each explains "how does this user-facing feature work?" from…
- Reconcile. Every feature file has a returned summary. Merge overlapping recipes into as few app states as practical. Spot-check cited…
- Live pass. Required even when source looks clean. The coordinator owns all driving; follow the verification skill's own launch model — one…
- Triage. Wrong or missing user-POV description → doc drift, fix it. Working behavior the harness can't drive → harness gap, fix it; a…
- Ship or stop. For changed: one PR of proven corrections, re-read every changed file first. For clean or blocked: no PR, report the outcome…
What it can do on your machine
Read from SKILL.md and the folder at commit 9f451cf. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Verification Skill Maintenance loads about 1.2k tokens when it runs. Until then it costs about 72 tokens; SKILL.md has 694 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
Without a licence we can't republish the file, so here is its outline and opening line. It has 694 words (~1,223 tokens).
“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…”
- name
- maintain-verification-skill
- disable-model-invocation
- true
Files
Just SKILL.md in pstack/skills/maintain-verification-skill of cursor/plugins.
Open the folder on GitHubat commit 9f451cf
Used in 8 other repositories
We found 8 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 8 other GitHub owners. This page covers the copy in cursor/plugins, which our catalogue first saw on October 7, 2026.
- chmonitor/chmonitor.claude/skills/pstack/upstream/skills/maintain-verification-skill
- Dimon94/skillsskills/maintain-verification-skill
- michael-denyer/pstack-claudeplugins/pstack/skills/maintain-verification-skill
- backnotprop/pstackskills/maintain-verification-skill
- tellahq/opensession.agents/skills/pstack-suite/skills/maintain-verification-skill
- am-will/gooey-pi.agents/skills/pstack/maintain-verification-skill
- jtaroreh/agystackskills/maintain-verification-skill
- uzairansaruzi/p3-stackskills/maintain-verification-skill
Compare with similar skills
Verification Skill Maintenance next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Verification Skill Maintenance this skillcursor/plugins | 10k | 8 repos | ~1.2k | Automated safety check: Pass | None | |
| Loop Change Verifiercobusgreyling/loop-engineering | 11k | 1 repos | ~383 | Automated safety check: Pass | MIT | |
| Iteration Progress Auditprime-radiant-inc/iterative-development | 181 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| OMA Multi-Agent Orchestrationfirst-fluke/oh-my-agent | 1.3k | — | ~4.1k | Automated safety check: Pass | MIT | |
| Cline Pilotsickn33/agentic-awesome-skills | 47k | 1 repos | ~4.6k | Automated safety check: Pass | MIT | |
| DeepSeek V4 Thinking-Mode Rulescodewhale-hq/Codewhale | 41k | — | ~443 | Automated safety check: Pass | MIT |
Similar skills
Iteration Progress Audit
prime-radiant-inc/iterative-development
Checks the quality of behavior evidence after each iteration in three tiers, using two auditor subagents in parallel to review the same work and find gaps.
OMA Multi-Agent Orchestration
first-fluke/oh-my-agent
Decomposes a complex feature into tasks, dispatches parallel specialist agents with durable state, and supervises verification, QA review and retries.
Cline Pilot
sickn33/agentic-awesome-skills
Acts as a proxy for the Cline CLI, dispatching coding tasks one at a time, monitoring runs by hard evidence, relaying decisions to you and learning per-project preferences.
DeepSeek V4 Thinking-Mode Rules
codewhale-hq/Codewhale
Three rules for multi-step work with DeepSeek V4 thinking models: verify references, use a verifier subagent before big edits, and write plans with exact path and line.
Phased Plan Executor
thedotmack/claude-mem
Executes a phased implementation plan by acting as an orchestrator that hands each step to subagents, verifies the results and commits only after verification passes.
More from cursor/plugins
All 99 skills in this repo- Official
Show Me Your Work Decision Log
cursor/plugins
Keeps a TSV decision log for long or unattended agent runs, one row per decision with what, why, evidence and result, so a reviewer can check the work later.
- Official
Code Design Rationale Investigator
cursor/plugins
Digs into why code is shaped the way it is by checking git history, pull requests and connected tools in parallel, then reporting a cited read on the tradeoffs.
- Official
Reflect on Session Learnings
cursor/plugins
Starts three parallel reviewer subagents over the current conversation transcript, then turns their findings into concrete edits to existing skills.
- Official
Technical Writing Standard
cursor/plugins
Applies four layers of technical-writing rules to docs, RFCs, readmes, PR descriptions and commit messages so a tired engineer follows them on the first read.
- Official
Advisor Mode
cursor/plugins
Adds a second, stronger model that the main agent consults before major decisions, when stuck and before finishing, controlled by /advisor commands.
- Official
Make PR Easy To Review
cursor/plugins
Prepare PRs for review by cleaning noisy history, improving PR descriptions, and adding reviewer guidance without changing code behavior.
Related
Categories
Questions about Verification Skill Maintenance
What does Verification Skill Maintenance do?
Audits a project's verification skill and its feature map against the source and the live app, then ships at most one pull request of proven corrections. A feature map goes stale as soon as the app changes, so this skill is the upkeep loop for a skill made by `/create-verification-skill`, or any project-local verification skill with a feature map.cursor/skills/verify-*/`, asks which one if several exist, and stops with a pointer to the creation skill if there is none.
When should I use Verification Skill Maintenance?
Verification Skill Maintenance fits situations like: A project's verification skill or feature map may have drifted from the app; running a periodic audit of the verify skill with live coverage of every feature; finding user-facing features that the feature map does not mention.
How do I install Verification Skill Maintenance in Claude Code?
Run `npx skills add cursor/plugins --skill maintain-verification-skill -a claude-code`. Or copy the skill folder (pstack/skills/maintain-verification-skill in cursor/plugins) into .claude/skills/maintain-verification-skill in your project. Claude Code loads it when a task matches its description.
How do I install Verification Skill Maintenance in Codex?
Run `npx skills add cursor/plugins --skill maintain-verification-skill -a codex`. Or copy the skill folder (pstack/skills/maintain-verification-skill in cursor/plugins) into .agents/skills/maintain-verification-skill in your project. Codex loads it when a task matches its description.
Can I use Verification Skill Maintenance in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add cursor/plugins --skill maintain-verification-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/maintain-verification-skill, .gemini/skills/maintain-verification-skill, .github/skills/maintain-verification-skill and .opencode/skills/maintain-verification-skill in your project.
What does Verification Skill Maintenance need to run?
SKILL.md names no scripts, command-line tools or credentials: Verification Skill Maintenance is instructions for the agent only. Our summary lists: A project-local verification skill with a feature map; A way to launch and drive the app live.
Does Verification Skill Maintenance access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Verification Skill Maintenance safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Verification Skill Maintenance use?
No licence was found for Verification Skill Maintenance or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.
How many tokens does Verification Skill Maintenance use?
About 1.2k tokens (SKILL.md is roughly 4.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Verification Skill Maintenance?
Skills that share tags, products or a category with Verification Skill Maintenance: Loop Change Verifier (cobusgreyling/loop-engineering, 11k stars), Iteration Progress Audit (prime-radiant-inc/iterative-development, 181 stars), OMA Multi-Agent Orchestration (first-fluke/oh-my-agent, 1.3k stars) and Cline Pilot (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Verification Skill Maintenance?
cursor (a GitHub organization, an official publisher) maintains it in cursor/plugins, which has 10,130 GitHub stars. The repository holds 99 skills in this directory. The repository was last updated on October 6, 2026.
Source: cursor/plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.