writing-skills

Guides authoring, structuring, and validating agent skills conforming to the agentskills.io specification.

Updated Jul 4, 2025
One-click install
npx skills add https://github.com/milespossing/nixdots --skill writing-skills-milespossing
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: writing-skills
Source: https://github.com/milespossing/nixdots/tree/main/modules/agents/_skills/writing-skills
Command: npx skills add https://github.com/milespossing/nixdots --skill writing-skills-milespossing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing an agent skill that actually gets discovered and triggered is hard: descriptions without triggers never load, folder names mismatch frontmatter, and bloated SKILL.md files blow the activation token budget. This Skill provides a step-by-step authoring procedure so your skills conform to the agentskills.io specification and load correctly. ## Core Features & Use Cases - Skill Scaffolding: Create a new skill from scratch with the correct folder layout (SKILL.md plus optional scripts/, references/, and assets/ directories) and a minimal skeleton template. - Frontmatter & Naming Rules: Enforces naming constraints (lowercase, hyphens, max 64 chars, folder name must match the name field) and shows how to write descriptions that answer what the skill does and when to load it. - Progressive Disclosure Design: Explains the three loading stages (discovery, activation, execution) and how to split content into focused reference files to stay within token budgets. - Validation & Auditing: Provides a manual checklist and the skills-ref CLI command to validate a skill, plus a catalog of common mistakes like hidden script dependencies and vague instructions. - Use Case: You built a pdf-processing skill but the agent never triggers it. Load this Skill to audit the description for missing trigger phrases, verify the folder name matches the frontmatter, and split an oversized SKILL.md into references/. ## Quick Start Ask the agent to scaffold a new agent skill named 'code-review' with proper frontmatter, folder layout, and a trigger-rich description following the agentskills.io specification.

Frequently Asked Questions about writing-skills

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 one sentence under 1024 characters that answers what the skill does and when the agent should load it. Include concrete trigger keywords and user intents, since the description is the only field visible at discovery time.

How to structure an agent skill folder with SKILL.md?▼

Create a folder whose name exactly matches the name frontmatter field, containing a required SKILL.md file. Add optional scripts/, references/, and assets/ subdirectories only when needed for executable helpers, on-demand docs, or templates.

Why is my agent skill not being triggered?▼

The most common cause is a description without trigger phrases, so the agent cannot tell when to load it. Also check that the folder name matches the name field exactly and that the name uses only lowercase letters, digits, and single hyphens.

What are the naming rules for a SKILL.md name field?▼

Names must use lowercase a-z, digits, and single hyphens only, with a maximum of 64 characters. Leading or trailing hyphens and double hyphens are rejected, and the folder name must match the name field exactly.

When should content go in references instead of SKILL.md?▼

Move content into references/ when the SKILL.md body approaches 500 lines or roughly 5000 tokens. Split references by topic into small focused files, since agents load them one at a time during the execution stage.

How do I validate an agent skill against the specification?▼

Run the skills-ref CLI with the command 'skills-ref validate ./my-skill' if it is installed. Otherwise manually check the name format, description length, body size, and that all relative paths in the body point to existing files.