Crap I couldn't find online, install with skills CLI.
Add -g to install globally (user-level, all projects) instead of into the current repo, and -y to skip the confirmation prompt.
| Skill | What it does |
|---|---|
clean-comments |
Deletes redundant and jargony comments from code you just wrote. Keeps the ones carrying information the code can't. |
Collected while working this out, because none of it was in one place online.
A skill is a directory, not a file. skills/<name>/SKILL.md. The directory name has to match the name in the frontmatter or it won't resolve.
Two required frontmatter fields: name and description. Nothing else is mandatory.
name: 1–64 chars, lowercase letters, numbers and hyphens. No leading, trailing, or consecutive hyphens.description: this is the entire trigger surface. The agent decides whether to load the skill from this line alone, so write it as when to use this, not just what it is. Include the phrasings someone would actually type.
The CLI only scans certain paths, to depth 2. Repo root (if it has a SKILL.md), then skills/, skills/.curated/, skills/.experimental/, skills/.system/, and agent dirs like .claude/skills/. Both skills/<name>/ and skills/<category>/<name>/ work. Anything outside those needs --full-depth at install time, so just use skills/.
One repo holds many skills. The @name suffix on the install command picks one out. Drop the suffix to get all of them.
There is no registry to submit to. No PR, no approval, no minimum stars, no license requirement. A public GitHub repo is the publish step. Listing on skills.sh happens on its own — the directory and leaderboard are built from anonymous telemetry when people run npx skills add, so a brand-new skill won't appear until it gets installed.
Converting a Claude Code slash command into a skill: $ARGUMENTS does not get substituted in a skill body. It stays there as literal text. Replace it with a plain instruction telling the agent to honor whatever the user passed at invocation.
Also worth knowing: npx skills init <name> scaffolds the template. There's no validate or lint command — nothing checks your frontmatter before someone installs it.