Individual skill
pack-authoring
Build a new nopekit pack — a reusable validation capability for a physical domain (CFD, FEA, thermal, chemical, optics, machining, sourcing). Use when a claim has no gate and the extension protocol has been followed, when wrapping a solver or analysis tool as a gate, when extracting existing validation code into a shareable pack, or when someone wants to contribute a capability back to nopekit.
skills/pack-authoring/SKILL.md
Source commit 61f2e186a7db355cce6d1c7dd75c55389ea95a32
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 5, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 19
- Repository last updated
- Oct 26, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- 3d-printing Repository topic
- agentic Repository topic
- ai-agents Repository topic
- cad Repository topic
- cfd Repository topic
- claude-code Repository topic
- claude-code-plugin Repository topic
- design-automation Repository topic
- engineering Repository topic
- finite-element Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Authoring an nopekit pack
A pack is how a validation capability stops being a one-off. You built a gate for
your project; a pack is that gate made reusable, self-testing and contributable.
Read `${CLAUDE_PLUGIN_ROOT}/docs/PACK_FORMAT.md` for the contract. This skill is the *procedure*.
Where no host filled `${CLAUDE_PLUGIN_ROOT}` in (Codex), it is the directory two above
this file: the plugin's root.
## Before you start
**Have you followed `${CLAUDE_PLUGIN_ROOT}/docs/EXTENSION_PROTOCOL.md`?** A pack is step 7 of that
protocol, not step 1. If you have not yet named the physical quantity precisely,