Token Map
nexu-io/open-design
Map an extracted Figma / source-code token bag onto the active OD design system, producing a deterministic mapping the generate stage can consume.
Audit an existing verification skill and feature map against source and the running app, then repair proven documentation or harness drift.
MITAuto-check passed
Install Maintain Verification Skill
$ npx skills add get-bb/bb --skill maintain-verification-skill -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install get-bb/bb 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/get-bb/bb.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.bb/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/get-bb/bb/tree/main/.bb/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/get-bb/bb/tree/main/.bb/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 get-bb/bb --skill maintain-verification-skill -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install get-bb/bb maintain-verification-skill --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/get-bb/bb.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.bb/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/get-bb/bb/tree/main/.bb/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 get-bb/bb --skill maintain-verification-skill -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install get-bb/bb maintain-verification-skill --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/get-bb/bb.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.bb/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/get-bb/bb/tree/main/.bb/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/get-bb/bb.git --path .bb/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 get-bb/bb --skill maintain-verification-skill -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install get-bb/bb 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/get-bb/bb.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.bb/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/get-bb/bb/tree/main/.bb/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 get-bb/bb 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 get-bb/bb --skill maintain-verification-skill -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/get-bb/bb.git skills-src && mkdir -p .github/skills && cp -r skills-src/.bb/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/get-bb/bb/tree/main/.bb/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 get-bb/bb --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 get-bb/bb maintain-verification-skill --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/get-bb/bb.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.bb/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/get-bb/bb/tree/main/.bb/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
- 4.2k
- Token cost
- ~1k tokens
- SKILL.md length
- 542 words
- Files
- 2
- Skills in repo
- 33
- Repo updated
- First seen
- Licence
- MIT
At a glance
Audit an existing verification skill and feature map against source and the running app, then repair proven documentation or harness drift.
- Maintain the verification skill
- SKILL.md covers Locate and scope, Read source, Drive the app and Reconcile, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Audit the verify skill
What it does
Maintain Verification Skill is an agent skill from get-bb/bb. Audit an existing verification skill and feature map against source and the running app, then repair proven documentation or harness drift. Use for "maintain the verification skill", "audit the verify skill", or "refresh the verification feature map".
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file.
The repository describes itself as: The agent IDE that builds itself. The licence is MIT.
When your agent uses it
- Maintain the verification skill
- Audit the verify skill
- Refresh the verification feature map
Example prompts
- “maintain the verification skill”
- “audit the verify skill”
- “refresh the verification feature map”
- “/maintain-verification-skill”
What it can do on your machine
Read from SKILL.md and the folder at commit 68a1e8b. 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
Links to these hosts (documentation or services it may open):
github.com
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
Maintain Verification Skill loads about 1k tokens when it runs. Until then it costs about 70 tokens; SKILL.md has 542 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
The full file from get-bb/bb at commit 68a1e8b, republished under its MIT licence (© get-bb). 542 words, ~1,038 tokens.
Download SKILL.mdSave it as
.claude/skills/maintain-verification-skill/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- maintain-verification-skill
- description
- Audit an existing verification skill and feature map against source and the running app, then repair proven documentation or harness drift. Use for "maintain the verification skill", "audit the verify skill", or "refresh the verification feature map".
Maintain a verification skill
Keep a repository's .bb/skills/verify-<app>/ usable by the next agent.
Locate and scope
Read repository instructions and the target verification skill. If several
apps are plausible and the request does not identify one, ask which. If none
exists, report that and point to create-verification-skill; do not invent an
audit target. A request to explain maintenance does not authorize running it.
Edit only the verification skill directory, its feature map, and its owned helpers. Report product regressions separately. Do not rewrite the expected behavior to match a broken app. Preserve only explicitly requested feature subsets and real product boundaries.
Read source
Check the index against its feature files. Read each feature's source entry points and compare its recipe with current routes, labels, CLI flags, defaults, and persistence behavior. Record a concrete source citation for each suspected drift and one concise live recipe per feature. Reconcile the feature inventory against current routes, commands, settings, plugins, platform clients, and action menus. Document omitted features even when their live prerequisites are unavailable. Preserve an explicitly requested subset, but do not infer a scope limit from gaps left by an earlier generator.
Work directly unless delegation is authorized. When source review is delegated, keep browser driving with one owner and reconcile findings before editing. Concurrent reviewers must not manipulate a shared app session.
Drive the app
Follow the skill's launch and isolation rules. Run doctor before driving and after unexpected behavior. Reset a stuck UI to a known state; do not repeatedly click into a broken session. Exercise every mapped feature through its actual user entry point, even when source review finds no drift.
Record the initial state, action, observable outcome, and relevant side effect. Use fresh isolated sessions when the launch model requires them. Preserve evidence outside disposable runtime state, including failed-attempt evidence. Clean up residue from failed attempts before proceeding.
When a prerequisite is missing, record what was attempted and the prerequisite. Source inspection is not a live pass. Do not claim whole-product coverage from a feature map that deliberately covers only a subset.
Show full SKILL.md (198 more words)Show less
Reconcile
- Wrong documentation: correct it using source and live evidence.
- Working behavior the harness cannot drive: repair the harness, then run the repaired recipe before accepting it.
- Broken product behavior: report the regression and evidence; keep the expected behavior intact.
- Missing prerequisite: mark coverage blocked and say what enables a retry.
Retry a failed setup or drive once after correcting its observed cause; stop that feature if it remains blocked and continue independent coverage.
Finish
Run final cleanup after all rechecks. Confirm owned processes and browser sessions stopped and evidence remains. Review the diff and report one outcome:
- clean: every mapped feature has source and live coverage; no corrections.
- changed: all mapped features have coverage and proven corrections are ready to commit.
- blocked: coverage or verification of a correction could not finish. Report completed coverage and any useful partial corrections explicitly.
Keep transient run details outside the repo. A checked-in validation summary, when requested, names the tested source commit and scope and excludes secrets, personal data, and machine-specific paths. Commit or publish only within the user's authorization. Do not create an automation merely because an audit ran.
Adapted from pstack.
The upstream MIT license is included in LICENSE.
© get-bb, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in .bb/skills/maintain-verification-skill of get-bb/bb.
- SKILL.md
- LICENSE
Open the folder on GitHubat commit 68a1e8b
Compare with similar skills
Maintain Verification Skill 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 |
|---|---|---|---|---|---|---|
| Maintain Verification Skill this skillget-bb/bb | 4.2k | — | ~1k | Automated safety check: Pass | MIT | |
| Token Mapnexu-io/open-design | 100k | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Maps Geographyasgeirtj/system_prompts_leaks | 69k | — | ~717 | Automated safety check: Pass | CC0-1.0 | |
| Feature Maponyx-dot-app/onyx | 32k | — | ~459 | Automated safety check: Pass | Custom licence | |
| Source Mapsthedaviddias/Front-End-Checklist | 74k | — | ~445 | Automated safety check: Pass | MIT | |
| Open Source Maintainer Assistantslopus/happy | 24k | — | ~1.9k | Automated safety check: Pass | MIT |
Similar skills
Maps Geography
asgeirtj/system_prompts_leaks
Accurate maps from real geo data — use for any map, or whenever geography would make a good graphic for a deliverable
Feature Map
onyx-dot-app/onyx
Use the Onyx feature map (.agents/feature-map/) to learn what a product surface does, the code behind it, and what a change can break.
Source Maps
thedaviddias/Front-End-Checklist
A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Provide source maps for production debugging.
Open Source Maintainer Assistant
slopus/happy
Helps maintain the slopus/happy open source project by triaging issues, drafting closing comments, finding duplicates and checking fixes, with approval before anything is posted.
Customer Journey Map
phuryn/pm-skills
Create an end-to-end customer journey map with stages, touchpoints, emotions, pain points, and opportunities.
More from get-bb/bb
All 33 skills in this repoBb CLI
get-bb/bb
Inspect or manage BB state with the bb CLI; use for BB commands and configuration.
Skill Creator
get-bb/bb
Create or improve BB skills, including their triggers, instructions, and supporting resources.
Submit A Plugin
get-bb/bb
Prepare and submit a BB plugin to the Community marketplace when publication or a marketplace PR is requested.
Workflows
get-bb/bb
Author or run durable BB workflows when the user requests workflow execution or multi-agent orchestration.
Verify Bb
get-bb/bb
Verify BB user journeys in an isolated source dev app using dev-browser@next and the matching source CLI.
Bb Theme Authoring
get-bb/bb
Create or edit BB color themes and inspect them in the Theme Preview panel.
Questions about Maintain Verification Skill
What does Maintain Verification Skill do?
Audit an existing verification skill and feature map against source and the running app, then repair proven documentation or harness drift. Maintain Verification Skill is an agent skill from get-bb/bb. Audit an existing verification skill and feature map against source and the running app, then repair proven documentation or harness drift.
When should I use Maintain Verification Skill?
Maintain Verification Skill fits situations like: maintain the verification skill; audit the verify skill; refresh the verification feature map.
How do I install Maintain Verification Skill in Claude Code?
Run `npx skills add get-bb/bb --skill maintain-verification-skill -a claude-code`. Or copy the skill folder (.bb/skills/maintain-verification-skill in get-bb/bb) into .claude/skills/maintain-verification-skill in your project. Claude Code loads it when a task matches its description.
How do I install Maintain Verification Skill in Codex?
Run `npx skills add get-bb/bb --skill maintain-verification-skill -a codex`. Or copy the skill folder (.bb/skills/maintain-verification-skill in get-bb/bb) into .agents/skills/maintain-verification-skill in your project. Codex loads it when a task matches its description.
Can I use Maintain Verification Skill 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 get-bb/bb --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 Maintain Verification Skill need to run?
SKILL.md names no scripts, command-line tools or credentials: Maintain Verification Skill is instructions for the agent only.
Does Maintain Verification Skill access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Maintain Verification Skill 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 Maintain Verification Skill use?
Maintain Verification Skill is published under the MIT licence (from the LICENSE file in the skill folder). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Maintain Verification Skill use?
About 1k tokens (SKILL.md is roughly 4.2k 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 Maintain Verification Skill?
Skills that share tags, products or a category with Maintain Verification Skill: Token Map (nexu-io/open-design, 100k stars), Maps Geography (asgeirtj/system_prompts_leaks, 69k stars), Feature Map (onyx-dot-app/onyx, 32k stars) and Source Maps (thedaviddias/Front-End-Checklist, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Maintain Verification Skill?
get-bb (a GitHub organization) maintains it in get-bb/bb, which has 4,155 GitHub stars. The repository holds 33 skills in this directory. The repository was last updated on October 7, 2026.
Source: get-bb/bb on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.