Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Authoring MateClaw Skills
## Overview
A skill is a `SKILL.md` file — YAML frontmatter plus a markdown body of reusable instructions. There are two places a SKILL.md can live, and they have different creation paths:
1. **Builtin (in-repo):** `mateclaw-server/src/main/resources/skills/<name>/SKILL.md` — committed, shipped inside the server JAR. On every startup `BuiltinSkillSeedService` scans `classpath*:skills/*/SKILL.md`, parses each frontmatter, and upserts a row into `mate_skill` keyed by `name`. The SKILL.md is the single source of truth — no SQL seed entry is required.
2. **Custom (runtime):** created by an agent or user through the `skill_manage` tool. Stored as a `mate_skill` row with `skill_type=custom` and exported to the workspace at `~/.mateclaw/skills/<name>/`. Not committed; lives per-installation.
This skill covers both. Note that `skill_manage` does NOT write into the in-repo `skills/` tree — builtin skills are authored by writing the file directly and restarting.
## When to Use
- You're adding a reusable workflow that should ship with MateClaw → builtin.
- You're editing an existing builtin skill under `mateclaw-server/src/main/resources/skills/`.
…
The line at the top of this page pins the label v1.0.0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
GET https://markdownregistry.com/api/v1/artifacts/art_awsgq53csvti2vjm
GET https://markdownregistry.com/api/v1/resolve?ref=mateaix/mateclaw/skill-authoring
GET https://markdownregistry.com/api/v1/blob/f202d33f77791c99c5e8f0e8b84ebb0101a0bbf1120c9926ff82579a7294ca27
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
nyldn/claude-octopus · .claude/skills/skill-authoring/SKILL.md · Principles for writing skills that behave the same way every run — use when adding, editing, or reviewing a skill in…
nyldn/claude-octopus · skills/skill-authoring/SKILL.md · Principles for writing skills that behave the same way every run — use when adding, editing, or reviewing a skill in…
cbrock84/headcount · plugins/technology/skills/skill-authoring/SKILL.md · Writes and revises agent skills so they trigger at the right moments and give usable instruction when they do. Use this…
athola/claude-night-market · plugins/abstract/skills/skill-authoring/SKILL.md · Guide creating Claude Code skills with TDD and persuasion principles. Use for new skill development.
microsoft/github-copilot-for-azure · .github/skills/skill-authoring/SKILL.md · Guidelines for writing Agent Skills that comply with the agentskills.io specification. WHEN: "create a skill", "new…
