Workflow · Brew 10 · Descale

Maintain the skill family

Keep a family of skills healthy after release: tune what drifted, re-release what changed, and confirm every listing still matches.

The steps, in order.

  1. Step 1

    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

  2. Step 2 · optional

    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

  3. Step 3

    Upstream Check Finds local commits that never reached GitHub, pushes only clean fast-forwards after a secret screen, then checks that the site index, the homepage, the marketplace and the READMEs agree with the repos that actually ship a SKILL.md. unversioned · shown working 24 Oct 2026

The nightly health job opens the issue this starts from; a weekly scheduled session runs it and opens PRs.

Install the whole workflow.

npx skills add arm-pz/tune-skill                # step 1
npx skills add arm-pz/prompts-to-skill-release  # step 2, optional
npx skills add arm-pz/upstream-check            # step 3

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.