Skip to content

Optimize the release-management skill family #1345

Description

@potiuk

Part of #1342 — apply the setup-family optimization recipe to the release-management family.

10 skills, 73,971 body tokens in total; 4 over the 200-token always-on budget, 8 over the 5,000-token body budget.

skill body tokens (budget 5,000) always-on tokens, est. (budget 200) lines (cap 500)
release-rc-cut 11,865 ⚠ ~274 ⚠ 931 ⚠
release-prepare 10,908 ⚠ ~400 ⚠ 991 ⚠
release-verify-rc 10,802 ⚠ ~323 ⚠ 967 ⚠
release-keys-sync 4,868 ~204 ⚠ 438
release-promote 6,968 ⚠ ~180 560 ⚠
release-vote-draft 6,745 ⚠ ~169 572 ⚠
release-announce-draft 5,976 ⚠ ~188 534 ⚠
release-audit-report 5,697 ⚠ ~164 518 ⚠
release-vote-tally 5,617 ⚠ ~182 557 ⚠
release-archive-sweep 4,525 ~183 429

Body tokens are from docs/mode-economics.md; always-on figures are a chars ÷ 4 estimate of description + when_to_use. ⚠ marks a budget exceeded. Line counts include the generated pre-flight block.

Order of work (per the umbrella):

  1. Trim the frontmatter of every skill marked ⚠ in the always-on column.
  2. Split any over-cap body, moving sub-action-specific rules into sibling files byte-for-byte.
  3. Wording pass on the rest, with headings, golden-rule headlines, code blocks and the pre-flight block kept byte-identical.
  4. Run each touched skill's eval suite before and after, outside the sandbox.

Record any inconsistencies found but not fixed (eval-coupled wording, stale headings) in the PR description.

Activity

  1. potiuk commented on Oct 5, 2026

    @potiuk
    MemberAuthor

    The release-management optimisation is complete.

    Savings

    Measured across all 10 release skills, from before the first PR to main with every pass merged:

    Before Now Change
    SKILL.md bodies, read on every run (measured_tokens) 78,241 65,114 −17%
    A release-prepare run (SKILL.md + the sub-command it executes) 14,285 6,600–9,300 −35–55%
    Advertised descriptions, loaded in every session (docs/setup/marketplace.md) ~1.4k ~0.8k −43%

    The split and the description pass cut most of the cost. The wording pass saved little, because the extraction and the split had already made the skills lean.

    What was done

    Still over the 500-line cap: release-rc-cut, -verify-rc, -announce-draft, -vote-draft and -audit-report. What remains in them is used on every run, so splitting further would save no tokens.

  2. added
    capability:resolveClose-out: invalidate, dedupe, CVE allocate, announcement
    capability:statsRead-only dashboards, metrics, governance evidence
    family:docsDocs, MISSION.md, READMEs
    family:ci.github workflows, prek, validators
    capability:triageSweep + classify + propose disposition
    substrate:framework-devTool substrate: build / validate / eval the framework itself
    substrate:releaseTool substrate: release-artefact helpers (reproducible archive build, lint, comparison)
    substrate:sandboxTool substrate: agent isolation, egress control, settings audit
    on Oct 5, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    capability:resolveClose-out: invalidate, dedupe, CVE allocate, announcementcapability:statsRead-only dashboards, metrics, governance evidencecapability:triageSweep + classify + propose dispositionenhancementNew feature or requestfamily:ci.github workflows, prek, validatorsfamily:docsDocs, MISSION.md, READMEsfamily:release-managementrelease-* skillsfamily:setupsetup-* skillsfamily:toolstools/*kind:perfToken / latency / API-call budgetsubstrate:framework-devTool substrate: build / validate / eval the framework itselfsubstrate:releaseTool substrate: release-artefact helpers (reproducible archive build, lint, comparison)substrate:sandboxTool substrate: agent isolation, egress control, settings audit

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions