Skillpack anatomy
The canonical one-page reference for what a third-party modusbrain skillpack looks like. The reference pack atexamples/skillpack-reference/ is the
live artifact this page describes; clone its tree and you have a 10/10
starting point.
Tree
modusbrain skillpack init <name> scaffolds this exact tree, pre-filled
with stubs that score 10/10 on modusbrain skillpack doctor . --quick
immediately. Replace the stubs with real content, run the doctor
between edits, and modusbrain skillpack pack produces a deterministic
<name>-<version>.tgz ready to publish to the registry.
How the agent uses a scaffolded pack
Aftermodusbrain skillpack scaffold <source> lands the files:
- The user’s agent walks
skills/*/SKILL.mdfrontmatter and reads each pack’striggers:array on startup or per-message. - When a user phrasing matches a trigger, the agent reads that SKILL.md body top-to-bottom as in-context instructions.
- modusbrain DISPLAYS
runbooks/bootstrap.mdonce after the scaffold but does NOT auto-execute it. The agent decides whether to walk the steps. This is the codex T1 supply-chain hardening: an auto-walker would let a malicious pack mutate the user’s brain on install, which is how npm postinstall attacks happen.
How the doctor scores a pack
Ten binary dimensions. Each is checked by a pure function insrc/core/skillpack/rubric.ts and returns {passed, detail, fix_hint}.
The doctor walks them in order and prints the score + per-dimension
status + paste-ready fix for every failure.
<!— BEGIN auto-generated:rubric —>
Core dimensions (5; must all pass to publish at any tier)
Quality badges (5; earn for tier eligibility)
Generated from
src/core/skillpack/rubric.ts by bun run scripts/build-skillpack-anatomy.ts.
<!— END auto-generated:rubric —>
Tier eligibility
CLI reference (third-party path)
See also
examples/skillpack-reference/— the live 10/10 reference packdocs/designs/SKILLPACK_REGISTRY_V1_SPEC.md— strategic spec + decisionsdocs/guides/skillpacks-as-scaffolding.md— v0.36 scaffold/reference model