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.
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API.
MITAuto-check passed
Install Create Verification Skill
$ npx skills add get-bb/bb --skill create-verification-skill -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install get-bb/bb create-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/create-verification-skill .claude/skills/create-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 "create-verification-skill" agent skill from https://github.com/get-bb/bb/tree/main/.bb/skills/create-verification-skill into .claude/skills/create-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-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/create-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 create-verification-skill -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install get-bb/bb create-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/create-verification-skill .agents/skills/create-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 "create-verification-skill" agent skill from https://github.com/get-bb/bb/tree/main/.bb/skills/create-verification-skill into .agents/skills/create-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-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 create-verification-skill -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install get-bb/bb create-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/create-verification-skill .cursor/skills/create-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 "create-verification-skill" agent skill from https://github.com/get-bb/bb/tree/main/.bb/skills/create-verification-skill into .cursor/skills/create-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-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/create-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 create-verification-skill -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install get-bb/bb create-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/create-verification-skill .gemini/skills/create-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 "create-verification-skill" agent skill from https://github.com/get-bb/bb/tree/main/.bb/skills/create-verification-skill into .gemini/skills/create-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-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 create-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 create-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/create-verification-skill .github/skills/create-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 "create-verification-skill" agent skill from https://github.com/get-bb/bb/tree/main/.bb/skills/create-verification-skill into .github/skills/create-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-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 create-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 create-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/create-verification-skill .opencode/skills/create-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 "create-verification-skill" agent skill from https://github.com/get-bb/bb/tree/main/.bb/skills/create-verification-skill into .opencode/skills/create-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-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
create-verification-skill- GitHub stars
- 4.2k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 707 words
- Files
- 2
- Skills in repo
- 34
- Repo updated
- First seen
- Licence
- MIT
At a glance
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API.
- Create a verification skill
- SKILL.md covers Discover, Generate, Prove and Finish
- Calls npm
- Make a verify skill for this repo
What it does
Create Verification Skill is an agent skill from get-bb/bb. Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
Its SKILL.md is about 1.4k 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
- Create a verification skill
- Make a verify skill for this repo
- Document how agents can verify this app
Example prompts
- “create a verification skill”
- “make a verify skill for this repo”
- “document how agents can verify this app”
- “/create-verification-skill”
Requirements
- Node.js
What it can do on your machine
Read from SKILL.md and the folder at commit 53c1e87. 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
Shell commands in SKILL.md call:
npm
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
Create Verification Skill loads about 1.4k tokens when it runs. Until then it costs about 66 tokens; SKILL.md has 707 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 53c1e87, republished under its MIT licence (© get-bb). 707 words, ~1,355 tokens.
Download SKILL.mdSave it as
.claude/skills/create-verification-skill/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- create-verification-skill
- description
- Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
Create a verification skill
Generate .bb/skills/verify-<app>/SKILL.md for an agent arriving cold in the
repository. Adapt the recipe to the actual app and prove it by running it.
Discover
Read repository instructions, startup scripts, routes, existing tests, and QA
docs. Establish the user surfaces, launch command, readiness signal, required
runtime, authentication, fixtures, automation harness, and observable side
effects. Prefer the repository's harness. For browser interaction without an
existing project harness, use dev-browser@next. Install it with
npm install -g dev-browser@next, then read dev-browser --help. It provides
Puppeteer scripts, named pages, page.snapshot(), and snapshot-ref selectors.
If it reports missing Chrome, run dev-browser install. Record the installed
version with the evidence; the next tag can change.
Inspect an existing verification skill before creating another. Extend it when it already owns the same app. Ask only for decisions the repository cannot answer. Do not execute this workflow for a request that only asks what a skill does or asks to verify one existing feature.
Establish isolation before launch: ports, database, host connections, browser profile, and process ownership. Use synthetic data. Do not copy a live store or reuse the user's logged-in app. Respect project rules for imported data and network-facing plugins. A new data-directory name alone does not prove that a launcher will not import existing data.
Check the real startup path. Resolve routine local setup failures within the task's scope. Report product defects and unavailable prerequisites precisely; do not change product behavior merely to make verification pass.
Generate
Write the skill with valid BB frontmatter and these sections:
- Launch: exact commands, runtime, readiness check, target discovery, and isolation. Derive ports and IDs from real output instead of guessed values.
- Doctor: a read-only check of instance identity, process ownership, build/source revision, API health, and any feature-specific prerequisite.
- Drive: documented harness commands and stable selectors from the real app. Include how CLI/API calls target the same instance as the browser.
- Evidence: capture the starting state, user action, resulting state, and relevant persisted side effect. Record the source commit, environment, command, and result. Keep evidence outside disposable runtime state.
- Cleanup: stop only processes and browser sessions this run owns. Verify they stopped and evidence survives. Handle failed attempts too.
Create an exhaustive feature inventory by default. Reconcile UI routes, navigation and action menus, CLI commands, settings, installed or bundled plugins, platform clients, and public agent interfaces. Group related features into files, but give each distinct capability its own driving recipe and observable success condition. Do not use a fixed feature count or treat the easiest working paths as the product's boundary. A starter subset is appropriate only when the user explicitly requests one.
Show full SKILL.md (271 more words)Show less
Write features/README.md as the index. Each feature file includes the user
goal, source entry points, prerequisites, how to reach it, driving recipes,
observable success, and gotchas. Include unavailable and platform-specific
features with their prerequisites; inability to run them does not justify
omitting their documentation. Explicitly classify compatibility aliases,
developer-only surfaces, and out-of-repository extensions.
Cross-check the map against a reproducible source inventory. Track newly added routes, commands, settings, and plugins so later audits expose missing coverage. Source coverage is not proof of behavior; keep inventory completeness separate from live verification status.
Any helper must be executable, documented, and tested. Avoid adding a wrapper when an existing command already does the job. Never commit credentials, personal data, machine-specific runtime state, or raw unreviewed transcripts.
Prove
Read and follow the generated instructions: launch, doctor, drive at least one mapped feature through its real entry point, capture evidence, and clean up. Use UI input for UI claims; API setup or database inspection can supplement it, but internal setters and mocked routes cannot prove the user journey.
Record each feature as live-verified, source-only, or blocked, with the reason and evidence. A browser check in Chromium does not verify Safari or a native app. Fix recipe errors and retry within a bounded scope. Confirm evidence still exists after cleanup. An unexecuted skill is a draft.
Finish
Report the generated skill, live coverage, limitations, and evidence location.
Point to maintain-verification-skill for upkeep; do not schedule it implicitly.
Commit the generated files when requested. Push, publish, or open a PR only
when the user's request authorizes that action.
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/create-verification-skill of get-bb/bb.
- SKILL.md
- LICENSE
Open the folder on GitHubat commit 53c1e87
Compare with similar skills
Create 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 |
|---|---|---|---|---|---|---|
| Create Verification Skill this skillget-bb/bb | 4.2k | — | ~1.4k | 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 | |
| Feishu Driveopenclaw/openclaw | 392k | — | ~375 | 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.
Feishu Drive
openclaw/openclaw
Feishu cloud-storage and comment workflows. An agent skill from openclaw/openclaw.
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 34 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 Create Verification Skill
What does Create Verification Skill do?
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Create Verification Skill is an agent skill from get-bb/bb. Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API.
When should I use Create Verification Skill?
Create Verification Skill fits situations like: create a verification skill; make a verify skill for this repo; document how agents can verify this app.
How do I install Create Verification Skill in Claude Code?
Run `npx skills add get-bb/bb --skill create-verification-skill -a claude-code`. Or copy the skill folder (.bb/skills/create-verification-skill in get-bb/bb) into .claude/skills/create-verification-skill in your project. Claude Code loads it when a task matches its description.
How do I install Create Verification Skill in Codex?
Run `npx skills add get-bb/bb --skill create-verification-skill -a codex`. Or copy the skill folder (.bb/skills/create-verification-skill in get-bb/bb) into .agents/skills/create-verification-skill in your project. Codex loads it when a task matches its description.
Can I use Create 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 create-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/create-verification-skill, .gemini/skills/create-verification-skill, .github/skills/create-verification-skill and .opencode/skills/create-verification-skill in your project.
What does Create Verification Skill need to run?
Going by SKILL.md and its folder, Create Verification Skill needs the command-line tools its instructions call (npm). Our summary lists: Node.js.
Does Create 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 Create 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 Create Verification Skill use?
Create 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 Create Verification Skill use?
About 1.4k tokens (SKILL.md is roughly 5.4k 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 Create Verification Skill?
Skills that share tags, products or a category with Create 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 Create Verification Skill?
get-bb (a GitHub organization) maintains it in get-bb/bb, which has 4,166 GitHub stars. The repository holds 34 skills in this directory. The repository was last updated on October 8, 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.