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

Forgecad Inspect Model

by ForgeCAD in ForgeCAD/forgecad-public-kit

Select, run, and interpret ForgeCAD inspection evidence for collisions, sections, wall thickness, components, masks, depth, normals, surface continuity, and fit.

MITAuto-check passedDevelopment

Install Forgecad Inspect Model

skills CLI
$ npx skills add ForgeCAD/forgecad-public-kit --skill forgecad-inspect-model -a claude-code

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

GitHub CLI
$ gh skill install ForgeCAD/forgecad-public-kit forgecad-inspect-model --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/ForgeCAD/forgecad-public-kit.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/forgecad-inspect-model .claude/skills/forgecad-inspect-model && 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
forgecad-inspect-model
GitHub stars
941
Token cost
~1.3k tokens
SKILL.md length
565 words
Files
2
Skills in repo
10
Repo updated
First seen
Licence
MIT

At a glance

Select, run, and interpret ForgeCAD inspection evidence for collisions, sections, wall thickness, components, masks, depth, normals, surface continuity, and fit.

  • Works in 8 steps: Identify the failure question. What… → Confirm the model executes. If in doubt,… → Pick ONE targeted evidence command from… → …
  • Development work in your project
  • SKILL.md covers Workflow, Evidence Selection, Section Probe + Replay and Misread Traps, plus 1 more section
  • Runs Python scripts from its folder; calls python

What it does

Forgecad Inspect Model is an agent skill from ForgeCAD/forgecad-public-kit. Select, run, and interpret ForgeCAD inspection evidence for collisions, sections, wall thickness, components, masks, depth, normals, surface continuity, and fit.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `summarize_manifest.py`).

It sits in Development. The repository describes itself as: Public companion kit for ForgeCAD: examples, agent skills, docs links, and issue tracking. The hosted CAD app and core source live elsewhere. The licence is MIT.

When your agent uses it

  • Development work in your project

Example prompts

  • “/forgecad-inspect-model”

Requirements

  • Python 3

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

  1. Identify the failure question. What would make the model wrong: overlap, thin walls, hidden cavity failure, disconnected or accidentally…
  2. Confirm the model executes. If in doubt, run forgecad run model.forge.js first; add --debug-imports for suspect imports.
  3. Pick ONE targeted evidence command from the table below. forgecad inspect evidence lists everything available.
  4. Summarize the manifest first, then use jq against manifest.json for targeted follow-up. The helper ships beside this SKILL.md — invoke it…
  5. Inspect the PNGs, not only the JSON. View identity/context images first, then the risk evidence's view, then orthogonal cameras (front…
  6. Isolate intentional overlaps with --focus "A,B" or --hide "C" so the remaining report stays meaningful.
  7. Treat findings as model bugs: unexpected collisions, critical thin regions, high unresolved thickness area, wrong component counts…
  8. Report honestly. Include the exact command, bundle path, manifest highlights, and the PNG views actually inspected. Never claim geometry…

What it can do on your machine

Read from SKILL.md and the folder at commit 7523f68. 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

    Ships script files (Python), which the agent can run.

    Shell commands in SKILL.md call:

    • python

    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

Forgecad Inspect Model loads about 1.3k tokens when it runs. Until then it costs about 46 tokens; SKILL.md has 565 words of instructions outside code blocks.

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

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 ForgeCAD/forgecad-public-kit at commit 7523f68, republished under its MIT licence (© ForgeCAD). 565 words, ~1,261 tokens.

Download SKILL.mdSave it as .claude/skills/forgecad-inspect-model/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
forgecad-inspect-model
description
Select, run, and interpret ForgeCAD inspection evidence for collisions, sections, wall thickness, components, masks, depth, normals, surface continuity, and fit.
forgecad-public
true

Inspect Model

Use forgecad inspect ... when a shaded render is too ambiguous and you need structured evidence: a bundle directory with evidence PNGs plus a root manifest.json (or, for inspect section, a probe directory with result.json, section.svg, section.png). Inspection is not a substitute artifact: look inside with sections, masks, --focus/--hide, and transparency — never edit the model into a cutaway or exploded default to make inspecting easier. Output dirs: let inspect allocate its timestamped directory by default (repeated probes never collide); use /tmp/<model>-inspect for throwaway bundles, a project directory only for persistent artifacts.

