• OpenClaw skills are SKILL.md files with YAML frontmatter and markdown instructions. Install them from ClawHub (13,700+ available) or build your own.
• This list covers 16 across web scraping, productivity, development, communication, and more. Firecrawl CLI, Gog, and self-improving-agent lead the download counts.
• Security matters: a February 2026 audit flagged 341 malicious skills on ClawHub. Check author reputation and star counts, or use the Skill Vetter skill to scan before installing.
• The article walks through building a custom invoice generator skill and publishing it to the registry.

OpenClaw skills turn a general-purpose AI agent into a specialized one. The ClawHub registry now lists thousands of skills across categories like web scraping, DevOps, productivity, and image generation, with new ones published daily.

But quantity creates its own problem. Finding the right skills among thousands of options takes time you could spend building. This article covers the best OpenClaw skills worth installing today, organized by category, plus a walkthrough for creating and publishing your own.

An OpenClaw skill is a directory containing a SKILL.md file. That file has two parts: YAML frontmatter declaring metadata and a markdown body with the actual instructions. The frontmatter covers the basics (name, description, version) plus any requirements the skill needs to run. The body acts as a runbook: what to do, what inputs to collect, how to handle failures, and what format to return.

A trimmed SKILL.md frontmatter looks like this:

---
name: todoist-cli
description: Manage Todoist tasks from the command line.
version: 1.2.0
metadata:
  requires:
    env:
      - TODOIST_API_KEY
    bins:
      - todoist-cli
    install:
      node: todoist-cli
---
# Todoist CLI Skill
 
When the user asks to manage tasks, use the `todoist-cli` binary...

The metadata block declares what the skill needs: environment variables, binaries, and install commands for npm, Homebrew, or uv. OpenClaw checks these at load time and warns you if anything is missing.

The ClawHub registry is where most skills live. As of February 2026, it hosts 13,729 skills published by individual developers and companies. The VoltAgent community maintains a curated awesome list of 5,494 vetted skills from that pool.

Instead of writing the same agent instructions from scratch each time, you install a skill someone already tested and refined.

The fastest way to install a skill is through the ClawHub CLI:

npx clawhub@latest install <skill-slug>

You can also search the registry from your terminal with clawhub search "web scraping" to browse what is available. To install a skill manually, copy its folder into ~/.openclaw/skills/ for global access or <project>/skills/ to scope it to a single workspace.

After installing, run openclaw skills list --eligible to confirm OpenClaw detects the skill. Use openclaw skills info <skill-name> to inspect its metadata and requirements.

Not everything on ClawHub is safe to install. A February 2026 audit reviewed 2,857 skills and flagged 341 as malicious. Of those, 335 were distributing the AMOS macOS stealer. Always check a skill's author reputation, version history, and star count before installing.

We picked these 16 based on download counts from ClawHub, star ratings, author reputation, and whether the skill fills a gap that OpenClaw's built-in tools leave open.

OpenClaw's built-in web_fetch tool breaks on JavaScript-heavy pages and bot-protected sites. Firecrawl handles both and returns clean markdown ready for LLM context across six commands: search, scrape, crawl, map, browser, and credit-usage.

Install it with a single command:

npx -y firecrawl-cli init --browser --all

The --browser flag adds the Browser Sandbox, providing remote browser sessions without a local Chromium install. Multiple concurrent sessions run in isolated sandboxes, so your agent can fill forms, click through multi-step flows, and scrape the results.

For a deeper look at the search command, see the OpenClaw web search guide. The full Firecrawl integration guide covers setup and advanced use cases, and the CLI reference docs have the complete command list.

Instead of installing six separate Google Workspace integrations, Gog bundles Gmail, Calendar, Drive, Docs, Sheets, and Contacts into one skill. "Send the Q3 report to Sarah and add a follow-up meeting for Thursday at 2pm" becomes one sentence instead of two apps.

The highest-starred skill on ClawHub (338 stars), self-improving-agent captures corrections and learnings across sessions in structured Markdown files. Fix a mistake once and the agent writes it down; learnings that recur three or more times within 30 days get promoted to permanent project memory.

Where self-improving-agent stores learnings as text, Ontology builds a typed knowledge graph with structured relationships. "This contact works at that company, which is a client on this project." Your agent can traverse those connections later to answer questions that depend on how entities relate to each other.

Point it at a 45-minute conference talk, a research PDF, a long article, local audio files, or a YouTube video and get a condensed version back. The CLI tool handles the full extraction-to-summarization pipeline, including fallback to Firecrawl for blocked sites and transcript extraction for video content.

Connects to the full Notion API for pages, databases, blocks, and comments. Setup requires a Notion integration token, and the skill handles pagination internally: ask for "all tasks in the Q1 roadmap database" and you get a flat list.

The local-first counterpart to Notion. Plain markdown, no cloud, no account. It searches your vault, creates notes, and manages links between them.

"Check if any CI runs failed overnight and summarize the errors." The Github skill wraps the gh CLI with agent-friendly patterns for triaging issues, reviewing PRs, and debugging CI failures. No new permissions needed; it teaches your agent the right commands instead of letting it hallucinate flags.

If your agents call third-party APIs, API Gateway (47 published versions) handles the OAuth plumbing. Token refresh for over 100 services including Stripe, Salesforce, and HubSpot runs without you wiring up auth flows manually.

Configuring MCP servers by hand means editing JSON files, managing auth tokens, and restarting processes. Mcporter turns that into agent-directed commands: discover available servers, inspect tool schemas, run calls, and handle OAuth flows from inside OpenClaw.

Not everyone uses Gmail. Himalaya provides IMAP/SMTP email for Outlook, ProtonMail, custom domains, or any provider supporting standard protocols.

