create-skill

Guides authoring of Cursor Agent Skills with SKILL.md structure and frontmatter.

Updated Oct 15, 2019
One-click install
npx skills add https://github.com/kkkaoru/dotfiles --skill create-skill-kkkaoru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/kkkaoru/dotfiles/tree/main/.cursor/skills-cursor/create-skill
Command: npx skills add https://github.com/kkkaoru/dotfiles --skill create-skill-kkkaoru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a well-structured Agent Skill requires knowing the SKILL.md format, frontmatter rules, description best practices, and directory conventions, which are easy to get wrong without guidance. ## Core Features & Use Cases - Structured Authoring Workflow: Walks through discovery, design, implementation, and verification phases when creating a new skill. - Format Standards: Defines required YAML frontmatter fields (name, description), storage locations (personal vs project), and the 500-line SKILL.md limit. - Writing Guidance: Provides description best practices, common patterns (templates, examples, workflows, feedback loops), and anti-patterns to avoid. - Use Case: When you want to teach the agent a repeatable workflow, such as reviewing PRs against team standards, use this skill to scaffold a properly formatted skill directory with an effective description. ## Quick Start Ask the agent to create a new Cursor skill for your workflow, describing its purpose, trigger scenarios, and whether it should be personal or project-scoped.

Frequently Asked Questions about create-skill

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

FAQPage Schema
How do I create a Cursor Agent Skill?

Create a directory containing a SKILL.md file with YAML frontmatter defining a name and description, followed by markdown instructions. Store it in ~/.cursor/skills/ for personal use or .cursor/skills/ for project sharing.

What should a skill description include for discovery?

Write the description in third person, covering both what the skill does and when to use it, with specific trigger terms. Keep it under 1024 characters and avoid vague phrases like "helps with documents".

Where should Cursor skills be stored?

Personal skills go in ~/.cursor/skills/skill-name/ and are available across projects, while project skills live in .cursor/skills/skill-name/ and are shared with the repository. Never create skills in ~/.cursor/skills-cursor/, which is reserved for built-in skills.

How long can a SKILL.md file be?

Keep SKILL.md under 500 lines for optimal performance. Move detailed documentation into separate reference files linked one level deep so the agent reads them only when needed.

When should a skill include utility scripts?

Add scripts for fragile or consistency-critical operations where generated code would be unreliable, such as validation or form analysis. Document required packages and make clear whether the agent should execute or read each script.