Introduction
One of the reasons OpenClaw is different from other AI assistants is its Skills system. Ai assistants can answer questions generate code or summarize documents.. What if you want your AI to follow a specific workflow every time?. For example you might want it to write blogs in your companys format.. You might want it to review code using your teams standards. Maybe you want it to generate emails following your organizations policies. This is where OpenClaw Skills come in.
What are OpenClaw Skills?
A Skill is a set of instructions that teaches the AI how and when to do a task. Of changing the model itself OpenClaw extends its behavior through Skills. Skills are written in a file. Each Skill is stored in its directory and has metadata and instructions that guide the agent. Think of a Skill like a manual.
Some examples of Skills include:
- Blog Writing
- Code Review
- Git Workflow
- Research Assistant
- Resume Builder
- Email Generator
Each one tells the AI how to approach that type of work.
Why Do We Need Skills?
Imagine asking an AI to "Write a blog." Without a Skill the output depends on the prompt. Now imagine you always want:
- Headings that are good for SEO
- Clean Markdown
- Code examples
- A professional tone
- A conclusion
- practices
Instead of repeating those instructions every time you create a Skill once. Then OpenClaw can reuse it whenever its needed.
Skills vs Tools
This is probably the misunderstood concept in OpenClaw.
| Skills | Tools |
|---|
| Tell the AI what workflow to follow | Perform actual actions |
| Written in Markdown | Implemented as executable capabilities |
| Define instructions and best practices | Read files, search the web, run Python, execute commands, etc. |
| Guide decision making | Produce results |
A Skill often tells the AI which tools to use and in what order.
How Does OpenClaw Load Skills?
OpenClaw looks for Skills in places. If two Skills have the name, the one with the highest priority wins.
Usually the priority is:
- Workspace Skills
- Project Agent Skills
- Personal Agent Skills
- Managed/Local Skills
- Bundled Skills
- Configured directories
This lets project-specific Skills override shared ones without changing the originals.
Where Are Skills Stored?
For Skills that are specific to a project:
workspace/
└── skills/
└── blog-writer/
└── SKILL.md
For Skills that're global:
~/.openclaw/skills/
Workspace Skills take precedence over global Skills. This makes them ideal for customizing projects.
What Happens Internally?
When you ask OpenClaw to do a task:
- You send a request.
- The Gateway gets it.
- The agent builds conversation context.
- Relevant Skills are discovered.
- The model decides if a Skill matches the request.
- If needed the Skill instructions become part of the prompt.
- The AI may call tools to complete the task.
- A final response is generated.
Building Your First Skill
Lets create a Blog Writer Skill.
Create the following directory:
workspace/
└── skills/
└── blog-writer/
└── SKILL.md
Now create the file:
name: blog-writer
description: Write professional technical blogs.
When writing a blog:
- Start with an introduction.
- Explain concepts step by step.
- Include examples.
- Use Markdown headings.
- Add a conclusion.
- Mention best practices where appropriate.
Reload the agent if necessary. OpenClaw also has commands like `openclaw skills list` and `openclaw skills check`.
Best Practices
- Keep one responsibility per Skill.
- Use names.
- Don't put workflows into the same Skill.
- Keep instructions testable.
- Store large reference material separately.