Add skills and plugins deliberately

CLIO Coder's Library contains skills, agents, prompts, playbooks, and plugins. You can add a procedure to one project or install it for your user. Preview what will be written, inspect the resource, and load it when a task needs it.

Browse what ships with CLIO Coder

Open /library in the terminal or press Alt+L. On the desktop alpha, the Library page lists the catalog with an Installed only filter. In the terminal, Browse shows available content and Installed manages your copies.

The terminal Library is one place. /library skills opens it on one kind, as do prompts, agents, playbooks, plugins and extensions; the old /skills, /prompts and /agents names are gone. /library install <ref> and the other verbs of clio-coder library open the review that command would apply. /library interop inspects the coding agents on your machine.

Inside the Library, b switches between Browse and Installed and s between user and project scope. i, u and x open the review for installing, updating or removing the selected package; nothing is written until you apply it. r refreshes.

Preview a small addition

1. 01

   Preview the install

   Start with a resource you can evaluate, such as the shipped test-driven-development skill:

   Shell

   clio-coder library install skill:tdd --project --dry-run

   The plain output names the planned step and its scope. Add --json to see the rest of the plan: the destination, the version it writes, the source with its sha256, and the dependencies.

   

2. 02

   Install it for this project

   Shell

   clio-coder library install skill:tdd --project

   The first project install in a workspace is yours, so CLIO Coder approves the project's packages for that workspace. After that, a changed project package set, including one that arrives with a clone or a pull, is listed but not loaded until you review it with clio-coder config trust plugins and approve the digest it prints.

3. 03

   Load it for one concrete task

   /skill tdd Add coverage for this parser before changing its behavior.

Choose project or user scope

Project packages take precedence over matching user packages, and a disabled project copy also suppresses the user copy. A project can therefore keep a resource unavailable instead of inheriting it from one developer's setup.

Scope helps reproducibility: another person can see which procedures belong to the project. It is not a filesystem sandbox, and the project's normal execution and tool controls still apply.

Use plugins for related resources

A Library plugin groups related skills, prompts, agents, playbooks, and supporting files. The catalog ships with CLIO Coder, but its content is not installed automatically.

clio-coder library list --kind plugin
clio-coder library install plugin:materio --dry-run

Review the bundle before installing it, and add --project when it should belong to the workspace. Local bundles use the same review flow; the plugin guide covers structure and lifecycle.

Installation records a pin over the complete package tree, and drifted content is blocked from loading. Verifying a pin is not a way to approve arbitrary edits to an installed package; use the documented update and review workflow.

Keep discovery separate from loading

A large Library should not mean every resource enters every model request. The coordinator starts with a smaller attached toolkit and discovers secondary capabilities when a task calls for them, and recipes load on demand.

Write clear resource descriptions and narrow procedures. A skill that explains one project's numerical-test conventions is easier to select and inspect than a bundle that promises to solve every task.

After changes made by another process, /reload library refreshes recipes and /skill off clears an active skill's armed tool surface. Neither erases earlier instructions from the conversation, and disabling a resource does not stop a tool already running.

Know when you need an extension

Library plugins provide portable recipes. Extensions are code that adds runtime tools, hooks, or interface behavior through clio-coder extensions, and load only after you approve the capabilities they declare.

Adding tool schemas requires a new session; reloading recipes does not change them. Project extensions follow the same trust rule through clio-coder config trust extensions, and CLIO Coder names any it ignored when a session starts.