arm-pz

Draft Skill — Development skill for Claude Code

Development community

Agent skill that creates a new skill from an idea: confirms the purpose before writing, checks installed siblings for overlap, splits scripts/references/assets, writes a description that triggers, val.

How to install Draft Skill

This entry records only its repository, not the path inside it, so there is no exact command to give. Open arm-pz/draft-skill and copy the folder into ~/.claude/skills/, or the file into ~/.claude/agents/.

What Draft Skill does

Alternatives in Development

Om Tidy — Self-maintenance pass — acts on every hygiene flag: archives completed work, groups loose clusters, splits ove 4.6k ★
MCP Language Server — mcp-language-server gives MCP enabled clients access semantic tools like get definition, references, rename, a 1.5k ★
Purpose — Orient yourself in pi-vs-cc — a collection of Pi coding agent extensions and agent specs that progressively de 527 ★

README

draft-skill

An agent skill that creates a **new** skill from a plain idea — no prompt list, no zip, just "I want an agent that does X". It confirms the purpose before writing a file, checks the idea against the skills already installed so two of them don't end up claiming the same request, decides what belongs in `scripts/` versus `references/` versus `assets/`, writes a description that actually triggers, validates the result with a script, and hands it off for tuning and packaging.

The two things it is strictest about are the two that fail silently in production: a description that promises a step the body never performs, and a name that already belongs to a better-established project. Both have a check written down rather than a feeling.

Install

npx skills add arm-pz/draft-skill --skill draft-skill

Or copy the `draft-skill/` folder into `~/.qoder/skills/` (Qoder) or `~/.claude/skills/` (Claude Code), then start a new session.

It calls `check_skill.py` from [`tune-skill`](https://github.com/arm-pz/tune-skill) for validation. Install that first, or the validate step has to be done by hand.

Ask it things like

"Make me a skill that reviews a client's SEO report."
"I keep pasting the same instructions — turn that capability into a skill."
"Scaffold a skill for talking to our internal API."
"There's an empty folder in ~/.qoder/skills/ — fill it properly."

What it does before writing anything

Collects three or four requests the skill should catch and one it should refuse, plus the output shape.
Reads the description of every installed sibling the examples touch, from the file.
Sets the boundary in both directions — what this owns, where it stops, who takes over.
Plans resources, then names the skill after checking GitHub for collisions.

Step 4's collision reading is documented in `references/structure.md`, including the trap that `github.com/topics/` renders a page for names that don't exist, so only a `topic:`