Skills and plugins

Claude Code can be extended with skills, plugins and commands. Vitrino does not manage any of them — it reads whatever your machine and project already provide, and shows what runs.

Skills

A skill is a packaged set of instructions for a kind of task, loaded when it is relevant.

When Claude runs one, the transcript shows a row naming the skill. What the skill then does — commands, edits, searches — appears as ordinary rows beneath it.

Skills come from your project's .claude directory, your user configuration, and any plugins installed. Vitrino lists the ones available to a session in the session details at the top of the transcript.

Plugins

A plugin bundles skills, commands and sometimes MCP servers. Anything a plugin adds shows up in the same places as anything else: its commands in the / palette, marked as coming from a plugin; its skills as skill rows.

Plugin commands are named plugin:command, and the palette shows the plugin as a label so you can tell where a command came from.

Commands

See Slash commands.

MCP servers

See MCP servers.

Adding them

Vitrino has no UI for installing skills or plugins, by design — it is a presentation layer over Claude Code, not a replacement for it. Install them the way Claude Code documents, and they appear in Vitrino next time the session picks up the change.

Claude Code pushes an updated command list when it changes, so a command you add mid‑session shows up without a restart.

Hooks

Hooks are project‑configured scripts Claude Code runs around tool use. They are usually noise, so Vitrino groups them into a single muted line saying how many ran.

A hook that stopped a turn is not noise, and is not grouped: the turn footer says a hook stopped it, and the hook's output is in the line above.