write-a-skill

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

Updated Nov 23, 2024
One-click install
npx skills add https://github.com/tokisakiyuu/dotfiles --skill write-a-skill-tokisakiyuu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: write-a-skill
Source: https://github.com/tokisakiyuu/dotfiles/tree/main/home/dot_claude/skills/write-a-skill
Command: npx skills add https://github.com/tokisakiyuu/dotfiles --skill write-a-skill-tokisakiyuu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a well-formed agent skill requires knowing the SKILL.md format, frontmatter rules, description conventions, and when to split content into scripts or reference files. This Skill guides that process so new skills are discoverable and correctly structured. ## Core Features & Use Cases - Structured authoring process: Gathers requirements, drafts the skill, and reviews it with the user in three steps. - SKILL.md template and description rules: Provides a ready template plus concrete guidance on writing trigger-rich descriptions under 1024 characters. - Splitting and scripting guidance: Explains when to add utility scripts, when to split content into REFERENCE.md or EXAMPLES.md, and includes a review checklist. - Use Case: You want to package a repeatable workflow as a reusable agent skill. This Skill walks you from requirements to a complete, review-ready skill directory. ## Quick Start Help me write a new skill for converting Markdown notes into slide decks, including the SKILL.md and any helper scripts it needs.

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 SKILL.md file for an agent skill?▼

Start with YAML frontmatter containing a name and a description with explicit triggers, then add a quick start, step-by-step workflows, and links to advanced reference files. Keep the body under 100 lines and split longer content into separate files.

What makes a good skill description for agent discovery?▼

A good description states what the skill does in the first sentence and when to trigger it in the second, using specific keywords, file types, or contexts. It must stay under 1024 characters, use third person, and avoid vague phrases like "helps with documents".

When should I add scripts to a skill?▼

Add utility 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 over generated code.

When should I split skill content into multiple files?▼

Split content when SKILL.md exceeds 100 lines, when the material covers distinct domains, or when advanced features are rarely needed. Move detailed docs to REFERENCE.md and usage samples to EXAMPLES.md, keeping references one level deep.

What should I check before publishing a new skill?▼

Verify the description includes "Use when" triggers, SKILL.md stays under 100 lines, terminology is consistent, examples are concrete, and no time-sensitive information is included. The skill provides a review checklist covering each of these points.