create-skill

Create Agent Skills with structured SKILL.md files and supporting resources.

Updated Sep 7, 2026
One-click install
npx skills add https://github.com/deriye/.agents-work --skill create-skill-deriye
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/deriye/.agents-work/tree/main/skills/create-skill
Command: npx skills add https://github.com/deriye/.agents-work --skill create-skill-deriye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing effective Agent Skills requires knowing the SKILL.md format, frontmatter rules, description best practices, and directory conventions. This Skill guides the agent through gathering requirements, designing, implementing, and verifying new skills so they are discoverable and concise. ## Core Features & Use Cases - Guided Skill Authoring: Walks through a four-phase workflow (discovery, design, implementation, verification) for creating personal or project skills. - Format Standards: Enforces SKILL.md frontmatter rules, third-person descriptions with trigger terms, progressive disclosure, and the 500-line limit. - Use Case: A user wants a reusable skill that generates commit messages in their team's format. The agent gathers requirements, drafts the name and description, writes SKILL.md with examples, and verifies it against the quality checklist. ## Quick Start Ask the agent to create a new skill for your workflow, for example: create a skill that reviews pull requests against our team 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 an Agent Skill with a SKILL.md file?▼

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

What makes a good skill description for discovery?▼

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

Where should personal vs project skills be stored?▼

Personal skills go in ~/.agents/skills/ and apply across all projects, while project skills live in .cursor/skills/ and are shared with 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 and put detailed material in separate reference files linked one level deep. This progressive disclosure keeps the context window efficient while preserving access to depth.

When should a skill include utility scripts?▼

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