Handles messages, reactions, pins, and files within a workspace. Configurable threading gives three reply modes (off, first message only, or every message), and the agent can fetch recent channel history to summarize what it missed.

@steipete, the creator of OpenClaw, maintains five macOS skills: Mail, Calendar, Reminders, Notes, and Shortcuts. Each one taps into Apple's native APIs with zero configuration and no API keys. If you have built any Apple Shortcuts automations, the Shortcuts skill makes all of them available to your agent.

Image generation without an OpenAI dependency. Runs on Google's Gemini 3 Pro Image API and handles both text-to-image generation and image-to-image editing, where you provide a source image plus instructions like "make the sky more dramatic."

Local speech-to-text where no audio leaves your machine. No API key, no cloud upload. Outputs plain text or SRT subtitles from MP3 and M4A input.

Before installing a skill from an unfamiliar author, run it through Skill Vetter first. It checks for undeclared environment variable access, hidden network calls, and obfuscated shell commands.

If nothing on ClawHub fits your workflow, building a custom skill takes a directory, a SKILL.md file, and optionally a supporting script. Claude Code uses the same SKILL.md format — if you're building for Claude Code rather than OpenClaw, the Claude Code skill tutorial covers the full workflow with a web scraping example. This walkthrough builds an invoice generator that collects billing details from the user and outputs a formatted PDF.

The folder name becomes the skill's slug on ClawHub, so it needs to follow the registry's naming rules: lowercase letters, numbers, and hyphens only, starting with a letter or number.

mkdir invoice-gen && cd invoice-gen

A skill needs at minimum a SKILL.md. This one also includes a Python script for PDF templating, so the final structure is:

invoice-gen/
├── SKILL.md
└── generate_invoice.py

The frontmatter declares runtime dependencies. Since the "What are OpenClaw skills?" section earlier covered the full frontmatter spec, this example just needs python3 on PATH and reportlab installed via uv:

---
name: invoice-gen
description: >
  Generate PDF invoices from client details, line items,
  hours, and rates. Use when the user asks to create,
  generate, or make an invoice.
version: 1.0.0
metadata:
  openclaw:
    requires:
      bins:
        - python3
    install:
      uv: reportlab
---

The description field is how OpenClaw decides which skill to activate when dozens are loaded at once. "Generate PDF invoices from client details, line items, hours, and rates" beats a vague "Helps with invoices" because it gives the agent specific phrases to match against user requests.

The instruction body tells the agent what to collect and how to run the script. {baseDir} resolves to the skill's install directory at runtime:

# Invoice Generator
 
## Inputs
 
Collect these from the user before generating. Ask for any missing.
 
- **client**: Company or individual name
- **items**: One or more line items, each with a description,
  hours worked, and hourly rate
- **output**: Where to save the PDF
  (default: `./invoice-{client}-{date}.pdf`)
 
## Workflow
 
1. Collect all inputs. If the user gives a single item without
   an hours/rate breakdown, ask for clarification.
2. Format items as a JSON array:
   `[{"description": "...", "hours": N, "rate": N}]`
3. Run the generation script:
   python3 {baseDir}/generate_invoice.py \
    --client "CLIENT_NAME" \
    --items 'JSON_ARRAY' \
    --output "OUTPUT_PATH"
4. Confirm the file path and total amount to the user.
 
## Error handling
 
- If `reportlab` is missing, run `uv pip install reportlab`
  and retry.
- If the output directory doesn't exist, create it first.

The workflow steps are numbered and specific for a reason. Vague instructions like "generate an invoice" leave the agent guessing at implementation; exact commands with placeholder values give it a fill-in-the-blanks template. The error handling covers the two likeliest failures rather than trying to anticipate every edge case.

Without a dedicated script, the agent would build invoice layouts from scratch each time, producing inconsistent formatting. The generate_invoice.py script uses reportlab to render a formatted PDF with invoice metadata, a line items table, tax calculation, and totals. The full script is too long to inline here, but it takes three CLI arguments (--client, --items as a JSON array, --output) and produces a clean, professional-looking PDF. Download it into your skill directory to follow along.

Copy the skill to your local skills folder and check that OpenClaw detects it:

cp -r invoice-gen ~/.openclaw/skills/
openclaw skills list --eligible
openclaw skills info invoice-gen

If invoice-gen shows up in the eligible list, the requirements are met and the frontmatter parsed correctly. OpenClaw's file watcher picks up changes to SKILL.md within 250ms, so you can edit the instructions and test again without restarting your agent session.

Install the ClawHub CLI and log in with your GitHub account (must be at least one week old):

npm i -g clawhub
clawhub login

Publish the skill with a version tag and changelog:

clawhub publish ./invoice-gen \
  --slug invoice-gen \
  --version 1.0.0 \
  --changelog "Initial release with PDF generation and multi-item support"

ClawHub runs VirusTotal scans on every published skill automatically. Your declared metadata (binaries, environment variables) must match what the code actually uses. If the script references an env var or binary that the frontmatter doesn't declare, the scan flags a metadata mismatch and blocks the publish.

To push updates later, edit your files and re-publish with a bumped version:

clawhub publish ./invoice-gen \
  --slug invoice-gen \
  --version 1.1.0 \
  --changelog "Added multi-currency support"

Or use clawhub sync --bump patch to auto-increment the version across all your published skills at once.

Start with Firecrawl CLI for web scraping and browser automation, Gog for Google Workspace, and self-improving-agent for persistent memory across sessions. Browse the full list of OpenClaw skills on ClawHub or the VoltAgent awesome list.

For anything the registry doesn't have yet, build a custom skill and publish it. The full cycle from mkdir to clawhub publish takes a few minutes.