ops-skill-creator

Extends the built-in skill-creator with our workspace conventions. Always read the built-in skill-creator SKILL.md first (/opt/homebrew/lib/node_modules/openclaw/skills/skill-creator/SKILL.md) for base spec (frontmatter, directory layout, progressive disclosure, packaging). This skill adds our naming, publishing, and registry rules on top.

Naming Convention

Prefix categories (kebab-case, directory name = frontmatter name):

Prefix	Category	Examples
ops-	Tooling & operations	ops-browser, ops-docx-gen, ops-llm-usage
mem-	Memory management	mem-runbook, mem-baseline
agents-	Agent orchestration	agents-coder, agents-research
model-	Model management	model-escalation, model-routing

Rules:

1. Directory name must equal frontmatter name field
2. All lowercase, hyphens only, prefix required
3. Under 64 characters

Workflow: Create a New Skill

1. Pick prefix — determine which category (ops/mem/agents/model)
2. Name — {prefix}-{verb-noun} style, e.g. ops-pdf-rotate
3. Scaffold — create directory under ~/.openclaw/workspace/skills/{name}/
4. Write SKILL.md — follow built-in skill-creator spec (frontmatter, body, progressive disclosure)
5. Validate — run the check in Validation below
6. Update registry — append to TOOLS.md Skill 命名规范 table
7. Commit — git add skills/{name} TOOLS.md && git commit

Workflow: Publish to GitHub

1. Repo name: {skill-name} (e.g. ops-pdf-rotate)
2. Org: catgodtwno1
3. Create:

   gh repo create catgodtwno1/openclaw-{skill-name} --public --source=skills/{skill-name} --push

4. Update TOOLS.md — fill in the GitHub column: catgodtwno1/openclaw-{skill-name}
5. Commit registry update

Workflow: Audit Existing Skills

Run validation across all skills:

for f in ~/.openclaw/workspace/skills/*/SKILL.md; do
  dir=$(basename $(dirname "$f"))
  name=$(grep "^name:" "$f" | head -1 | sed 's/name: *//')
  # Check dir == name
  [ "$dir" != "$name" ] && echo "❌ MISMATCH: dir=$dir name=$name"
  # Check prefix
  echo "$dir" | grep -qE '^(ops|mem|agents|model)-' || echo "⚠️  NO PREFIX: $dir"
done

Check TOOLS.md registry is in sync with actual skills/ directories.

Validation

Before committing any new or renamed skill:

dir="{skill-name}"
name=$(grep "^name:" skills/$dir/SKILL.md | head -1 | sed 's/name: *//')
# 1. dir == name
[ "$dir" = "$name" ] && echo "✅ name match" || echo "❌ name mismatch"
# 2. has prefix
echo "$dir" | grep -qE '^(ops|mem|agents|model)-' && echo "✅ prefix ok" || echo "❌ missing prefix"
# 3. length
[ ${#dir} -lt 64 ] && echo "✅ length ok" || echo "❌ too long"

Current Registry

See TOOLS.md → Skill 命名规范 section for the authoritative list. Keep it updated after every create/rename/delete.