New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Verify

by andymai in andymai/brepjs

A skill your agent uses when running brep on a .brep.ts part and interpreting the result — reading the JSON report (ok / checks / assertions / hints), verifying visually from snapshots, driving…

Apache-2.0Auto-check passedDevelopment

Install Verify

skills CLI
$ npx skills add andymai/brepjs --skill verify -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install andymai/brepjs verify --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/andymai/brepjs.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/brepjs-cad/skills/verify .claude/skills/verify && rm -rf skills-src

Use ~/.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/

Facts

Skill name
verify
GitHub stars
114
Token cost
~1.1k tokens
SKILL.md length
475 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when running brep on a .brep.ts part and interpreting the result — reading the JSON report (ok / checks / assertions / hints), verifying visually from snapshots, driving…

  • Running brep on a .brep.ts part and interpreting the result — reading the JSON report (ok / checks / assertions / hints)
  • SKILL.md covers Verify (type + geometry), Reading the report, Verify visually and Repair discipline, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
  • Verifying visually from snapshots

What it does

Verify is an agent skill from andymai/brepjs. Use when running brep on a .brep.ts part and interpreting the result — reading the JSON report (ok / checks / assertions / hints), verifying visually from snapshots, driving repair of the smallest responsible section, and using the brep CLI subcommands. This is the checking step that decides whether a part is done.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Development. The repository describes itself as: Web CAD library with exact B-Rep geometry. The licence is Apache-2.0.

When your agent uses it

  • Running brep on a .brep.ts part and interpreting the result — reading the JSON report (ok / checks / assertions / hints)
  • Verifying visually from snapshots
  • Driving repair of the smallest responsible section
  • Using the brep CLI subcommands

Example prompts

  • “/verify”

What it can do on your machine

Read from SKILL.md and the folder at commit ee50994. 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 (its code samples are jsonc).

    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

Verify loads about 1.1k tokens when it runs. Until then it costs about 81 tokens; SKILL.md has 475 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~81
When it runs · the whole SKILL.md, loaded when a task matches
~1.1k

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 andymai/brepjs at commit ee50994, republished under its Apache-2.0 licence (© andymai). 475 words, ~1,090 tokens.

