What are skills?
The concept, the file format, where skills live on disk, and how Cerevisor discovers them.
A skill is a small, focused capability you can attach to an agent. Think of it as a teaching aid: when an agent has a skill assigned, it knows how to do that specific thing.
Examples of real skills shipped in the Cerevisor ecosystem:
| Skill | What it does |
|---|---|
docx |
Creates, edits, and reads .docx Word documents. |
pptx |
Builds PowerPoint decks. |
xlsx |
Excel spreadsheet operations. |
recency-research |
Strict web-only research with publish-date enforcement and source validation. |
frontend-design |
Distinctive, production-grade frontend code without generic AI aesthetics. |
imagegen |
Generate images via Gemini's native image-gen models. |
brainstorming |
Structured creative ideation before building. |
Skills are not built into Cerevisor; they live as folders on your filesystem that Cerevisor discovers at launch.
Where skills live
Cerevisor scans several folders on startup and merges everything it finds:
| Folder | What's typically there |
|---|---|
~/.cerevisor/skills/ |
Skills you've created in Cerevisor's Skill Workshop, or installed only for Cerevisor. |
~/.claude/skills/ |
Skills you've installed for use with Claude Code. Cerevisor picks these up automatically; they're the same files, in the same format. |
~/.claude/settings/skills/, ~/.codex/skills/, ~/.opencode/skills/ |
Skills installed for other harnesses. Cerevisor surfaces them too, so you see all your skills in one place. |
Cerevisor also scans any additional roots you configure in Settings, and skills shipped inside enabled plugins.
If a skill with the same name exists in more than one folder, the first one found wins. The folders above are scanned in the listed order, so the ~/.cerevisor/skills/ copy takes precedence.
The skill file format
A skill is a folder containing a SKILL.md file. Minimal skill:
~/.claude/skills/my-skill/
└── SKILL.md
SKILL.md is markdown with a YAML frontmatter header:
---
name: my-skill
description: Use when X. Triggers on phrases like "do X", "build X", "make X". Do NOT use for Y.
---
# My Skill
Step 1: do this.
Step 2: do that.
Step 3: produce the output.
The name and description fields are required. The description is critical; it tells Cerevisor when to offer this skill to agents. Good descriptions specify:
- When to use the skill (the trigger conditions).
- What it does (so the agent knows what to expect).
- When NOT to use it (negative space).
A skill can also declare an optional compatibility: frontmatter field naming which providers it works with — see Skill compatibility with providers.
Skills written for Claude Code often reference that tool's own tool names (Read, Write, Bash, slash commands). Cerevisor detects this automatically and, when such a skill runs on one of Cerevisor's own agents, prepends a short translation note so the agent maps those instructions onto its own tools. You don't need to rewrite the skill.
Most skills include additional folders alongside SKILL.md, references/, scripts/, templates/, etc.; that the skill's own instructions reference. You don't need to know what's in those subfolders to use the skill.
How agents use skills
When you assign a skill to an agent, two things happen:
- The skill's
SKILL.mdis included in the agent's system prompt (so the agent knows the skill exists and how to use it). - If the skill includes scripts or templates the agent should call, those are made available.
The agent decides at run time whether to invoke the skill based on its instructions and the work being done. Skills aren't auto-fired; they're tools the agent can reach for.
Skill discovery
Cerevisor keeps a list of every skill it finds. That list is behind:
- The Skills panel in the right sidebar.
- The
find_skillstool (agents can ask for a skill that matches a task description). - The chat builder's awareness of what's available.
Fast start
When Cerevisor opens, the Skills panel shows your skills straight away from the last scan, then checks your skill folders again in the background and updates the list. A little later, your default model writes richer summaries of what each skill is for, and the panel updates again.
Semantic search
Cerevisor also runs a small model on your own computer (about 23 MB, downloaded once) so that skills can be found by meaning, not only by keyword: an agent asking for "make a slide deck" can find pptx even if the words don't match.
Three modes (Settings → Skills):
- auto (default): search by meaning when the model is available; otherwise by keyword only.
- on: always search by meaning (an error is shown if the model can't load).
- off: keyword only; the model is never loaded.
Where to go next
- Browse and assign skills: the actual UI for picking skills.
- Create a skill in the Workshop: make your own.