Skip to main content
Skills and plugins extend stagewise beyond its default capabilities. Skills teach the agent about your project. Plugins add new tools, integrations, and interactive features.

Skills

A skill is a set of instructions the agent follows when working on specific tasks. You create skills as SKILL.md files in your workspace.

How skills resolve

When the agent picks up a task, it checks whether any skills match the trigger, then resolves them in priority order: Higher-priority versions shadow lower ones when the same skill exists in multiple locations.

What skills do

Skills can teach the agent:
  • Project conventions — Naming patterns, file structure, preferred libraries
  • Domain knowledge — How your framework or system works
  • Workflows — Multi-step processes the agent should follow
  • Constraints — Rules the agent must respect

Skill locations and priority

Skill structure

A SKILL.md needs a clear trigger description:

Slash commands

Invoke skills explicitly with slash commands. Type / in the chat to see available commands from your skills and plugins.

Plugins

Plugins are pre-built extensions that can include skills, credential storage, and interactive mini-apps.

Built-in plugins

Plugin credentials

Some plugins need API keys or tokens. Credentials are encrypted on your machine and never exposed in plaintext. Configure them in Settings → Agent → Plugins.

Plugin apps

Plugins can ship interactive mini-apps that render inside the chat sidebar. The agent opens these apps and exchanges data with them — for example, a Figma plugin showing a design preview panel.

Skills vs plugins

What’s next

Agent context

Understand how skills fit into the agent’s context system.

Skills & context reference

Configure skills and context files per workspace.

Plugins reference

Manage installed plugins and configure credentials.
Last modified on June 3, 2026