How do I install the Add Skill skill?

Run npx skillmds@latest add prostdev/add-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 Add Skill safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Add 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 Add Skill free to use?

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

Who published Add Skill?

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

Add Skill by prostdev — Agent Skill

Name: Add Skill
Author: ProstDev

Add Skill

Add a new skill to this marketplace repo the complete way — write an agnostic SKILL.md, place it in the right plugin, bump that plugin's version, and update the CHANGELOG and README. Use when adding a skill here, or turning an issue/idea into a shipped skill.

ProstDev 3705ddb 2.3 KB Updated Sep 17, 2026

File contents

Add a skill (to this repo)

Adding a skill is four coupled edits. Skip any and installs drift: a skill with no version bump never reaches managed /plugin users; one missing from the README/CHANGELOG is invisible.

1. Write the SKILL.md — and make it agnostic

Path: plugins/<plugin>/skills/<kebab-name>/SKILL.md. Follow the writing-skills skill for craft (frontmatter name + description; keep the body concise, ≤500 lines).
Genericize — this is the point of a public marketplace. These ship into strangers' repos. Strip anything from the source project: app/repo/product names, sibling-skill names that don't exist here, absolute paths, and stack specifics (Vitest, Prisma, TZ=UTC, .next/types). Replace with the general shape ("the repo's type-checker", "any multi-environment test matrix").
Cross-references to sibling skills in this repo are fine — verify the name actually exists.
model: haiku/sonnet only if the skill is mechanical AND terminal; judgment-heavy skills inherit.

2. Pick the plugin

content = blog/technical writing · dev = code, git, QA, session wrap-up · general = session-wide, codebase-agnostic helpers. Unsure between two? Ask the user — don't guess.

3. Bump that plugin's version

Edit plugins/<plugin>/.claude-plugin/plugin.json: SemVer, new skill → minor (0.1.0→0.2.0), fix/wording → patch. Only the plugin you touched bumps. marketplace.json carries no versions — but update its plugin description if the plugin's scope widened.

4. CHANGELOG + README

CHANGELOG.md: add an ### Added bullet under a <plugin> <new-version> heading.
README.md: add a row to that plugin's skills table — [`name`](path/SKILL.md) | one-liner. Keep the table alphabetical.

Before done

Grep the new SKILL.md for leaked source-project names/paths — expect none.
Confirm: file written, plugin bumped, CHANGELOG entry, README row. Don't commit or push unless asked.

---name: add-skilldescription: Add a new skill to this marketplace repo the complete way — write an agnostic SKILL.md, place it in the right plugin, bump that plugin's version, and update the CHANGELOG and README. Use when adding a skill here, or turning an issue/idea into a shipped skill.---# Add a skill (to this repo)Adding a skill is four coupled edits. Skip any and installs drift: a skill with no version bumpnever reaches managed `/plugin` users; one missing from the README/CHANGELOG is invisible.## 1. Write the SKILL.md — and make it agnostic- Path: `plugins/<plugin>/skills/<kebab-name>/SKILL.md`. Follow the `writing-skills` skill for craft (frontmatter `name` + `description`; keep the body concise, ≤500 lines).- **Genericize — this is the point of a public marketplace.** These ship into strangers' repos. Strip anything from the source project: app/repo/product names, sibling-skill names that don't exist here, absolute paths, and stack specifics (`Vitest`, `Prisma`, `TZ=UTC`, `.next/types`). Replace with the general shape ("the repo's type-checker", "any multi-environment test matrix").- Cross-references to **sibling skills in this repo** are fine — verify the name actually exists.- `model: haiku`/`sonnet` only if the skill is mechanical AND terminal; judgment-heavy skills inherit.## 2. Pick the plugin`content` = blog/technical writing · `dev` = code, git, QA, session wrap-up · `general` =session-wide, codebase-agnostic helpers. Unsure between two? **Ask the user** — don't guess.## 3. Bump that plugin's versionEdit `plugins/<plugin>/.claude-plugin/plugin.json`: SemVer, new skill → **minor** (`0.1.0`→`0.2.0`),fix/wording → **patch**. Only the plugin you touched bumps. `marketplace.json` carries no versions —but update its plugin `description` if the plugin's scope widened.## 4. CHANGELOG + README- `CHANGELOG.md`: add an `### Added` bullet under a `<plugin> <new-version>` heading.- `README.md`: add a row to that plugin's skills table — `[`\``name`\``](path/SKILL.md) | one-liner`. Keep the table alphabetical.## Before done- Grep the new SKILL.md for leaked source-project names/paths — expect none.- Confirm: file written, plugin bumped, CHANGELOG entry, README row. Don't commit or push unless asked.

Frequently asked questions