Skills

#Getting them

The skills come with the plugin; installing the plugin is the whole step. One distribution serves both Claude Code and Codex.

vitrinka install     # plugin, skills, MCP, token

#Invoking one

Each skill is a slash command. Most are also triggered by describing the job in plain words — you rarely have to remember the name.

/vitrinka:listen
/vitrinka:resolve testing-11-7
/vitrinka:publish

#Auto-scoping, and why it matters

A skill given no board infers its scope from the repository and the current git branch — the project name comes from the main worktree, the same derivation vitrinka push uses.

• Several sessions can work at once — each holds its own project+branch scope without stepping on the others.
• The global queue is never the default — an unscoped listing is a firehose containing other sessions' work; skills scope before they read.

#The four jobs

Seventeen skills, and they fall into four groups. Each has its own page.