Source
One canonical skill definition with triggers, instructions, policy, and verification.
Good work should be
repeatable.
The Skills Library turns how we work into portable, governed capability that Claude, Cursor, and Codex can all use.
one source → three clients → less driftNOT A PROMPT FOLDER
A skill says when to act, how to act, what it may touch, and how the result will be verified.
01 / Library architecture
Write the method once.
Make it native everywhere.
CANONICALSKILL.mdtrigger · method · policy · proof
→VISIBLE LIBRARYNotion Skills DBregistry · lifecycle · ownership
→ClaudeCursorCodex
Registry
A visible Notion library records what exists, how it is governed, and where its runtime source lives.
Distribution
The same skill is fanned out to the native homes used by Claude, Cursor, and Codex.
Execution
Each client discovers the skill in its own language without maintaining three copies.
02 / Working examples
Capability you can call by name.
/batonRoute substantial work by judgment, cost, and evidence.
/deep-thinkingSlow down consequential decisions and surface the logic.
/build-verifyRequire real-path proof before calling a build complete.
/motion-shipMove finished work through a repeatable release gate.
/carefulApply higher caution to evidence, credentials, and irreversible changes.
/design-reviewEvaluate an interface against an explicit visual standard.
03 / Governance
Portable does not mean uncontrolled.
- Trigger The skill states when it applies.
- Model policy The work can name the judgment or cost lane it deserves.
- Read / write boundary The skill declares the systems it can inspect or change.
- Verification Completion has an acceptance test, not just a confident sentence.
- Registry parity The visible Notion record and runtime skill stay linked.