create-skill

Guides creation of new agent-native skills using templates and naming conventions.

Updated May 13, 2026
One-click install
npx skills add https://github.com/fred07diamond/Call-Copilot --skill create-skill-fred07diamond
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/fred07diamond/Call-Copilot/tree/main/apps/design/.agents/skills/create-skill
Command: npx skills add https://github.com/fred07diamond/Call-Copilot --skill create-skill-fred07diamond

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams building agent-native apps need a consistent way to capture reusable agent guidance, but without a standard process skills end up vague, mis-scoped, or duplicating existing documentation. ## Core Features & Use Cases - 5-Question Interview: A structured intake that defines the skill's purpose, triggering conditions, type, and supporting files before writing anything. - Three Skill Templates: Ready-made markdown templates for Pattern (architectural rules), Workflow (step-by-step), and Generator (scaffolding) skills. - Naming and Quality Rules: Enforces hyphen-case naming, descriptions under 40 words, SKILL.md under 500 lines, and lists anti-patterns like inline LLM calls or database usage. - Use Case: An engineer notices the agent repeatedly makes the same architectural mistake, answers the five interview questions, picks the Pattern template, and produces a new skill that prevents the mistake going forward. ## Quick Start Ask the agent to create a new skill for a recurring pattern, and it will walk through the interview questions and generate the SKILL.md from the appropriate template.

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 new skill for an agent-native app?▼

Answer the five interview questions covering purpose, triggering conditions, skill type, and supporting files, then fill in the matching Pattern, Workflow, or Generator markdown template. Save it as SKILL.md inside .agents/skills/your-skill-name/.

When should I create a skill instead of editing AGENTS.md?▼

Create a skill when guidance is reusable and should trigger in specific situations, such as repeated patterns or multi-step workflows. Put one-off notes or general project context in AGENTS.md or learnings.md instead.

What are the naming rules for skill directories?▼

Skill names must use hyphen-case only, matching the pattern [a-z0-9-] with a maximum of 64 characters. Pattern skills use descriptive names like storing-data, while workflow and generator skills use verb-noun forms like create-script.

What should go in a skill description field?▼

Keep the description under 40 words and describe when the skill should trigger in natural language. Slightly over-triggering is preferred over under-triggering, and vague phrases like "helps with development" should be avoided.

What are common anti-patterns when writing agent skills?▼

Avoid inline LLM calls, introducing databases, ignoring db sync wiring, vague descriptions, and pure documentation without actionable guidance. Skills should direct agent action rather than just explain concepts.