How do I install the New Skill skill?

Run npx skillmds add majiayu000/new-skill-3 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 New Skill safe to use?

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

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

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

Who published New Skill?

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

New Skill by majiayu000 — Agent Skill

Name: New Skill
Rating: 4.666666666666667 (3 reviews)
Author: majiayu000

File contents

New Skill Scaffolder

Create a new skill in the kungfu repository with the correct structure and conventions.

Usage

When the user asks to create a new skill, follow these steps in order.

Step 1: Gather Info

Ask the user for:

Skill name (kebab-case, e.g. my-new-skill)
Description (single line, no newlines, max 1024 chars)
Subdirectories needed (references/, scripts/, examples/, templates/, assets/ -- all optional)

Step 2: Create Directory and SKILL.md

mkdir -p skills/<skill-name>

Write skills/<skill-name>/SKILL.md with this template:

---
name: <skill-name>
description: <single-line description>
license: MIT
---

# <Skill Title>

<Brief overview of what the skill does and when to use it.>

Step 3: Create Requested Subdirectories

If the user wants references/, scripts/, etc., create them with a .gitkeep:

mkdir -p skills/<skill-name>/references
touch skills/<skill-name>/references/.gitkeep

Step 4: Add Plugin Symlink

Create a symlink in the business plugin so the skill is discoverable:

ln -s ../../../skills/<skill-name> plugins/business/skills/<skill-name>

Step 5: Validate

Run validation to confirm everything is correct:

just validate

Fix any issues reported before continuing.

Step 6: Update README Table

just readme-table --write

Conventions

Name: Must be kebab-case, must match the directory name exactly
Description: Single line, no \n or \r, no YAML block scalars (|, >)
Orphan rule: Every file in subdirectories must be referenced from SKILL.md via markdown link or backtick
Word count: Keep under 1500 words
Sources: Use [Title](url) markdown link format

---name: new-skill-3description: Scaffold a new skill with correct directory structure, frontmatter, naming, plugin symlink, and validation--- # New Skill Scaffolder Create a new skill in the kungfu repository with the correct structure and conventions. ## Usage When the user asks to create a new skill, follow these steps in order. ### Step 1: Gather Info Ask the user for: - **Skill name** (kebab-case, e.g. `my-new-skill`) - **Description** (single line, no newlines, max 1024 chars) - **Subdirectories needed** (`references/`, `scripts/`, `examples/`, `templates/`, `assets/` -- all optional) ### Step 2: Create Directory and SKILL.md ```bash mkdir -p skills/<skill-name> ``` Write `skills/<skill-name>/SKILL.md` with this template: ```markdown --- name: <skill-name> description: <single-line description> license: MIT --- # <Skill Title> <Brief overview of what the skill does and when to use it.> ``` ### Step 3: Create Requested Subdirectories If the user wants `references/`, `scripts/`, etc., create them with a `.gitkeep`: ```bash mkdir -p skills/<skill-name>/references touch skills/<skill-name>/references/.gitkeep ``` ### Step 4: Add Plugin Symlink Create a symlink in the business plugin so the skill is discoverable: ```bash ln -s ../../../skills/<skill-name> plugins/business/skills/<skill-name> ``` ### Step 5: Validate Run validation to confirm everything is correct: ```bash just validate ``` Fix any issues reported before continuing. ### Step 6: Update README Table ```bash just readme-table --write ``` ## Conventions - **Name**: Must be kebab-case, must match the directory name exactly - **Description**: Single line, no `\n` or `\r`, no YAML block scalars (`|`, `>`) - **Orphan rule**: Every file in subdirectories must be referenced from SKILL.md via markdown link or backtick - **Word count**: Keep under 1500 words - **Sources**: Use `[Title](url)` markdown link format

Frequently asked questions