OpenClaw Skills: The Ultimate Guide to Agent Capabilities

Skills are what make OpenClaw go from a generic AI assistant to a specialized expert. They're reusable instruction sets — written in plain markdown — that tell OpenClaw exactly how to handle specific types of tasks.

Think of skills like job descriptions for your AI agent. Without them, OpenClaw is a generalist. With the right skills loaded, it becomes a focused specialist that follows your team's exact processes.

How Skills Work

A skill is a markdown file that lives in your project's .openclaw/skills/ directory. When OpenClaw starts a session, it reads all available skills and uses them as context for task execution.

Here's a real example of a simple skill:

# Write Blog Post

## Instructions
When asked to write a blog post:
1. Research the topic using web search
2. Create an outline with H2 and H3 headings
3. Write in a casual, helpful tone — no corporate jargon
4. Keep paragraphs to 2-3 sentences max
5. Include code examples where relevant
6. Add an FAQ section at the end with 5 questions
7. Save to content/blog/[slug].md

## Tone
- Conversational but authoritative
- Use "you" and "your" — talk to the reader
- Data-backed claims with sources
- Short sentences. No filler.

## SEO Requirements
- Target keyword in H1 and first paragraph
- Meta description under 155 characters
- Internal links to at least 2 other posts

That's it. No special syntax, no configuration files, no API calls. Just markdown with clear instructions.

When you ask OpenClaw to write a blog post, it finds this skill, follows the instructions, and produces output that matches your standards every time.

Built-in vs Custom Skills

OpenClaw ships with a handful of built-in skills for common tasks:

| Built-in Skill | What It Does | | --------------- | ------------- | | code-review | Reviews code changes for bugs, style issues, and performance | | test-writer | Generates unit tests for existing code | | refactor | Restructures code while preserving behavior | | git-commit | Writes conventional commit messages from staged changes | | debug | Analyzes error messages and traces to find root causes |

Custom skills are where the real power is. You write them for your specific workflows, your team's conventions, and your product's requirements.

The awesome-openclaw-skills Repository

The community has gone wild building skills. The awesome-openclaw-skills repository on GitHub has 5,197 curated skills organized into categories:

| Category | # of Skills | Examples | | ---------- | ------------ | ---------- | | Development | 2,841 | API design, database migrations, CI/CD setup | | Marketing | 198 | SEO analysis, ad copy, social media calendars | | Productivity | 156 | Meeting summaries, email drafts, task prioritization | | Communications | 162 | PR writing, customer support responses, newsletters | | Data & Analytics | 324 | CSV processing, report generation, data visualization | | DevOps | 412 | Docker configs, Terraform plans, monitoring setup | | Other | 1,104 | Research, legal review, translation, accessibility audits |

516 of these skills are specifically for non-developer use cases. That number is growing fast as more non-technical teams adopt OpenClaw.

How to Install Community Skills

Grab a skill from the community repository:

# Clone the skills repo
git clone https://github.com/community/awesome-openclaw-skills.git

# Copy specific skills to your project
cp awesome-openclaw-skills/marketing/seo-audit.md .openclaw/skills/
cp awesome-openclaw-skills/marketing/content-calendar.md .openclaw/skills/

# Or copy an entire category
cp -r awesome-openclaw-skills/marketing/ .openclaw/skills/

OpenClaw detects new skills automatically — no restart needed.

How to Create Your Own Skills

Creating a custom skill takes about 5 minutes:

1. Create a markdown file in .openclaw/skills/

2. Give it a clear name (e.g., deploy-to-production.md)

3. Write instructions in plain English

4. Include examples of expected input and output

5. Add constraints (what NOT to do is just as important)

Here's a more advanced skill example for a marketing team:

# Generate Weekly Analytics Report

## Trigger
When asked for a "weekly report" or "analytics summary"

## Steps
1. Connect to Google Analytics via MCP server
2. Pull data for the last 7 days
3. Compare against the previous 7-day period
4. Calculate: sessions, bounce rate, conversion rate, top pages, traffic sources
5. Generate a summary with:
   - 3 key wins (metrics that improved)
   - 3 areas of concern (metrics that declined)
   - 3 recommended actions for next week
6. Format as a Slack-ready message with emoji headers
7. Save raw data to reports/weekly/[date].csv

## Output Format
Use bullet points, not paragraphs. Executives skim — make it scannable.
Round percentages to one decimal. Use arrows (↑↓) for trends.

## Don'ts
- Don't include raw API responses
- Don't speculate about causes without data
- Don't recommend actions that require engineering work (this is for marketing)

Top 10 Most Useful Skills

Based on community downloads and ratings:

1. seo-audit — Crawls a site, checks meta tags, heading structure, Core Web Vitals, and generates a prioritized fix list

2. api-documentation — Reads your API routes and generates OpenAPI specs with examples

3. content-repurposer — Takes a blog post and creates Twitter threads, LinkedIn posts, and email newsletter versions

4. database-migration — Generates safe migration scripts with rollback plans from schema diffs

5. competitor-analysis — Scrapes competitor sites and produces feature comparison matrices

6. test-coverage — Identifies untested code paths and generates targeted test cases

7. onboarding-guide — Reads your codebase and generates developer onboarding documentation

8. email-sequence — Creates drip email campaigns with subject lines, body copy, and send timing

9. incident-response — Analyzes error logs, identifies root cause, suggests fixes, and drafts a postmortem

10. data-cleanup — Validates, deduplicates, and normalizes messy CSV/JSON datasets

Skills for Teams

Skills become especially powerful when shared across a team. Instead of every person prompting OpenClaw differently, skills ensure consistent output quality and process adherence.

For teams managing multiple OpenClaw agents, RunAgents lets you assign skills to agents centrally, track which skills are being used, and share skill libraries across your workspace — all from a visual dashboard instead of managing files on disk.

Frequently Asked Questions

What format are OpenClaw skills written in?

Plain markdown. There's no special syntax or schema to learn. Write instructions in natural language, use headings to organize sections, and include code blocks for examples. OpenClaw parses the markdown and uses it as context during task execution.

Where do I put custom skills?

Drop them in your project's .openclaw/skills/ directory. OpenClaw scans this directory at startup and whenever new files are added. You can also organize skills into subdirectories — OpenClaw finds them recursively.

Can I use skills from the community repository?

Absolutely. The awesome-openclaw-skills repo has 5,197+ skills you can copy into your project. Just download the markdown file and place it in your skills directory. No installation step, no package manager — it's just files.

What's the difference between built-in and custom skills?

Built-in skills ship with OpenClaw and cover common developer tasks (code review, testing, debugging). Custom skills are ones you or the community write for specific use cases. Custom skills override built-in skills if they share the same name.

How specific should my skills be?

As specific as possible. A skill called "write-content" is too vague. A skill called "write-product-changelog-entry" with exact formatting rules, tone guidelines, and output location will produce dramatically better results. The more context you give, the less you have to correct.

Can skills call other skills?

Not directly — skills are passive instruction sets, not executable programs. However, you can reference other skills in your instructions ("follow the style guidelines in the brand-voice skill") and OpenClaw will pull in that context. For complex multi-step workflows, consider using a workflow orchestration tool like RunAgents.

Want skills managed by a team, not just one developer? RunAgents gives you managed OpenClaw hosting with task management, team collaboration, and agent debugging built in. Get started free

Related Guides

• What Is OpenClaw? -- Start from the basics

• OpenClaw Browser Relay -- Automate any website

• OpenClaw Chrome Extension -- Browser automation without code