create-skill

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

Updated Aug 6, 2026
One-click install
npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill create-skill-ferrarifankid04
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/ferrarifankid04/ai-skills-public/tree/main/cursor/skills-cursor/create-skill
Command: npx skills add https://github.com/ferrarifankid04/ai-skills-public --skill create-skill-ferrarifankid04

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. This Skill walks you through gathering requirements and producing a compliant, discoverable skill for Cursor. ## Core Features & Use Cases - Requirements Gathering: Structured discovery of purpose, storage location (personal vs project), trigger scenarios, and output formats before writing. - Authoring Guidance: Enforces naming rules, third-person descriptions with WHAT and WHEN, conciseness, progressive disclosure, and anti-pattern avoidance. - Four-Phase Workflow: Discovery, Design, Implementation, and Verification phases with a final quality checklist. - Use Case: You want a project skill that generates commit messages in your team's format. This Skill helps you draft the name, description, instructions, and examples, then verifies the result against the checklist. ## Quick Start Help me create a new Cursor skill that reviews pull requests against our team coding standards.

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 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.md description include?

Write in third person and include both what the skill does and when to use it, with specific trigger terms. For example, mention file formats, task names, and scenarios so the agent knows when to apply the skill.

Where are Cursor skills stored?

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

How long should a SKILL.md file be?

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

What are common mistakes when writing agent skills?

Common anti-patterns include vague names like helper or utils, Windows-style backslash paths, time-sensitive instructions, inconsistent terminology, and offering too many tool options without a clear default.