Skills

Skills are sticky because most useful behaviors require more than one turn to play out: a code review touches multiple files, an onboarding assistant walks the user through a sequence, a research skill accumulates context. Per-turn prompt injection would force the user to repeat the activation command on every message. Sticky activation collapses that friction into a single decision.

A skill lives on disk as a directory under workspace/skills/ with a required SKILL.md file. The YAML frontmatter declares metadata, optional tier override, and optional MCP server. The Markdown body is the instruction text injected into the session.

workspace/skills/my-skill/
├── SKILL.md          # Required: instructions + metadata
├── scripts/          # Optional: helper scripts
├── templates/        # Optional: document templates
└── resources/        # Optional: reference files

---
name: github-assistant
description: Work with GitHub via MCP
tier: coding
mcp:
  command: npx -y @modelcontextprotocol/server-github
  env:
    GITHUB_PERSONAL_ACCESS_TOKEN: ${GITHUB_TOKEN}
  startup_timeout: 30
  idle_timeout: 10
---

Use the available MCP tools to work with GitHub.
Focus on the repositories the user asks about.
When creating issues or PRs, summarize first and ask for confirmation.

A skill moves through four states.

• Installed — the directory exists on disk, metadata is parsed, skill is visible in the marketplace. Not affecting any session.
• Activating— a user, chat command, or the agent's skill_management tool triggered the skill. Frontmatter is parsed, tier is overridden if declared, MCP server (if any) is started and handshaked.
• Active— instructions are in context, MCP tools are exposed. Subsequent turns see the skill's effect.
• Deactivated — the skill was dismissed or the session ended. The MCP server is stopped after its idle timeout. Instructions are removed from the next context build.

Activation can also be triggered from the Skills page in the dashboard or via the /skills chat command.

Install skills from Settings → Skills Marketplace (or use /skills in chat to list and activate installed skills). Custom skills appear automatically when you add a directory under workspace/skills/ with a valid SKILL.md.

---
name: code-reviewer
description: Review code for bugs and style issues
---

Review the provided code for:
- Logic errors and edge cases
- Style violations
- Missing error handling