Creating Skills
Skills teach the agent how and when to use tools. Each skill is a directory containing aSKILL.md file with YAML frontmatter and markdown instructions.
For how skills are loaded and prioritized, see Skills.
Create your first skill
Write SKILL.md
Create
SKILL.md inside that directory. The frontmatter defines metadata,
and the markdown body contains instructions for the agent.Add tools (optional)
You can define custom tool schemas in the frontmatter or instruct the agent
to use existing system tools (like
exec or browser). Skills can also
ship inside plugins alongside the tools they document.Skill metadata reference
The YAML frontmatter supports these fields:| Field | Required | Description |
|---|---|---|
name | Yes | Unique identifier (snake_case) |
description | Yes | One-line description shown to the agent |
metadata.openclaw.os | No | OS filter (["darwin"], ["linux"], etc.) |
metadata.openclaw.requires.bins | No | Required binaries on PATH |
metadata.openclaw.requires.config | No | Required config keys |
Best practices
- Be concise — instruct the model on what to do, not how to be an AI
- Safety first — if your skill uses
exec, ensure prompts don’t allow arbitrary command injection from untrusted input - Test locally — use
openclaw agent --message "..."to test before sharing - Use ClawHub — browse and contribute skills at ClawHub
Where skills live
| Location | Precedence | Scope |
|---|---|---|
\<workspace\>/skills/ | Highest | Per-agent |
~/.openclaw/skills/ | Medium | Shared (all agents) |
| Bundled (shipped with OpenClaw) | Lowest | Global |
skills.load.extraDirs | Lowest | Custom shared folders |
Related
- Skills reference — loading, precedence, and gating rules
- Skills config —
skills.*config schema - ClawHub — public skill registry
- Building Plugins — plugins can ship skills