DocsWorking with Alran
Plugins, skills and hooks
Skills teach Alran a kind of work, plugins bring skills, MCP servers and hooks together. Many are built in.
Which skills are built in?
Alran Code ships with skills for code review, deep research, Word documents, spreadsheets, slide decks, PDFs and for writing new skills. They work offline, right after install. /skills lists them, /review reviews your local changes.
The Plugin Store and the Skill Library
The Plugin Store offers plugins from one or more stores; the Skill Library is the same catalogue seen as single skills. Alran Code reads the store Ottili hosts, which holds skills and plugins from open-source projects and platform vendors, unmodified and with their licenses.
alran plugin search <words> # find a plugin
alran plugin info <name> # what is in it, and what it runs, before you install
alran plugin install <name>
alran skills search <words> # find a single skill
alran skills install <name>
alran plugin marketplace add <url> # read another store as wellIn the TUI, /plugin opens the Store and /skills library opens the Skill Library: type to search, Enter installs or updates, Space switches a plugin on or off, Delete removes it.
Every download is checked against the SHA-256 and content digest pinned in the store's index before anything is written. A plugin that runs commands or connects to services is shown to you first: you approve the list, or it is not installed. Alran never overwrites a plugin or skill you put there yourself. A store is not signed, though: whoever controls it controls what it lists, so add only stores you trust (alran plugin marketplace add <url>). ALRAN_STORE_URL=off switches Ottili's store off.
Manage plugins
alran plugins list # installed plugins
alran plugins list --available # plus what the stores offer
alran plugins update [name]
alran plugins disable <name>
alran plugins enable <name>
alran plugins remove <name>
alran plugins marketplace list # stores and the local plugin folder/reload reloads plugins after a change.
Local plugins
A folder in ~/.alran/plugins/<name> is an installed plugin. Alran reads three manifest formats:
| Format | Manifest |
|---|---|
| Alran | .alran-plugin/plugin.json |
| Claude Code | .claude-plugin/plugin.json |
| Codex | .codex-plugin/plugin.json |
So the skills and MCP servers you already use with another agent come along.
Write a plugin
A plugin is a folder with .alran-plugin/plugin.json: name, version, description, author, icon, category, and at least one of skills, MCP servers, apps or hooks. Check it with node tools/plugins/validate-plugin.mjs <folder> from the Alran Code repository.
Hooks
Hooks run your own commands at fixed points: when a session starts, before and after a tool runs, when a permission is requested, when a subagent starts or stops, and when a turn ends (Stop). A hook that prints a systemMessage shows a notice in the TUI without adding it to the model's context:
{
"hooks": {
"Stop": [{
"hooks": [{ "type": "command", "command": "node \"${PLUGIN_ROOT}/scripts/notice.cjs\"", "timeout": 5 }]
}]
}
}Common questions
Which skills are built in?
Alran Code ships with skills for code review, deep research, Word documents, spreadsheets, slide decks, PDFs and for writing new skills. They work offline right after the install, the command /skills lists them and /review reviews your local changes.
How do I install a plugin from the store?
Use alran plugin search and alran plugin install, or alran skills search and alran skills install for a single skill. Every download is checked against the SHA-256 and the content digest pinned in the store, and a plugin that runs commands or connects to services is shown to you before it installs.
How do I use my own plugin folder?
A folder in ~/.alran/plugins that you name yourself is an installed plugin. Alran reads three manifest formats: .alran-plugin/plugin.json for Alran, .claude-plugin/plugin.json for Claude Code and .codex-plugin/plugin.json for Codex, so the skills and MCP servers you already use come along.