SKILL.md file with instructions, and Craft Agents adds it to its toolkit—using it automatically when relevant, or when you @mention it directly.
Skills follow the Agent Skills open standard, making them compatible with Claude Code and other tools that support the spec.
Creating Skills
Just ask Craft Agents to create one. Describe what you want, and the agent will create the skill for you:Skill Structure
Skills are folders in your workspace containing aSKILL.md file:
SKILL.md Format
Frontmatter Fields
| Field | Required | Description |
|---|---|---|
name | Yes | Display name for the skill |
description | Yes | Brief description shown in skill list |
icon | No | Emoji (e.g., 🔧) or URL. Relative paths are not supported. |
globs | No | File patterns that auto-trigger this skill (e.g., ["**/*.test.ts"]) |
alwaysAllow | No | Tools to auto-allow when skill is active (e.g., ["Bash(npm test)"]) |
requiredSources | No | Source slugs to auto-enable when skill is invoked (e.g., ["linear"]) |
When a skill declares
requiredSources, those sources are automatically enabled for the session when the skill is invoked — so the agent has access to their tools from the first turn. Sources must be configured in the workspace and authenticated; unauthenticated sources are skipped and handled at runtime.For the full SKILL.md schema including advanced fields like
allowed-tools, context, and agent, see the Claude Code skills documentation.Using Skills
Mention the skill with@ in your message:
Skill Locations
| Location | Path | Precedence |
|---|---|---|
| Workspace | ~/.craft-agent/workspaces/{id}/skills/{slug}/ | First (overrides built-in) |
| Built-in | Bundled with Craft Agents | Fallback |