Ship A Release To Skool

Every Skool pack lesson carries the current ZIP + checksum, and its advertised skill list matches exactly what that ZIP contains

Inputs

  • 📋 Release version
  • 📋 Pack list in scope
  • 📋 Whether any `draft` skills should be promoted to `ready` before the cut (decide *before* step 2 —

What BOB Does

  1. Refresh page frontmatter — `documented_skill_count`, `live_skill_count`, `last_synced`

Outputs

  • 📋 One GitHub Release per pack on `brncx-releases`, ZIP + `.sha256` attached
  • 📋 One commit + tag per pack in the `brncx-releases` repo, with a generated changelog
  • 🏢 Updated durable pages under `20-COMPANY/50-MARKETING/skool/courseware/pack-*/`
  • 📅 Updated Skool lessons — attachment, skill table, count, changelog line
Time Savings ~2–4 h (step 5 dominates — one lesson per pack, browser-driven) manual → automated with agent assistance
Try It "A vault release has been built and versioned (e.g. v2.5.0) and the Skool classroom still advertises the previous version's ZIPs and skill counts"
Compounding Each run refines templates and context — 1 automated steps improve with accumulated data