Looking to get a VPS for your project? Vultr offers reliable VPS hosting starting at $5/month with global data centers. Many OpenClaw users self-host on Vultr for consistent uptime and affordable pricing.
\n
OpenClaw Skills: How to Install and Use Them
\n
Out of the box, OpenClaw can browse the web, read files, run commands, and chat via Telegram. But Skills take it much further. Think of Skills like apps for your AI agent — each one adds a specific new capability. This guide explains how the Skills system works, how to install Skills, and how to get the most out of them.
\n
What Are OpenClaw Skills?
\n
Skills are modular add-ons that extend what your OpenClaw agent can do. They’re typically a folder containing a SKILL.md file with instructions, plus any supporting scripts, templates, or reference data.
\n
When you install a Skill, your agent gains access to new knowledge and new abilities. The SKILL.md file tells your agent when and how to use the Skill — in plain English, not code. This makes Skills accessible to both developers and non-technical users.
\n
Some Skills are general-purpose, while others are highly specialized:
\n
- \n
- Weather Skill: Fetch current weather and forecasts for any location
- Coding Agent Skill: Delegate software development tasks to a sub-agent
- Healthcheck Skill: Audit your server’s security and configuration
- MCP Porter Skill: Connect and manage MCP (Model Context Protocol) servers
- Node Connect Skill: Diagnose connection issues with OpenClaw companion apps
\n
\n
\n
\n
\n
\n
How Skills Work
\n
When you send your agent a task, it scans the available Skills to see if any are relevant. If a match is found, the agent reads that Skill’s SKILL.md instructions before proceeding. This gives the agent specialized context it wouldn’t otherwise have.
\n
For example, if you ask about the weather, the Weather Skill tells your agent exactly which API to use, what format to request, and how to present the result clearly. Without the Skill, your agent could figure out weather lookup on its own — but the Skill makes it faster, more consistent, and more accurate.
\n
Where Skills Are Stored
\n
Skills are stored in the OpenClaw package directory, typically:
\n
- \n
- Windows:
%APPDATA%npmnode_modulesopenclawskills - macOS/Linux:
/usr/local/lib/node_modules/openclaw/skills/
\n
\n
\n
Each Skill is a subfolder with at minimum a SKILL.md file inside it.
\n
Built-In Skills
\n
OpenClaw ships with several Skills pre-installed:
\n
weather
\n
What it does: Gets current weather and forecasts using wttr.in or Open-Meteo APIs (no API key needed).
\n
When it activates: Whenever you ask about weather, temperature, or forecasts for any location.
\n
Example prompts: “What’s the weather in Chicago?” / “Will it rain this weekend in Seattle?”
\n
coding-agent
\n
What it does: Delegates complex coding tasks to a specialized sub-agent (Codex, Claude Code, etc.) that can explore your codebase and build features iteratively.
\n
When it activates: For building new features, reviewing code, refactoring large codebases, or iterative development tasks.
\n
Example prompts: “Build a Python script to parse my invoices” / “Review the code in /projects/myapp and suggest improvements”
\n
healthcheck
\n
What it does: Audits your host’s security configuration — firewall rules, SSH settings, system updates, and overall risk posture.
\n
When it activates: When you ask for security audits, hardening recommendations, or version checks.
\n
Example prompts: “Run a security check on this server” / “What’s my current risk exposure?”
\n
mcporter
\n
What it does: Manages MCP (Model Context Protocol) servers — letting your agent call external tools and services directly.
\n
When it activates: When managing or calling MCP server tools.
\n
node-connect
\n
What it does: Diagnoses connection issues between OpenClaw and companion apps (Android, iOS, macOS).
\n
When it activates: When you have QR code or pairing failures, connection errors, or setup code issues.
\n
skill-creator
\n
What it does: Helps create, edit, improve, or audit Skills themselves — including writing SKILL.md files and organizing Skill directories.
\n
When it activates: When asked to “create a skill,” “improve a skill,” “audit a skill,” etc.
\n
Installing a New Skill
\n
There are two ways to add Skills to OpenClaw:
\n
Method 1: From npm (Official Skills)
\n
If a Skill is published as an npm package, install it with:
\n
npm install -g openclaw-skill-[name]\n
The Skill will be placed in the correct location automatically.
\n
Method 2: Manually (Custom Skills)
\n
For custom or community Skills:
\n
- \n
- Download or create the Skill folder
- Place it in the
skills/directory of your OpenClaw installation - Make sure it contains a valid
SKILL.mdfile - Restart OpenClaw
\n
\n
\n
\n
\n
Creating Your Own Skills
\n
Skills are surprisingly easy to create — the core of any Skill is just a plain text markdown file. A basic SKILL.md contains:
\n
- \n
- A description of what the Skill does
- Instructions for when to activate it
- Step-by-step guidance for the agent
- Any relevant reference data, API details, or scripts
\n
\n
\n
\n
\n
You write Skills in plain English. No coding required for basic Skills.
\n
Example: You could create a “social-media” Skill that tells your agent the exact format, hashtags, and tone to use when drafting posts for your brand’s social media accounts.
\n
Use the built-in skill-creator Skill to get help writing new Skills:
\n
Create a Skill for [describe what you want it to do]
\n
Tips for Getting the Most from Skills
\n
- \n
- Keep Skills focused: One Skill, one job. Don’t try to cram everything into one SKILL.md
- Test with clear prompts: After installing a Skill, test it with prompts that closely match its description to confirm it activates correctly
- Update regularly: Official Skills may be updated with bug fixes and improvements — keep OpenClaw updated to get them
- Document your custom Skills: If you build a Skill for your own use, write clear notes in the SKILL.md about what it does and what prompts activate it
- Use reference files: Large reference data (like a product catalog or FAQ) can be stored in the Skill’s
references/subfolder and loaded when needed
\n
\n
\n
\n
\n
\n
Skill Ideas for Common Use Cases
\n
Here are some custom Skills worth building for everyday users:
\n
- \n
- email-summarizer: Instructions for how to summarize your emails with the right priority levels and format
- social-media: Brand voice, posting schedule, and hashtag guidelines for your social accounts
- research-reporter: A template and process for how to produce research reports on any topic
- client-communications: Tone, phrasing, and protocol for responding to client emails in your freelance business
- daily-briefing: Format and content for your agent’s morning summary
\n
\n
\n
\n
\n
\n
Related Guides
\n
- \n
- OpenClaw Beginner’s Guide
- OpenClaw Commands Reference
- OpenClaw for Small Business Owners
\n
\n
\n
\n\n
? Recommended: Automation Business Book | Productivity Desk Mat
Written by: Alex Torres, Editor at OpenClaw Resource
\n
Last Updated: May 2026
\n
Our Editorial Standards | How We Review Skills | Affiliate Disclosure
\n
Want to automate WordPress with OpenClaw? See our guide to setting up OpenClaw skills for WordPress automation →
Leave a Reply