Routing: authoring/API questions → forgecad skill; creating a new model → forgecad-build-model.

Workflow

  1. Identify the failure question. What would make the model wrong: overlap, thin walls, hidden cavity failure, disconnected or accidentally fused bodies, floating parts, orientation artifacts, identity confusion?

  2. Confirm the model executes. If in doubt, run forgecad run model.forge.js first; add --debug-imports for suspect imports.

  3. Pick ONE targeted evidence command from the table below. forgecad inspect evidence lists everything available.

  4. Summarize the manifest first, then use jq against manifest.json for targeted follow-up. The helper ships beside this SKILL.md — invoke it skill-dir-relative; it accepts the bundle directory or a manifest.json path:

    bash
    python <this-skill-dir>/summarize_manifest.py /tmp/model-inspect

  5. Inspect the PNGs, not only the JSON. View identity/context images first, then the risk evidence's view, then orthogonal cameras (front, right, top) when iso hides the issue, sections only when internals matter. In automation, resolve file paths through the manifest — custom cameras break canonical filenames.

  6. Isolate intentional overlaps with --focus "A,B" or --hide "C" so the remaining report stays meaningful.

  7. Treat findings as model bugs: unexpected collisions, critical thin regions, high unresolved thickness area, wrong component counts, floating bodies, or surprising gaps mean fix the model and reinspect.

  8. Report honestly. Include the exact command, bundle path, manifest highlights, and the PNG views actually inspected. Never claim geometry is verified if you only ran forgecad run.

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

Evidence Selection

QuestionEvidence command
Quick visual sanityinspect visual image
Kinematic rig, joints, axes, and linksinspect visual rig
Object naming and identityinspect visual objects
Exact local section measurement, bore widths, rib thickness through a chosen lineinspect section --ray ...
Hidden internals, cavities, pockets, screw paths, captured componentsinspect sections at|stack|sample
Multi-part interference, fit checks, ghost parts, moving clearancesinspect fit interference
Printability, shell walls, ribs, bosses, snaps, slotsinspect manufacture thickness plus inspect sections at|stack|sample when internals matter
Parts without a mesh-contact path to the groundinspect physical floating
Accidental fusion, connected solidsinspect physical components
Air gaps between physical componentsinspect physical gaps
Surface orientation, occlusion, faceting, strange protrusionsinspect visual depth or inspect visual normals
Loft, fillet, skin, and sweep surface continuityinspect surface zebra or inspect visual normals
Reference-vs-candidate reconstruction comparisoninspect compare overlay --with reference.3mf

Section Probe + Replay

The agent-native measure-then-recheck loop:

bash
forgecad inspect section model.forge.js --plane yz --ray bore:-20,0:20,0
forgecad inspect replay outputs/inspect/<probe>/result.json --source candidate.forge.js

The probe's result.json field contract (frames, rulers, gaps, replaySpec) is documented in the forgecad skill's docs/guides/inspection-bundles.md.

Misread Traps

  • Face-touching is not a collision; collision findings are positive-volume overlaps.
  • Gray/unresolved thickness area means the evidence is incomplete, not that the model is safe.
  • Distance/gap figures are bbox-gap metrics between components, not closest-surface distances.
  • Depth, normals, and zebra are visual aids (heatmap, camera-view normals, stripe shader), not exact measurements or curvature proofs.
  • Resolve mask colors through the manifest's object list, never by object order.

Reference

Bundle/manifest contract, evidence semantics, and current limits: the forgecad skill's docs/guides/inspection-bundles.md. CLI flags and command tree: its docs/CLI.md.

© ForgeCAD, 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 skills/forgecad-inspect-model of ForgeCAD/forgecad-public-kit.

  • SKILL.md
  • summarize_manifest.py

Open the folder on GitHubat commit 7523f68

Compare with similar skills

Forgecad Inspect Model 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.

Forgecad Inspect Model compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Forgecad Inspect Model this skillForgeCAD/forgecad-public-kit941—~1.3kAutomated safety check: PassMIT
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 ForgeCAD/forgecad-public-kit

