Skip to content
Skills Library
AI & agents · Writing

create-skill

/create-skill

Writes a new skill or improves an existing one, as a SKILL.md with frontmatter and step-by-step instructions, then loads it to check it. Use when the user asks to make, write, save or fix a skill, turn a procedure into a skill or slash command, or says "remember how to do this".

Licence
MIT
Last repository change
12.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 12.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Writes a new skill or improves an existing one, as a SKILL.md with frontmatter and step-by-step instructions, then loads it to check it. Use when the user asks to make, write, save or fix a skill, turn a procedure into a skill or slash command, or says "remember how to do this".

Triggers from the description

remember how to do this

Arguments

/create-skill <what the skill should do>
Original author description

Writes a new skill or improves an existing one, as a SKILL.md with frontmatter and step-by-step instructions, then loads it to check it. Use when the user asks to make, write, save or fix a skill, turn a procedure into a skill or slash command, or says "remember how to do this".

How it works

  1. 1. Find out what the skill is for
  2. 2. Choose where it lives
  3. 3. Pick the name
  4. 4. Write the description
  5. 5. Write SKILL.md
  6. 6. Write the files
  7. 7. Verify
  8. 8. Finish
Original SKILL.md headings · 58 lines, 711 words
SKILL.md preview
---
name: create-skill
description: Writes a new skill or improves an existing one, as a SKILL.md with frontmatter and step-by-step instructions, then loads it to check it. Use when the user asks to make, write, save or fix a skill, turn a procedure into a skill or slash command, or says "remember how to do this".
argument-hint: <what the skill should do>
---
A skill is a folder `<name>/SKILL.md`: YAML frontmatter, then instructions in Markdown, plus any files beside it. `format.md` in this skill's folder has the exact rules and every problem message; read it when a rule below is not enough.

## 1. Find out what the skill is for
- Take the job from the user's words, the conversation, or `$ARGUMENTS`. If the procedure was just done in this session, use the steps that actually worked.
- Settle two things before writing: what the skill does, and when it should trigger (the phrases a user would say). Ask the user only if you cannot infer either one.
- Keep it to one job. If the request holds two, write two skills.
- To change an existing skill, load it with the `skill` tool first; the result gives its folder.

## 2. Choose where it lives
- Default: the project, `<project>/.silo-harness/skills/<name>/`, where `<project>` is the session folder (or its git root when the skill is for the whole repository).
- The user's own, `~/.silo-harness/skills/<name>/`, when it is personal or useful across projects.
- Tell the user which one you chose and why, in one sentence.
- A project skill of the same name hides the user's and the built-in one; pick another name unless replacing it is the point.

## 3. Pick the name
- Lower-case letters, digits and single hyphens, at most 64 characters: `deploy-staging`, `release-notes`.
- A verb or a clear noun phrase. The folder name and `name:` must be the same.
- The user will type it as `/name`, so keep it short.

## 4. Write the description
One or two sentences, at most 1,024 characters, in the third person: what it does, then "Use when …" with the words a user would actually say. The model picks skills from this line alone.

- Good: `Drafts release notes from the commits since the last tag, grouped into New, Improved and Fixed. Use when the user asks for release notes, a changelog entry, or what changed since the last release.`
- Bad: `Release notes helper.` (no trigger, no outcome)

## 5. Write SKILL.md
```markdown
---
name: release-notes
description: Drafts release notes … Use when the user asks for …
argument-hint: <version>
---
1. Find the last tag with `git describe --tags --abbrev=0`.
2. …
```
- Add `argument-hint` when the skill takes input; use `$ARGUMENTS`, `$1`, `$2` in the body where it goes.
- Add `disable-model-invocation: true` only when the skill has side effects the user should start themselves (deploys, sending messages). Add `user-invocable: false` only for background knowledge nobody types.
- The body: numbered steps in the imperative, in working order, each one something you can check was done. Name exact commands, files and tools. Say what "done" looks like.
- No filler, no greetings, no restating the description. No secrets, keys, tokens or personal paths; read them from the environment or ask.
- Keep SKILL.md under about 200 lines. Put long reference material, templates and scripts in files beside it and refer to them by relative path (`see checklist.md`, `run scripts/check.sh`). Use `${SKILL_DIR}` when a command needs the absolute folder.

## 6. Write the files
- Create the folder and write `SKILL.md` and any supporting files.
- Make scripts executable (`chmod +x`) and run each once to see it works.

## 7. Verify
1. Load it: call the `skill` tool with the name. It re-reads the skill folders, so a new skill is found.
2. Read the result: the body must come back whole, the base directory must be the folder you chose, and the files list must show every supporting file.
3. If it lists problems, fix each one and load it again. Repeat until there are none.
4. If the tool says the skill is run by the user only, that is the `disable-model-invocation` you set; it still lists any problems.
5. Read the description once more as the model would: would a user's request for this job match it, and would unrelated requests not?

## 8. Finish
Tell the user, briefly:
- the skill's name and folder;
- how to run it: `/name` (with the argument hint, if any), or just ask for the job in their own words;
- that Settings → Skills lists it.
Files in this package (2)
  • SKILL.md 4 KB
  • format.md 4 KB

Versions

RepositoryScoreLicence
This page · BrandeisPatrick/silo-harness100MIT
mgiovani/cc-arsenal100MIT
zylos-ai/zylos-core100MIT
mthines/agent-skills100MIT
jongio/skills100MIT
fairladyz625/harness-anything100AGPL-3.0
coco-research/coco100MIT
builderio/agent-native100MIT
vanducng/skills100MIT

Database snapshot: 13.11.2026 · package version 5e838e12bc99 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100new-skill
    按本仓库约定创建新技能。先访谈用途、触发短语和工具需求,再从技能模板生成 `.codebuddy/skills/<name>/SKILL.md`,最后运行 `check-skill-integrity` 核验 frontmatter 与正文。用户说 "write a skill"、"scaffold a skill"、"create a new skill"、"I keep doing X, make it a skill"、"new slash command"、"turn this workflow into a…
  • 100skill-template
    Generate custom skill/command from template. Use when creating a new skill or slash command from scratch, or scaffolding a skill file with correct frontmatter.
  • 95make-skill
    Create a focused workspace Skill from reusable decisions, knowledge, templates, or workflows in the current conversation. Use for /make-skill with a focus argument and requests such as save this workflow or turn this into a skill; do not use for one-off summaries or ordinary file creation.
  • 100forge
    Use when the user says 'forge this', 'new skill', 'create enchantment', or wants to create a MemStack skill.
  • 80Command Development
    This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create command with file references", "interactive command", "use AskUserQuestion in…
  • 100slash-command-builder
    Use when creating, improving, or troubleshooting Claude Code slash commands. Expert guidance on command structure, arguments, frontmatter, tool permissions, and best practices for building effective custom commands.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.