write-a-skill

Create new agent skills with structured SKILL.md files and bundled resources.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing a well-structured agent skill requires knowing the correct SKILL.md format, description conventions, and when to split content into scripts or reference files. This Skill guides you through that process so new skills are discoverable and effective. ## Core Features & Use Cases - Guided Skill Authoring: Walks through gathering requirements, drafting SKILL.md, and reviewing the result with the user. - Description Best Practices: Explains how to write trigger-rich descriptions so agents can select the right skill. - Structure Guidance: Defines when to add scripts, split reference files, and keep SKILL.md concise. - Use Case: You want to build a custom skill for your team's deployment workflow. Use this Skill to draft the SKILL.md, decide whether helper scripts are needed, and validate it against the review checklist. ## Quick Start Help me create a new skill for formatting weekly status reports from raw notes.

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?

Write a description under 1024 characters in third person with two parts: what the skill does, then "Use when" followed by specific triggers like keywords, file types, or contexts. The description is the only text the agent sees when choosing skills.

How do I create a new agent skill from scratch?

Gather requirements about the task domain and use cases, draft a SKILL.md with YAML frontmatter containing name and description, then add scripts or reference files if needed. Review the draft with the user against a checklist before finalizing.

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. Keep references one level deep and link them from the main SKILL.md.

When should a skill include utility scripts?

Add scripts when operations are deterministic like 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.

What makes a skill description fail to trigger?

Vague descriptions like "Helps with documents" give the agent no way to distinguish the skill from others. Include concrete capabilities and specific trigger keywords so the agent can match user requests to the skill.