How do I install the Create Skill skill?

Run npx skillmds@latest add vitoabella/create-skill in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Create Skill safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: CAUTION, Skill Scanner: PASS. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Create Skill?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Create Skill free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Create Skill?

vitoabella (@vitoabella) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Create Skill by vitoabella — Agent Skill

Name: Create Skill
Rating: 4.2 (5 reviews)
Author: vitoabella

File contents

create-skill

Create the skill with skillkit add. Do not invent a folder layout and do not copy the skill into an IDE directory.

Confirm before writing

Ask for anything the user has not already settled:

Name. 1-64 characters. Lowercase letters, numbers, and single hyphens. It must not start or end with a hyphen. The folder name will match.
Description. What the skill does and when to use it. This is the slash-menu label and, if the skill is later set to auto, the only text the model sees before it opens the file. The Agent Skills spec allows at most 1024 characters. The procedure itself belongs in the body, not in this field.
Category. A folder under the root, such as school or github. Use one level unless the user asks for nested folders.
Phases. If the procedure has separable parts, list a short hyphenated name for each phase. If it is one procedure, do not add modules.

Default root is custom/, which is gitignored so personal skills stay out of the kit repository. Use --root shared only when the user says the skill should ship with the kit.

Write it

One phase:

skillkit add --name NAME --description "DESCRIPTION" --category CATEGORY

Several phases:

skillkit add --name NAME --description "DESCRIPTION" --category CATEGORY --phase PHASE --phase PHASE

Then edit SKILL.md so each Read modules/<phase>.md when ... line states the real condition for that phase. Fill each module with the steps for that phase. Put long reference material in references/ and executable helpers in scripts/, and mention those files from the module that needs them.

The new skill stays in library state: on disk, not in the slash menu. Enable it only if the user asks:

skillkit enable NAME manual

manual is the usual choice. Use auto only when the user wants the model to select the skill without /NAME.

If add fails

custom is not an active root: skills.config.local.yaml does not list custom under roots. Say so. Offer --root shared only for a skill meant for every clone.
The name fails the pattern: show the rule and ask for another name.
The description is longer than 1024 characters: shorten the trigger text and keep the procedure in the body.

---name: create-skilldescription: Create a new skill from the kit skeleton. Use when the user asks to add, author, or scaffold a skill.---# create-skillCreate the skill with `skillkit add`. Do not invent a folder layout and do not copy the skill into an IDE directory.## Confirm before writingAsk for anything the user has not already settled:1. **Name.** 1-64 characters. Lowercase letters, numbers, and single hyphens. It must not start or end with a hyphen. The folder name will match.2. **Description.** What the skill does and when to use it. This is the slash-menu label and, if the skill is later set to auto, the only text the model sees before it opens the file. The Agent Skills spec allows at most 1024 characters. The procedure itself belongs in the body, not in this field.3. **Category.** A folder under the root, such as `school` or `github`. Use one level unless the user asks for nested folders.4. **Phases.** If the procedure has separable parts, list a short hyphenated name for each phase. If it is one procedure, do not add modules.Default root is `custom/`, which is gitignored so personal skills stay out of the kit repository. Use `--root shared` only when the user says the skill should ship with the kit.## Write itOne phase:```textskillkit add --name NAME --description "DESCRIPTION" --category CATEGORY```Several phases:```textskillkit add --name NAME --description "DESCRIPTION" --category CATEGORY --phase PHASE --phase PHASE```Then edit `SKILL.md` so each `Read modules/<phase>.md when ...` line states the real condition for that phase. Fill each module with the steps for that phase. Put long reference material in `references/` and executable helpers in `scripts/`, and mention those files from the module that needs them.The new skill stays in **library** state: on disk, not in the slash menu. Enable it only if the user asks:```textskillkit enable NAME manual````manual` is the usual choice. Use `auto` only when the user wants the model to select the skill without `/NAME`.## If add fails- `custom` is not an active root: `skills.config.local.yaml` does not list `custom` under `roots`. Say so. Offer `--root shared` only for a skill meant for every clone.- The name fails the pattern: show the rule and ask for another name.- The description is longer than 1024 characters: shorten the trigger text and keep the procedure in the body.

Frequently asked questions

Create Skill