Cédric Rittié

/skill:create

Skill Creator

MetaBeginner2 min install68 lines

Guides the creation of a new Skill in 4 steps: name (category:name), description (what triggers it), allowed tools, main content. Handles colons in folder names (which mkdir doesn't always like). Auto-symlinks to ~/.claude/skills/ if you store Skills in an Obsidian vault.

Published April 15, 2026Updated April 16, 2026
GitHub
Who it's for

Anyone who re-explained the same method to Claude 3 times this week and wants to capitalize. That said: if you only use Claude Code for one-shots, Skills won't help — they're for capitalizing on methods you reuse.

Configuration

Name
skill:create
Category
Meta
Description
Creates a new Claude Code skill. Handles folder creation (with colons in names), SKILL.md structure, and conventions.
Allowed tools
BashWriteRead

Installation

One line, one terminal
$ mkdir -p ~/.claude/skills/skill:create && \
  curl -sSL https://www.cedricrittie.com/api/skills/skill-create/raw \
       -o ~/.claude/skills/skill:create/SKILL.md

Then restart Claude Code. Test with `/skill:create`.

Need to install Claude Code first? See the Claude Code page · Download the raw .md

Usage examples

›/skill:create

Interactive mode: asks questions one by one (name, trigger, tools, content), then creates the file and verifies.

Sample output
Let's create a new Skill.

1. Name (format: category:name)
> coach:prep

2. Short description (what triggers it?)
> Prepares a brief for a client meeting based on past notes

3. Allowed tools (comma-separated, or "auto")
> Read, Write, WebSearch

4. Main instructions
> (paste content here)

Created: ~/Documents/YourVault/Context/Skills/coach:prep/SKILL.md
Symlinked: ~/.claude/skills/coach:prep → vault
Restart Claude Code. Test with /coach:prep
›/skill:create coach:prep - Prépare un brief avant RDV

One-shot mode: name + description as args, Skill scaffolds the file with standard sections and lets you fill in.

Sample output
Created skeleton at ~/Documents/YourVault/Context/Skills/coach:prep/SKILL.md

Scaffold contains:
- Frontmatter (description, allowed-tools)
- # Title section
- ## When to use
- ## Workflow
- ## Output format

Open the file to complete the instructions. Then:
ln -s ~/Documents/YourVault/Context/Skills/coach:prep ~/.claude/skills/coach:prep

Full SKILL.md

Why is the Skill written in English? LLMs are trained mostly on English. A system prompt in English gives more reliable, more precise results, even when Claude replies to you in French. The output the Skill produces (your posts, audits, digests) comes out in whatever language you use. Only the system instructions stay in English, by design for performance.

Skill Creator

Create a new Claude Code skill following standard conventions.

Process

  1. Ask the user:

    • Name: in category:name format (e.g. coach:call, product:prd, ops:deploy)
    • Purpose: what should this skill do? (1-2 sentences is enough)
    • Allowed tools: which tools can the skill use without asking permission? (default: Read, Write)

  2. Create the skill folder and file:

    • Path: ~/Documents/YourVault/Context/Skills/{category:name}/SKILL.md (or wherever the user stores skills)
    • MUST use terminal (Bash/mkdir/Write) because some editors (like Obsidian) cannot create folders with : in the name
    • The folder will be visible and editable in the editor once created

  3. Write the SKILL.md following this template:

---
description: [One clear sentence. Start with a verb. Explain WHEN to trigger this skill.]
allowed-tools: [Comma-separated list of tools]
---

# [Skill title]

[Core instructions for Claude when this skill is invoked.]

## [Sections as needed]

[Keep instructions precise and actionable. No filler.]

Conventions

  • Language: all skill files are written in English (instructions, frontmatter, comments)
  • Folder naming: category:name using colons — MUST be created via terminal, not via editors that block colons
  • Description field: starts with a verb, explains when to trigger, one sentence
  • Tone of instructions: direct, imperative, no fluff
  • Location: your skills folder (typically symlinked to ~/.claude/skills/)
  • After creation: the skill is immediately available as a slash command /category:name in Claude Code

Categories already in use

Check existing skills before creating:

ls ~/.claude/skills/

Common categories:

  • writing: — text writing, editing, coaching
  • product: — product management, PRDs, analysis
  • coach: — structured thinking, calls, feedback
  • ops: — infrastructure, server, deployment
  • obsidian: — vault operations, notes, templates

What NOT to do

  • Never create the folder from an editor that forbids colons in folder names
  • Never use a language other than English in the SKILL.md content
  • Never skip the frontmatter (description + allowed-tools are required)
  • Never create a skill without confirming name and purpose with the user first

Public version of this Skill. 68 lines. Copy into ~/.claude/skills/skill:create/SKILL.md to install.

Read related article →