skill-writer

Guides creation of Agent Skills with valid SKILL.md frontmatter and structure.

1|1|Updated Jan 29, 2026
One-click install
npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill skill-writer-ultraviollettnympho
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: skill-writer
Source: https://github.com/ultraviollettnympho/transit-ticket/tree/main/.github/skills/skill-writer
Command: npx skills add https://github.com/ultraviollettnympho/transit-ticket --skill skill-writer-ultraviollettnympho

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Writing Agent Skills that Claude Code can actually discover and activate is error-prone: invalid YAML frontmatter, vague descriptions, wrong directory placement, and naming violations all cause Skills to silently fail. This Skill walks you through the entire authoring process so your Skills validate and trigger correctly. ## Core Features & Use Cases - Structured authoring workflow: Ten guided steps covering scope definition, location choice (personal vs. project), directory scaffolding, frontmatter rules, and content structure. - Validation and debugging: Built-in checklists for naming rules, description quality, YAML syntax, plus troubleshooting steps when a Skill fails to activate. - Reusable patterns: Ready-made templates for read-only Skills, script-based Skills, and multi-file Skills with progressive disclosure. - Use Case: You want to turn a repeated prompt workflow (e.g., commit message formatting) into a reusable project Skill. This Skill helps you pick a name, write a discoverable description, create SKILL.md, and verify activation. ## Quick Start Ask Claude to help you create a new Agent Skill for your desired workflow and follow the guided steps to produce a valid SKILL.md.

Frequently Asked Questions about skill-writer

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

FAQPage Schema
How do I create an Agent Skill for Claude Code?

Create a directory containing a SKILL.md file with YAML frontmatter defining a name and description, followed by Markdown instructions. Place it in ~/.claude/skills/ for personal use or .claude/skills/ for project-shared Skills, then restart Claude Code to load it.

What should a SKILL.md description include?

A description should state what the Skill does and when to use it, staying under 1024 characters. Include specific trigger words, file extensions, and concrete operations so Claude can match the Skill to relevant user queries.

Why is my Claude Code Skill not activating?

Skills fail to activate when descriptions are too vague, YAML frontmatter is invalid, or the file is in the wrong location. Add specific trigger words and file types to the description, verify the SKILL.md path, and run claude --debug to diagnose.

What are the naming rules for Agent Skills?

Skill names must use lowercase letters, numbers, and hyphens only, with a maximum of 64 characters, and must match the directory name. Names like pdf-processor are valid, while PDF_Processor or names with spaces are rejected.

Can I restrict which tools a Skill can use?

Yes, add the optional allowed-tools field to the frontmatter with a comma-separated list such as Read, Grep, Glob. This is recommended for read-only Skills or security-sensitive workflows that should not modify files.