vorn-extension-author
Skill25 starsChanged 27 days agoMITView on GitHub
Write, change or review a Vorn extension (a program, a Wasm component or one-shot commands), including the ones Vorn ships from vorn-run/extensions. Use for anything touching a vorn-extension.toml, the extension API's version, or what an extension may call.
In this repository3 other files it gives its agents.
- rust-idiomsSkill
- vornui-craftSkill
- vorn-wp-builderSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Read docs/extensions.md first, then docs/wasm-extensions.md for components and the element tree.
- Very specific: line 14
One API,
vorn:extension@1.0: Never add another api id. Every manifest sets api = "vorn:extension@1.0". - Very specific: line 22
A built-in builds on
vorn-extension-sdkalone: No other path dependency, no vorn_extension_sdk::bindings or ::guest.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Writing a Vorn extension
Read docs/extensions.md first, then docs/wasm-extensions.md for
components and the element tree. The API is defined once, in
packages/core/crates/extensions/wit/extension.wit.
The rules
- One API,
vorn:extension@1.0. Never add another api id. Every manifest setsapi = "vorn:extension@1.0";vorn = ">=1.0"is optional and is a range of API versions, not of Vorn releases. - Public only. An extension, Vorn's own included, calls only the
methods in
CORE_METHODS(gate.rs) and listens only toCORE_EVENTS(events.rs), each under the permission its manifest declares. If it needs something the API cannot do, add it to the API (WIT,gate.rs, docs), never a private path. - A built-in builds on
vorn-extension-sdkalone. No other path dependency, novorn_extension_sdk::bindingsor::guest. An exception goes inpackages/core/freeze.tomlwith a one-line reason. - The core stays frozen. A new place where a core or host crate names a
built-in (its id, its crate or its vornd module) fails
cargo test -p vorn-extensions --test freezeuntil it is listed infreeze.tomlunder[exceptions.hooks]with a reason. Prefer moving the behaviour behind the public API. - Versioning. A minor version only adds. Changing or removing anything
is a major: bump the WIT package,
wit/stdio.json(VORN_UPDATE_WIT=1 cargo test -p vorn-extensions publishes_the_mapping) and every manifest, and say so in the PR. - Handshake. A program checks
guest.init'sctx.apiand refuses a Vorn older than it was built for with a message naming both versions; a component is checked by vornd before linking. - Own workflows only. Seeded workflow ids and unseed prefixes start
with
<extension id>:, andworkflow.runruns only those. Running another's workflow, or seeding a script, agent or undeclared step, needsprocess.run.
Checks
cargo test --profile ci -p vorn-extensions --test freeze
cargo test --profile ci -p vorn-extensions --lib compatA manifest error names its field and line; keep it that way in any new
field you add to manifest/file.rs.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

