metamask/ocap-kernel · Archived
How to add entries to the glossary
npx skills add metamask/ocap-kernel --skill glossary
This repository is archived — consider an actively maintained alternative.
How to check code by linting, building, and testing.
4 installsUpdates changelogs for all packages with consumer-facing changes.
4 installsHow to review code; a pull request, feature branch, local changes etc.
4 installsCreate a new monorepo package using the create-package CLI
3 installsRelated neighbors and high-traction skills in the same topics — useful to compare before installing.
When the user wants to create, optimize, or audit glossary page content and structure. Also use…
895 installsUse when building reusable Obsidian glossary notes from an existing paper source manifest, opti…
7 installsManage terminology glossary with Vale. TRIGGERS - sync terms, glossary validation, add terms, V…
133 installsOther skills from metamask/ocap-kernel.
npx skills add metamask/ocap-kernel
Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.
main
Files included with this skill beyond the listing page.
SKILL.md
545 B
SUMMARY.md
50 B
The [glossary](../../docs/glossary.md) explains terms with specific meanings in this project. When a new term is introduced—or an old term without a glossary entry discovered— consider adding the term to the glossary.
When doing so:
[term](../path/to/file.ts) syntax[term](#term) syntax to link related concepts