Name: Skills Writer
Author: vchelaru

Process

Read all source files relevant to the skill topic.
Check .claude/skills/ for existing skill files to match style and depth.
Distill non-obvious behaviors, relationships, and gotchas into SKILL.md. Obvious things (property names, method signatures) do not belong.

Skill File Rules

Length: Under 500 lines; aim for under 100 for focused topics.
Naming: Kebab-case noun phrases for the directory (e.g., gum-tool-undo).
Frontmatter: name, description (third person, specific — state what the skill covers AND when to load it).
Structure: ## sections. Tables for key-file maps and event/class lists. Prose for relationships and non-obvious behavior.
Progressive disclosure: High-level architecture at the top. Link to separate detail files for advanced content (e.g., [xnafiddle.md](xnafiddle.md)) rather than inlining everything.

Read all source files relevant to the skill topic.
Check .claude/skills/ for existing skill files to match style and depth.
Distill non-obvious behaviors, relationships, and gotchas into SKILL.md. Obvious things (property names, method signatures) do not belong.

Length: Under 500 lines; aim for under 100 for focused topics.
Naming: Kebab-case noun phrases for the directory (e.g., gum-tool-undo).
Frontmatter: name, description (third person, specific — state what the skill covers AND when to load it).
Structure: ## sections. Tables for key-file maps and event/class lists. Prose for relationships and non-obvious behavior.
Progressive disclosure: High-level architecture at the top. Link to separate detail files for advanced content (e.g., [xnafiddle.md](xnafiddle.md)) rather than inlining everything.