All 10 skills in this repo

  • Forgecad Verify Mujoco

    ForgeCAD/forgecad-public-kit

    Verify a ForgeCAD MJCF export in MuJoCo with dynamics, contacts, controls, joint travel, and rendered evidence before calling it simulation-ready.

    941 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

  • Forgecad Reconstruct From Images

    ForgeCAD/forgecad-public-kit

    Reconstruct a real parametric ForgeCAD object from reference images by using images as evidence, not as a one-view facade.

    941 GitHub stars~1.3k tokensUpdated 3 mo ago
    Auto-check passed

  • Forgecad Reconstruct Cad File

    ForgeCAD/forgecad-public-kit

    Reconstruct a readable parametric ForgeCAD model from an existing CAD or mesh file such as STL, OBJ, 3MF, STEP, or STP.

    941 GitHub starsUsed in 1 repo~919 tokens
    Auto-check passed

  • Forgecad Design Spec

    ForgeCAD/forgecad-public-kit

    Create a ForgeCAD design brief, HLD, or LLD before coding by walking through use, assembly, interfaces, decisions, and verification.

    941 GitHub stars~2.5k tokensUpdated 3 mo ago
    Auto-check passed

  • Forgecad

    ForgeCAD/forgecad-public-kit

    ForgeCAD model authoring, editing, debugging, and execution guidance for .forge.js, SVG-import, assembly, and CLI workflows.

    941 GitHub stars~1.6k tokensUpdated 3 mo ago
    Auto-check passed

  • Forgecad Grade Model

    ForgeCAD/forgecad-public-kit

    Grade a ForgeCAD or CAD-as-code model against a requirement, brief, prompt, reference, or acceptance criteria with evidence and a 0-10 score.

    941 GitHub stars~1.3k tokensUpdated 3 mo ago
    Auto-check passed

Categories

Questions about Forgecad Inspect Model

What does Forgecad Inspect Model do?

Select, run, and interpret ForgeCAD inspection evidence for collisions, sections, wall thickness, components, masks, depth, normals, surface continuity, and fit. Forgecad Inspect Model is an agent skill from ForgeCAD/forgecad-public-kit. Select, run, and interpret ForgeCAD inspection evidence for collisions, sections, wall thickness, components, masks, depth, normals, surface continuity, and fit.

When should I use Forgecad Inspect Model?

Forgecad Inspect Model fits situations like: development work in your project.

How do I install Forgecad Inspect Model in Claude Code?

Run `npx skills add ForgeCAD/forgecad-public-kit --skill forgecad-inspect-model -a claude-code`. Or copy the skill folder (skills/forgecad-inspect-model in ForgeCAD/forgecad-public-kit) into .claude/skills/forgecad-inspect-model in your project. Claude Code loads it when a task matches its description.

How do I install Forgecad Inspect Model in Codex?

Run `npx skills add ForgeCAD/forgecad-public-kit --skill forgecad-inspect-model -a codex`. Or copy the skill folder (skills/forgecad-inspect-model in ForgeCAD/forgecad-public-kit) into .agents/skills/forgecad-inspect-model in your project. Codex loads it when a task matches its description.

Can I use Forgecad Inspect Model 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 ForgeCAD/forgecad-public-kit --skill forgecad-inspect-model -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/forgecad-inspect-model, .gemini/skills/forgecad-inspect-model, .github/skills/forgecad-inspect-model and .opencode/skills/forgecad-inspect-model in your project.

What does Forgecad Inspect Model need to run?

Going by SKILL.md and its folder, Forgecad Inspect Model needs Python for the scripts in its folder and the command-line tools its instructions call (python). Our summary lists: Python 3.

Does Forgecad Inspect Model 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 Forgecad Inspect Model 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 Forgecad Inspect Model use?

Forgecad Inspect Model is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Forgecad Inspect Model use?

About 1.3k tokens (SKILL.md is roughly 5k 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 Forgecad Inspect Model?

Skills that share tags, products or a category with Forgecad Inspect Model: 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 Forgecad Inspect Model?

ForgeCAD (a GitHub organization) maintains it in ForgeCAD/forgecad-public-kit, which has 941 GitHub stars. The repository holds 10 skills in this directory. The repository was last updated on June 15, 2026.

Source: ForgeCAD/forgecad-public-kit on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.