Workflow · Brew 1 · Pour-over

Build a skill and make it installable

Go from an idea or a pile of prompts to a tested skill anyone can install: draft it, tune its trigger, then package and release it.

The steps, in order.

  1. Step 1 · pick one

    Draft Skill Creates a new agent skill from a plain idea: confirms the purpose before writing anything, checks the installed siblings for overlap, splits scripts from references from assets, writes a description that actually triggers, then validates it with check_skill.py. Written from scratch, so it carries no text from Qoder's built-in skill-creator, which ships without a licence permitting redistribution. unversioned · shown working 24 Oct 2026 Prompts To Skill Turns a list of your own prompts into a finished, tested skill, one skill per prompt: an intent interview, an overlap check against what is already installed, a draft written with draft-skill, trigger test cases that include near-misses, and a tune-skill gate at the end. It needs draft-skill and tune-skill and stops with a clear message if either is missing. unversioned

  2. Step 2

    Tune Skill Audits and fine-tunes a skill that already exists: the description that never fires, overlap with installed siblings, stale names and counts, handoff contracts that do not hand off. Ships check_skill.py, a deterministic validator over frontmatter, folder and heading agreement, description length and reference paths that do not exist. Not for creating one from scratch; that is draft-skill. unversioned · shown working 24 Oct 2026

  3. Step 3

    Prompts To Skill Release Packages a finished skill for release: runs its trigger test cases and records which passed and which did not, sets the version and CHANGELOG, builds the archive, writes the README, and ends with a per-platform install checklist. Failed tests stay in the report instead of being dropped from it. unversioned

  4. Step 4 · optional

    Skill to Mod Checks whether a skill should become a Claude Code mod, then builds the plugin with your skill unchanged and a thin trigger, validates and tests it, and lists what it can touch. Says no when a skill should stay a skill. unversioned

skill-launch runs the first steps as one chain.

Install the whole workflow.

npx skills add arm-pz/draft-skill                        # step 1
npx skills add arm-pz/prompts-to-skill                   # step 1, or the line above
npx skills add arm-pz/tune-skill                         # step 2
npx skills add arm-pz/prompts-to-skill-release           # step 3
npx skills add arm-pz/skill-to-mod --skill skill-to-mod  # step 4, optional

In Claude Code you can take every skill at once instead: /plugin marketplace add arm-pz/caffeinity-skills, then /plugin install caffeinity@caffeinity-skills. Not sure this is the right workflow? Install caffeinity-routing and describe the outcome; it picks one.

Other workflows.

Need this fitted to your team's own tools and rules? We build custom skills.