Download SKILL.mdSave it as .claude/skills/verify/SKILL.md (or your agent's skills folder).
name
verify
description
Use when running brep on a `.brep.ts` part and interpreting the result — reading the JSON report (ok / checks / assertions / hints), verifying visually from snapshots, driving repair of the smallest responsible section, and using the brep CLI subcommands. This is the checking step that decides whether a part is done.
version
0.1.0

Verify a brepjs part

Run the part on the kernel and judge it by the report, not by how the code reads. The CLI ships in the brepjs-cad package as brep.

Verify (type + geometry)

brep verify part.brep.ts --check --json report.json

--check type-checks before running (catches wrong-API calls early); the JSON report is the source of truth. Iterate fast with brep watch part.brep.ts.

Reading the report

jsonc
{
  "ok": false,                       // true only if valid AND every assertion passes
  "shapeType": "Solid",
  "checks": [{ "name": "isValidSolid", "passed": false }],
  "measurements": { "volume": …, "area": …, "bounds": {…} },
  "assertions": [{ "name": "volume", "expected": 24000, "actual": 31200, "passed": false }],
  "hints":  [{ "code": "FILLET_NO_EDGES", "fix": "…", "nextStep": "…" }],
  "errorInfos": [{ "code": "…", "message": "…" }]
}
  • ok is the verdict. false → not done. With an expected block, ok also requires every assertion to pass.
  • checks = kernel validity (manifold solid, positive volume). A failed check means the geometry is broken, not just wrong-sized.
  • shapeType: 'Compound' is normal for a single body. A cut, a fillet, or a chain of cuts often reports the result as Compound even though it's one watertight solid — fine as long as ok:true and the validity checks pass. Only a loose Compound from a failed fuse of merely-touching solids is a problem (../implement/references/booleans.md). Don't retry a valid part just because it isn't labelled Solid.
  • assertions = declared intent vs reality. A failed assertion means valid-but-wrong.
  • hints = actionable fix + next step keyed on the error code. Read these before guessing.
  • errorInfos = raw structured failures (code + message) the hints derive from. Cite the code when repairing.
  • Trust this JSON over the rendered image. The render confirms shape; the JSON confirms correctness.

Verify visually

Add --snapshot shots/ for iso/front/top/right PNGs; each has the bbox size (W × D × H) burned in, so you can read scale from the image. Review against the brief. A visual concern is not a conclusion: convert a dimensional one to a measurement ("hole looks off-center → check bounds"); a design-quality one ("looks lumpy / glued-from-primitives") goes to brepjs:polish. Don't declare done without a snapshot.

Show full SKILL.md (197 more words)Show less

Repair discipline

  • Change the smallest responsible section, re-verify, repeat. Don't rewrite the whole part on one failure.
  • Let the code/hints localize the cause (INVALID_FILLET_RADIUS → reduce radius vs local edge length; *_NOT_3D → you passed a 2D shape to a 3D op; BOOLEAN_HAS_ERRORS → inputs overlap-degenerate).
  • A part that runs but reports ok:false is wrong, not done. Treat it like a crash.

Asserting expected codes (for fixtures / eval)

brep verify part.brep.ts --expect-code <CODE> exits 0 only if the report emits <CODE>; --expect-invalid exits 0 only if ok:false. Use these to assert that a known-bad part fails the right way.

CLI subcommands (the brep bin)

  • verify <files...> (default): report; flags --check, --json [path|-], --step, --glb, --snapshot <dir>, --serve, --no-open, --expect-code <CODE>, --expect-invalid. One file → the full report (all flags). Multiple files or a quoted glob (brep verify "parts/*.brep.ts") → a validity-only JSON array, exit 1 if any part is invalid (single-file artifact flags are ignored).
  • snapshot <file> [--label <tag>]: render iso/front/top/right PNGs without re-verifying.
  • init <name>: scaffold <name>.brep.ts + tsconfig.json.
  • watch <file>: re-verify on every save.
  • export <file>: batch STEP/GLB/STL behind a validity gate (--step/--glb/--stl/--all).
  • measure <a> [b]: measurements for one part, or distance between two.
  • diff <a> <b>: compare two parts' measurements.

© andymai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in packages/brepjs-cad/skills/verify of andymai/brepjs.

Open the folder on GitHubat commit ee50994

Compare with similar skills

Verify 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.

Verify compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Verify this skillandymai/brepjs114—~1.1kAutomated safety check: PassApache-2.0
Vercel Composition Patternssupabase/supabase111k59 repos~726Automated safety check: PassMIT
Finishing a Development Branchobra/superpowers296k5 repos~1.9kAutomated safety check: PassMIT
Typescript Advanced Typesrolling-scopes/rsschool-app10k25 repos~4.2kAutomated safety check: PassMPL-2.0
PR Babysitteropeninterpreter/openinterpreter69k3 repos~4.2kAutomated safety check: PassApache-2.0
Code Review ChecklistshareAI-lab/learn-claude-code78k5 repos~1.1kAutomated safety check: PassMIT

Similar skills

  • Vercel Composition Patterns

    supabase/supabase

    Official

    React composition patterns that scale. An agent skill from supabase/supabase.

    111k GitHub starsUsed in 59 repos~726 tokens
    DevelopmentAuto-check passed

  • Finishing a Development Branch

    obra/superpowers

    Walks the last step of a branch: confirm tests pass, detect the git environment, ask how to integrate, carry out your choice and clean up the worktree.

    296k GitHub starsUsed in 5 repos~1.9k tokens
    DevelopmentAuto-check passed

  • Typescript Advanced Types

    rolling-scopes/rsschool-app

    Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications.

    10k GitHub starsUsed in 25 repos~4.2k tokens
    DevelopmentAuto-check passed

  • PR Babysitter

    openinterpreter/openinterpreter

    Watches an open GitHub pull request until it merges, handling review comments, diagnosing CI failures and retrying flaky checks along the way.

    69k GitHub starsUsed in 3 repos~4.2k tokens
    DevelopmentAuto-check passed

  • Code Review Checklist

    shareAI-lab/learn-claude-code

    Reviews code against a five-part checklist covering security, correctness, performance, maintainability and testing, and reports findings in a fixed format.

    78k GitHub starsUsed in 5 repos~1.1k tokens
    DevelopmentAuto-check passed

  • Greploop

    onyx-dot-app/onyx

    Iteratively improves a PR (GitHub), MR (GitLab), or shelved changelist (Perforce) until Greptile gives it a 5/5 confidence score with zero unresolved comments.

    32k GitHub starsUsed in 4 repos~3.3k tokens
    DevelopmentAuto-check passed

More from andymai/brepjs

All 21 skills in this repo

  • Implement

    andymai/brepjs

    A skill your agent uses when authoring or editing a brepjs .brep.ts part — writing the geometry with the functional API (box, cylinder, fuse, cut, fillet, sketch→extrude…), declaring an expected…

    114 GitHub stars~3.4k tokensUpdated today
    Auto-check passed

  • Memory And Disposal

    andymai/brepjs

    This skill should be used when managing WASM handle lifetimes or hunting memory leaks in brepjs — when a task mentions "createHandle() without using keyword risks WASM memory leak"…

    114 GitHub stars~3.1k tokensUpdated today
    Auto-check passed

  • Polish

    andymai/brepjs

    A skill your agent uses when a valid brepjs part should look designed rather than glued-from-primitives (products, toys, mechanisms, anything a human eyeballs), and when exporting/handing off the…

    114 GitHub stars~588 tokensUpdated today
    Auto-check passed

  • Wasm Interop

    andymai/brepjs

    This skill should be used when working across the JS/WASM boundary in brepjs — writing or debugging code in src/kernel/occt, src/kernel/occtWasm, or src/kernel/brepkit, or diagnosing symptoms like…

    114 GitHub stars~3k tokensUpdated today
    Auto-check passed

  • Writing Tests

    andymai/brepjs

    This skill should be used when writing, running, or fixing tests in the brepjs repository — when a task says "add a test", "write a regression test", "tests are failing", "test timed out", "coverage…

    114 GitHub stars~4.3k tokensUpdated today
    Auto-check passed

  • Adding Operations

    andymai/brepjs

    This skill should be used when adding or extending a geometric shape operation in brepjs — the end-to-end recipe once the target module is chosen (which is decided by architecture-navigation) — when…

    114 GitHub stars~4.4k tokensUpdated today
    Auto-check passed

Categories

Questions about Verify

What does Verify do?

A skill your agent uses when running brep on a .brep.ts part and interpreting the result — reading the JSON report (ok / checks / assertions / hints), verifying visually from snapshots, driving…. Verify is an agent skill from andymai/brepjs.ts part and interpreting the result — reading the JSON report (ok / checks / assertions / hints), verifying visually from snapshots, driving repair of the smallest responsible section, and using the brep CLI subcommands.

When should I use Verify?

Verify fits situations like: running brep on a .brep.ts part and interpreting the result — reading the JSON report (ok / checks / assertions / hints); verifying visually from snapshots; driving repair of the smallest responsible section; using the brep CLI subcommands.

How do I install Verify in Claude Code?

Run `npx skills add andymai/brepjs --skill verify -a claude-code`. Or copy the skill folder (packages/brepjs-cad/skills/verify in andymai/brepjs) into .claude/skills/verify in your project. Claude Code loads it when a task matches its description.

How do I install Verify in Codex?

Run `npx skills add andymai/brepjs --skill verify -a codex`. Or copy the skill folder (packages/brepjs-cad/skills/verify in andymai/brepjs) into .agents/skills/verify in your project. Codex loads it when a task matches its description.

Can I use Verify 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 andymai/brepjs --skill verify -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/verify, .gemini/skills/verify, .github/skills/verify and .opencode/skills/verify in your project.

What does Verify need to run?

SKILL.md names no scripts, command-line tools or credentials: Verify is instructions for the agent only.

Does Verify 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 Verify 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 Verify use?

Verify is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Verify use?

About 1.1k tokens (SKILL.md is roughly 4.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 Verify?

Skills that share tags, products or a category with Verify: Vercel Composition Patterns (supabase/supabase, 111k stars), Finishing a Development Branch (obra/superpowers, 296k stars), Typescript Advanced Types (rolling-scopes/rsschool-app, 10k stars) and PR Babysitter (openinterpreter/openinterpreter, 69k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Verify?

andymai (a GitHub user) maintains it in andymai/brepjs, which has 114 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 8, 2026.

Source: andymai/brepjs on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.