write-a-skill

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

Updated Jul 7, 2026
One-click install
npx skills add https://github.com/bbenefield89/skills --skill write-a-skill-bbenefield89
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-skill
Source: https://github.com/bbenefield89/skills/tree/main/skills/write-a-skill
Command: npx skills add https://github.com/bbenefield89/skills --skill write-a-skill-bbenefield89

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a well-structured agent skill requires knowing the SKILL.md format, description conventions, and when to split content into scripts or reference files. This Skill guides you through gathering requirements, drafting, and reviewing a new skill so it is discoverable and effective. ## Core Features & Use Cases - Structured authoring process: Walks through requirement gathering, drafting, and user review for new skills. - SKILL.md template and description rules: Provides a ready template plus concrete guidance on writing trigger-rich descriptions agents can match. - Bundling guidance: Explains when to add utility scripts, split reference files, and keep SKILL.md concise. - Use Case: You want to package a repeatable workflow as an installable skill. Use this Skill to scaffold the directory, write a discoverable description, and validate it against the review checklist. ## Quick Start Ask the agent to help you create a new skill for your chosen task and follow its guided drafting and review process.

Frequently Asked Questions about write-a-skill

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

FAQPage Schema
How do I create a new agent skill?

Create a directory containing a SKILL.md file with YAML frontmatter defining a name and description, followed by Markdown instructions. This Skill walks you through gathering requirements, drafting the content, and reviewing it against a checklist.

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 and contexts. Keep it under 1024 characters, in third person, since it is the only text the agent sees when selecting skills.

When should I add scripts to a skill?

Add utility scripts when operations are 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 separate files?

Split content when SKILL.md exceeds 100 lines, when content covers distinct domains, or when advanced features are rarely needed. Move detailed docs to REFERENCE.md and examples to EXAMPLES.md, linking them from SKILL.md.

What are the limitations of a minimal skill description?

Vague descriptions like "helps with documents" give the agent no way to distinguish the skill from others, so it may never be triggered. Always include concrete triggers, file types, or task keywords in the description.