skill
The install line for the SKILL.md procedure attached to a verdict, and what it returns while none are published.
A verdict says what to pick. A skill says how to write the code once you have picked, at the version the reviewer tested. skill looks one up by slug and returns its install command.
Arguments
| Name | Type | Limits | Required | Default |
|---|---|---|---|---|
slug | string | 1 to 120 characters | yes | none |
The lookup is an exact match on the skill's own slug. It is not a search, and it is not the verdict slug unless the two happen to be the same string.
Request
{
"name": "skill",
"arguments": { "slug": "auth-nextjs-solo" }
}Response
A published skill answers in two lines:
SKILL <slug> v<version>
install: npx skills add <repo path>No skill is published today, so every slug currently returns the miss:
no skill "auth-nextjs-solo" yet. Browse https://wellworn.dev/skills
remaining: 51wellworn.dev/skills says the same thing, and it is the page to watch: the first batch ships with the verdicts the skills belong to, in WellWorn-dev/wellworn under skills/<slug>/SKILL.md.
Where a verdict does have a skill, its compact block carries a SKILL npx skills add … line, so recommend hands you the install command without a second call.
Limit and error lines
| Line | Cause |
|---|---|
no skill "…" yet. Browse https://wellworn.dev/skills | No row with that slug. |
MCP error -32602: Input validation error: … | slug missing, empty, or over 120 characters. |
limit reached: … | The window is spent. Limits. |
What to do with the answer
Run the install line, then read the file before you follow it: a skill is a procedure a person wrote against one version, and the version it was written for is in the verdict it belongs to. Until skills are published, the PICK reason and the TRAPS rows in a verdict block are the procedure.