skill-creator

Create Claude skills with SKILL.md YAML frontmatter under ~/.claude/skills/.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/Z5Jonathan-maker/ai-coding-os --skill skill-creator-z5jonathan-maker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-creator
Source: https://github.com/Z5Jonathan-maker/ai-coding-os/tree/main/claude/skills/skill-creator
Command: npx skills add https://github.com/Z5Jonathan-maker/ai-coding-os --skill skill-creator-z5jonathan-maker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Skill-creator helps you define, structure, and document a new Claude-style skill so it can be discovered and used reliably instead of being a vague set of instructions.

Core Features & Use Cases

  • Guided skill definition: Helps you specify what the skill does, when it should trigger, and which tools it needs so the outcome is clear and actionable.
  • Correct folder + entry-point setup: Creates the expected kebab-case folder under ~/.claude/skills/ and ensures SKILL.md exists at the root with required YAML frontmatter.
  • Clean operational instructions: Produces focused markdown instructions for the skill’s runtime behavior, while directing deeper documentation to references/ when needed.
  • Use case: When you want a reusable assistant capability (e.g., “summarize meeting notes into product requirements”) that you can refine over time without rewriting everything in chat.

Quick Start

Tell the AI what the skill should do, when it should trigger, and any tools it needs, and ask it to generate the correct ~/.claude/skills/<skill-name> folder plus a valid SKILL.md.

Frequently Asked Questions about skill-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a reusable Claude skill with YAML frontmatter?

To create a reusable skill, generate a kebab-case folder under ~/.claude/skills/ and add a root SKILL.md file with required YAML frontmatter specifying the name and description, plus operational instructions defining triggers and behavior.

What's the best way to structure markdown instructions for workflow authoring?

Workflow authoring requires focused markdown instructions in the root SKILL.md for runtime behavior, while deeper documentation should be directed to a references/ subfolder to keep the entry point clean and actionable.

When do I need to add scripts, references, or assets folders to a local skill?

You should add scripts/, references/, or assets/ folders to a local skill only when the operational instructions require external tooling, supplementary documentation, or static files to execute the triggered capability successfully.

How does trigger design work when building local skills?

Trigger design involves specifying clear conditions in the SKILL.md description so the assistant knows exactly when to activate the capability, ensuring reliable discovery and execution without overlapping with unrelated chat instructions.

Can I modify an existing SKILL.md entry point without rewriting the whole folder?

Yes, you can modify an existing SKILL.md entry point to refine trigger conditions or operational instructions incrementally, allowing you to optimize the capability over time without rewriting the entire folder structure.

Why should I use kebab-case naming for skill folders?

Kebab-case naming ensures consistent discovery and parsing of skill folders under ~/.claude/skills/, preventing path resolution errors and maintaining a standardized structure for reusable triggered capabilities.