What problem does it solve?
When working with the @bradygaster/squad-cli, it is hard to know exactly how versions are stamped into squad.agent.md, what squad upgrade overwrites versus preserves, and how to check the npm registry for the latest release without breaking user data. This Skill documents those internals so an agent can perform version checks and upgrades safely.
Core Features & Use Cases
- Version Stamping Internals: Explains how getPackageVersion, stampVersion, and readInstalledVersion mutate and read squad.agent.md.
- Upgrade Behavior Reference: Details which files
squad upgrade overwrites (templates, workflows) and which it preserves (team.md, decisions.md, .squad/config.json, agent history).
- Registry & Cache Probing: Provides the npm dist-tags one-liner with a 5-second timeout, plus the OS-specific update-check cache paths and the repo-local .squad/.cache/version-check.json schema with 24h TTL.
- Use Case: A coordinator agent needs to greet users with an update notice only when a newer insider build exists; it reads the cache, falls back to
npm view @bradygaster/squad-cli dist-tags --json, and degrades gracefully on network errors.
Quick Start
Ask the agent to check whether a newer version of @bradygaster/squad-cli is available on the insider channel using the npm registry probe with a 5-second timeout.