Skills and resources

Browse and use skills, prompts, agents, fleets, and plugins.

Find a useful skill

The Library contains skills, agents, prompts, playbooks, plugins, and extensions. Open /library or press Alt+L. Switch categories with left/right, search with /, and open a package with Enter.

clio-coder library update --all updates eligible copies, clio-coder library package <directory> turns a skill directory into a package, and clio-coder library validate checks what you author.

Use Browse to find available content and Installed to manage your copies. Choose User for tools shared across projects or Project for resources specific to this workspace.

install uses user scope unless you pass --project; s switches scope in the Library. Project packages live under .clio-coder/plugins/.

For example, preview and install the test-driven-development skill:

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

Then activate it in the terminal:

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

Write your own prompts and skills

A file such as .clio-coder/prompts/bugfix.md runs as /bugfix. A SKILL.md with a description in .clio-coder/skills/<name>/ loads with /skill <name>. Prompts and skills that Claude Code, Codex or OpenCode keep in your home folder are found without copying; copies inside a project wait until you trust them.

Move your prompts, skills and settings to another machine with a share archive:

clio-coder share export --out project.clio-coder-share.json --project
clio-coder share import project.clio-coder-share.json --dry-run

Command reference

Prefix each with clio-coder. A reference is kind:name, such as skill:tdd, or an unambiguous bare name. update --all skips extensions, which each need their own review.

Review before installing

The install review shows the destination, dependencies, and verified package pin. In the Library, the selected row offers install, update, enable/disable, and remove actions when applicable. Management actions name the owning package and selected scope.

Project packages take precedence over matching user packages. A disabled project copy also suppresses the user copy, so a project can explicitly keep a resource unavailable. A project package set you have not approved for the workspace is listed but not loaded, and does not override your user copy; see plugins.

Trust project packages

A project copy comes from the repository, so its digest proves integrity, not your consent. Approve project packages per workspace:

clio-coder config trust plugins
clio-coder config trust plugins --hash <sha256>

The first is a read-only review; the second approves what you reviewed, and --revoke withdraws it. /reload library applies it to a running session. A changed package identity needs a new review, and an import never approves one.

Refresh a running session

After changing recipes through another process, run:

/reload library

Disabling a package prevents subsequent discovery; it does not stop an in-flight tool or erase instructions already read. Disable deletes no files; library enable <ref> restores the package. Disabling and removal apply without a reload, while installs from another process need /reload library. /skill off clears an active skill's armed tool surface without erasing earlier context.

For bundles of related resources, see plugins. To review resources from other coding agents, see interoperability.

Related tutorials