write-a-skill

Create new agent skills with proper structure, frontmatter, and bundled resources.

3|Updated Jan 9, 2026
One-click install
npx skills add https://github.com/craft-ts/craft-ts --skill write-a-skill-craft-ts
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-a-skill
Source: https://github.com/craft-ts/craft-ts/tree/main/.agents/skills/write-a-skill
Command: npx skills add https://github.com/craft-ts/craft-ts --skill write-a-skill-craft-ts

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a well-formed agent skill requires knowing the exact SKILL.md structure, frontmatter rules, description conventions, and when to split content into scripts or reference files. This Skill guides the creation process so new skills are discoverable, concise, and correctly organized. ## Core Features & Use Cases - Structured authoring workflow: Gathers requirements, drafts the skill, and reviews it with the user in three clear steps. - SKILL.md template and description rules: Provides a ready template plus concrete guidance on writing trigger-rich descriptions that agents can match to user requests. - Bundling guidance: Explains when to add utility scripts for deterministic tasks and when to split content into REFERENCE.md or EXAMPLES.md files. - Use Case: A user wants to build a new skill for generating API client code. This Skill walks them through defining the description triggers, drafting the instructions, and deciding whether helper scripts are needed. ## Quick Start Ask the agent to help you create a new skill for your chosen task and answer its questions about scope, triggers, and resources.

Frequently Asked Questions about write-a-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a good skill description for agent discovery?▼

Write the description in third person with two parts: one sentence stating what the skill does, then a sentence starting with "Use when" listing specific triggers like keywords, file types, or contexts. Keep it under 1024 characters so agents can match it to user requests.

What files does a new agent skill need?▼

A skill requires a SKILL.md file with YAML frontmatter containing name and description, followed by Markdown instructions. Optionally add REFERENCE.md or EXAMPLES.md for detailed content and a scripts/ directory for deterministic utility code.

When should I split skill content into separate files?▼

Split content when SKILL.md exceeds 100 lines, when the material covers distinct domains, or when advanced features are rarely needed. Keep references one level deep so the main instructions stay concise and load quickly.

When should a skill include utility scripts?▼

Add scripts when an operation is deterministic, such as validation or formatting, when the same code would be generated repeatedly, or when errors need explicit handling. Scripts save tokens and improve reliability compared to generated code.

What are common mistakes when writing a skill description?▼

Vague descriptions like "Helps with documents" give the agent no way to distinguish the skill from others. Always include concrete capabilities and specific trigger phrases so the agent knows exactly when to load it.