validate SKILL.md skillA
validate from partcad/partcad is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add partcad/partcad/validate@git:20261014.8f07d63Pins git:20261014.8f07d63 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- partcad/partcad
- Path
ai-agents/common/skills/validate/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261014.8f07d63, committed Oct 14, 2026
- First version recorded
- Oct 13, 2026
- Size
- 7,900 bytes
- Repository stars
- 507
- License
- Apache-2.0
Validate a PartCAD part, assembly, scene or sketch against the requirements its `requirements:` section declares - run `pc test` for the ports, interfaces and physics PartCAD measures, run every simulation, render it from every angle that matters with its ports and interfaces drawn, read the bill of materials and the assembly instructions of an assembly, and reason about whether each feature is met. Use for /pc:validate, when the user asks whether a design meets its requirements, or when the…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# pc:validate Decide whether an object is what it was required to be. `$ARGUMENTS` names the object (a part by default; an assembly, a scene or a sketch when the user says so, or when the package declares it as one). An object's `requirements:` has two halves, and they are validated two ways: - **What PartCAD measures** — `ports:`, `interfaces:` and `physics:`. These are checked by `pc test` (its `requirements` check), and its verdict is the verdict. You report it; you do not second-guess it. - **`features:`** — a name and a sentence each: "takes an M3 screw from either side", "does not tip over on a 10° slope". Some are demonstrated by a simulation that names them (`feature:` on a `simulate:` entry). Every one of them is for *you* to judge, from evidence you gathered and can point at. The verdict on a feature is never a guess. If nothing you gathered shows it, the verdict is "cannot tell" and you say what evidence would settle it — not "met". Pass `--no-ansi` on every run (it is global and goes before the subcommand): the output is then plain text, logged to stderr, so capture both streams (`2>&1`). Make sure PartCAD is available as `/pc:init` describes. …
Read the whole file at its exact version.
How to install
mdr add partcad/partcad/validate@sha256:64977ddadde6addcThe line at the top of this page pins the label git:20261014.8f07d63, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_popjvnpnwdiknwaw)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 13, 2026 and Oct 14, 2026, about one every day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261014.8f07d63 latest | 2026-10-14 | 8f07d63 | 7,900 B | A | view · diff |
| git:20261013.ce7c6cc | 2026-10-13 | ce7c6cc | 7,326 B | A | view |
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7900 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
partcad/partcad · 507 stars · license Apache-2.0 · pushed 2026-10-19 · branch devel
API
GET https://markdownregistry.com/api/v1/artifacts/art_popjvnpnwdiknwaw GET https://markdownregistry.com/api/v1/resolve?ref=partcad/partcad/validate GET https://markdownregistry.com/api/v1/blob/64977ddadde6addcf2e2a0a2256dace7f41d16ac1ae719f8638465ef478613c4
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.