create-skill

Design and document Cursor Skills with required frontmatter and structure.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Guides users through creating effective Agent Skills for Cursor. It explains the required frontmatter (name and description) and the recommended structure, so skills are easy to discover and reuse.

Core Features & Use Cases

  • Provides a clear Skill creation workflow: discovery, design, implementation, and verification.
  • Describes the required frontmatter and the optional components (scripts/, references/, assets/) that can accompany a skill.
  • Outlines naming conventions, folder structure, and progressive disclosure to keep skills maintainable.

Quick Start

Create a minimal SKILL.md with frontmatter for name and description and a concise, action-oriented body.

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 Skill and what frontmatter is required?

To create a Cursor Skill, author a SKILL.md file with required frontmatter for name and description, then add a concise, action-oriented body. This ensures the skill is discoverable and reusable.

What is the recommended folder structure for organizing personal and project Cursor Skills?

Cursor Skills use specific folder structures: personal skills reside in ~/.cursor/skills/ and project skills in .cursor/skills/. Organizing them this way maintains discoverability and keeps workflows manageable.

What is progressive disclosure in skill creation and when should I apply it?

Progressive disclosure in skill creation structures SKILL.md documentation to reveal complexity incrementally. Apply it to keep skills maintainable and ensure discoverability without overwhelming the Cursor agent.

What is the best way to document and structure a SKILL.md file for Cursor?

The best way to document a SKILL.md file is following the skill creation workflow: discovery, design, implementation, and verification. Include required frontmatter and use optional components like scripts/ or references/.

Can I use optional components like scripts and assets when authoring a Cursor Skill?

Yes, you can use optional components like scripts/, references/, and assets/ directories to accompany a Cursor Skill. These components support the core SKILL.md file and extend the skill's capabilities.