name: openclaw-skill-creator description: Create, improve, or evaluate OpenClaw skills (SKILL.md). Use when: (1) designing a new skill from scratch, (2) improving an existing skill's description for better triggering accuracy, (3) evaluating whether a skill description would trigger correctly, (4) reviewing the skill library for quality issues. NOT for: creating Claude Code / Codex skills (those use a different format), editing skill scripts/assets unrelated to skill design.

OpenClaw Skill Creator

A skill for creating and iteratively improving OpenClaw skills — inspired by Anthropic's skill-creator, adapted for the OpenClaw skill format.

OpenClaw Skill Architecture

Skills are directories containing a SKILL.md file and optional resources.

Custom skills (user-created) are typically placed in the OpenClaw workspace:

<workspace>/skills/<skill-name>/

Built-in skills ship with the OpenClaw installation.

Custom skills in the workspace take precedence over built-ins of the same name.

Minimal structure

<skill-name>/
├── SKILL.md          ← required
└── scripts/          ← optional, executable helpers

No packaging step needed. The directory is the skill.

SKILL.md format

---
name: skill-name
description: <trigger description — the most important field>
---

# Skill Name

Instructions for the agent...

Only name and description in frontmatter. No other fields.

Use {baseDir} in scripts/instructions to reference the skill's own directory:

python3 {baseDir}/scripts/my_script.py

Writing Descriptions (Most Critical Part)

The description field is the only triggering mechanism. The body is never read unless the skill triggers first.

Core principles

1. Be pushy: Agents tend to undertrigger skills. Make the description slightly aggressive — list specific contexts where this skill MUST be used.
2. Use when + NOT for: Explicit structure reduces both under-triggering and false positives.
3. Include trigger phrases: List common user phrasings. Include non-English phrases if the user communicates in other languages.
4. Describe context, not just function: "What the skill does AND when to use it."

Template

<what the skill does>. Use when: (1) <context 1>, (2) <context 2>, (3) phrases like "<example phrase>". NOT for: <anti-patterns>.

Example (before → after)

❌ Before: "Track work time per project with start/stop timers."

✅ After: "Track work time and generate productivity reports. Use this skill whenever the user wants to start/stop a timer, log time to a project, or generate a time report — including phrases like 'start timer', 'log my time', 'how long did I work this week'. NOT for: calendar scheduling, task management."

Skill Creation Process

1. Capture Intent