CLACOROO
EN IT
Download

Skills

A skill is a piece of context Claude Code loads on demand — a Markdown file in a plugin that teaches the assistant how to do one specific thing (write a SQL migration, explain a flag, build a regex, …). The Skills section in CLACOROO is your catalogue of every skill across every installed plugin, with inline preview.

You don’t enable or disable skills here — they belong to their plugin and travel with it. This is the explorer: see what you have, learn what each skill does, and copy the trigger to use it.

Overview

The Skills section, a grid of skill cards grouped by plugin.

A grid of skill cards (or rows in Compact view). Each card carries the skill name, the plugin that ships it, a short description, a status dot (ok / warning / error), and the trigger pattern Claude Code recognises.

A topbar above the grid lets you filter by plugin, search by name, sort, and toggle Cards / Compact view.

What it shows

Skill card

A single skill card with name, plugin badge, description, status dot and Open / Copy buttons.

The card shows everything you need to decide whether to use the skill:

  • Name — the skill identifier
  • Plugin badge — which plugin bundles it
  • Description — the first 1-2 sentences from the skill’s front matter
  • Status dot — ok (green), warning (yellow), error (red)
  • Actions — Open preview, Copy command, Open in VS Code

Skill preview (modal)

The skill preview modal showing the Markdown content with code blocks and headings rendered.

Click Open preview (or the skill title) to read the full Markdown the skill contains — the same content Claude Code will see when the skill activates. Code blocks, headings, lists are rendered properly so you can read it like documentation.

The modal is non-modal in spirit: you can scroll, copy text, and close it without losing your place in the section.

Trigger / command

A skill card with the trigger pattern highlighted and a copy button next to it.

Most skills declare a trigger pattern in their front matter (e.g. "when X happens", or a regex, or an explicit instruction). CLACOROO surfaces it with a Copy command button so you can:

  • Paste it into your Claude Code chat to invoke the skill on purpose, or
  • Use it as reference when writing prompts that should activate the skill

Filters and grouping

  • Filter by plugin — keep only skills from a specific plugin
  • All types / From plugins — when both global and plugin-shipped skills exist, separate them
  • Search — matches name and description
  • Sort — name A→Z, name Z→A, plugin A→Z, plugin Z→A

In Cards view, skills are visually grouped by plugin (with a colored marker per plugin). In Compact view they’re shown as a dense list with the same grouping made explicit by a separator row.

Common tasks

How to invoke a skill from Claude Code

  1. Find the skill in the section, read its description in the card
  2. Open the preview if you want to know exactly what context it adds
  3. Click Copy command to grab the trigger pattern
  4. Paste it (or rephrase it naturally) in your Claude Code session
  5. The skill activates and the relevant context is added to the prompt

How to read what a skill does

Open its preview: it’s literally the skill’s Markdown file, rendered. If something looks wrong (broken code block, missing front matter), CLACOROO shows the parse error in a banner at the top of the preview.

How to edit a skill

Click Open in VS Code on the card. CLACOROO opens the skill’s file in VS Code so you can edit it directly. Save, and CLACOROO picks up the change on the next refresh (or immediately if the file watcher is responsive).

Note. Editing a skill shipped by a marketplace plugin counts as a local modification — claude plugins update <plugin> will overwrite it. If you want to keep changes, fork the plugin or copy the skill into a local-scope plugin.

How to find skills with errors

  1. Look for red status dots on cards (or red rows in Compact view)
  2. Open the preview — the parse error appears at the top
  3. Either fix the file (Open in VS Code) or report it upstream to the plugin author

Tips & shortcuts

  • The grouping by plugin in Cards view tells you which plugin is contributing what — a quick way to audit what each plugin actually adds to your context
  • Search is case-insensitive and matches partial words: typing mig finds migration, migrate, mighty indifferently
  • The preview modal’s first lines often contain the skill’s trigger condition in plain English — read those if the copy command isn’t obvious
  • A skill with 0 description simply hasn’t filled in its front matter — open it in VS Code to add one and improve discoverability

Edge cases & errors

  • No skills appear even though you have plugins installed. Either none of your plugins ships skills, or they’re disabled. Open the Plugin manager to check.
  • A skill’s preview shows a parse error. Its front matter or one of its Markdown blocks is malformed. The error message points to the line.
  • A copied command doesn’t activate the skill in Claude Code. Try rephrasing in natural language matching the trigger description. Some skills use semantic triggers, not exact strings.
  • Skills appear duplicated. Two plugins ship a skill with the same name. The plugin badge on each card tells you which is which.
  • Agents — the cousin of skills: agents bring tools and behavior, skills bring knowledge
  • Plugin manager — the source of every skill listed here
  • Concepts — the difference between skill, agent, hook, MCP server explained in plain English
  • Dashboard — the Skills (index) category on the context bar adds up everything in this section