standardharness Creating a skill
A skill is a folder with a SKILL.md. Only name and description sit in the
catalog; the body loads on demand. Write the description as the trigger.
Capture first
Pull the workflow from the conversation before asking. Corrections the user made along the way are the most valuable lines — they are what a fresh session would get wrong.
Confirm in one or two sentences, then write.
Where it lives
| Location | Scope |
|---|---|
.harness/skills/<name>/SKILL.md |
this project |
~/.harness/skills/<name>/SKILL.md |
this user, every project |
A single <name>.md file is also valid. Project shadows personal.
File
---
name: run-migrations
description: Apply or roll back database migrations in this repo, and when to reach for it.
---
# Run migrations
1. ...
description must say when to use it and when not to. Unknown frontmatter is
ignored.
Test
Ask the user two prompts: one that should load the skill, one that should not. If the catalog line would fire on the second, tighten the description.