create-skill

Guides creation of agent skills using progressive disclosure and structured SKILL.md conventions.

Updated Feb 8, 2026
One-click install
npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill create-skill-ttnhan18062000
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-skill
Source: https://github.com/ttnhan18062000/rpg-based-simulation/tree/main/docs/archive/legacy_agents_skills_20260722/create-skill
Command: npx skills add https://github.com/ttnhan18062000/rpg-based-simulation --skill create-skill-ttnhan18062000

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Writing skills that agents can reliably discover and use is hard: bloated SKILL.md files waste context, vague descriptions prevent discovery, and poor structure slows activation. This Skill provides the conventions, patterns, and checklists needed to author effective skills. ## Core Features & Use Cases - Progressive Disclosure Guidance: Enforces the 200-line SKILL.md rule and the three-level loading system (metadata, body, bundled resources) to minimize context usage. - Structure and Naming Standards: Defines SKILL.md frontmatter requirements, gerund-form naming conventions, and third-person description writing for reliable skill discovery. - Best Practices References: Ships detailed reference files covering examples, workflows, feedback loops, and anti-patterns for skill authoring. - Use Case: When you need to package a repeatable workflow (e.g., PDF processing or database management) as a reusable agent skill, use this guide to structure the SKILL.md, split details into references/, and validate against the quality checklist. ## Quick Start Use the create-skill guide to help me author a new skill for processing Excel files, following the progressive disclosure and naming conventions.

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 skill for an AI agent?

Create a directory containing a SKILL.md file with YAML frontmatter defining a name and description, followed by concise Markdown instructions. Keep the body under 200 lines and move detailed content into a references/ directory loaded on demand.

What should a SKILL.md file contain?

SKILL.md requires YAML frontmatter with name and description fields, plus a Markdown body covering the skill's purpose, when to use it, and how to use it. It should link to reference files one level deep for detailed documentation.

How long should a SKILL.md file be?

SKILL.md should stay under 200 lines, though up to 500 lines can still perform adequately. Longer content should be split into reference files so the agent loads details only when needed, reducing context usage by roughly 85 percent.

How do I write a good skill description for discovery?

Write the description in third person, stating both what the skill does and when to use it, with specific keywords and triggers. Avoid vague phrases like "helps with documents" and first- or second-person phrasing.

What naming convention should skills follow?

Use gerund-form names such as processing-pdfs or analyzing-spreadsheets. Noun phrases and action-oriented names are acceptable alternatives, but avoid vague names like helper or utils and keep naming consistent across your skill collection.

When should I split skill content into reference files?

Split content whenever SKILL.md exceeds 200 lines or covers multiple domains. Keep references one level deep from SKILL.md, add a table of contents to reference files over 100 lines, and avoid duplicating content between files.