trailhead-manage

trailhead-manage is the manage cluster of the trailhead skill: the admin verbs that keep a trailhead install healthy. config shows the effective config or changes it (a guided menu, or get / set <key> <value>); update checks for a newer trailhead and installs it where that is safe; prune reclaims a map's native sub-issue slots under GitHub's 100-cap; audit checks closed tickets for regressions against today's code and finds duplicate or groupable open ones. Everything lives on the GitHub Issues; the repo holds code only.

Load first, in order

Before doing anything, load <skill base>/../_shared/load-first.md and follow it: the shared-core load contract (the six core files, in order, then the effective config). <skill base> is this skill's base directory (Claude Code prints it as Base directory for this skill: when the skill loads; on another host, the directory holding this SKILL.md): resolve the path to an absolute path and open it with the Read tool on that absolute path. Never cd into a skills directory and never read a relative path from the shell (a cd compound followed by a read is denied by the search guard). The same rule covers every later ../_shared/... or references/... path in this skill: resolve it against the base directory to an absolute path before reading. _shared/ is a sibling of this cluster's own directory (at ../_shared/), never a child of it; its absence from a listing of the cluster dir is expected, not a missing core.

These admin verbs resolve no ticket and set up no isolation workspace.

Routing: verb to engine

The first word of the arguments is the verb (config, update, prune, or audit); the rest is that verb's argument (get, set <key> <value>, a map, --all, or empty).

• config [get|set …] to ../_shared/configuration-reference.md: the config keys, their semantics, and the guided menu setup. With no argument it runs the guided setup; config get prints the merged config read-only (project .trailhead/config.json over global over defaults, showing which source wins each key); config set <key> <value> writes one key directly (to the project .trailhead/config.json, or to ~/.claude/trailhead/config.json with --global). Read that file and follow it.
• update to references/updating.md: the update protocol (detect the install channel, compare the installed version with the latest from the matching source, install the newer one where it is safe). Read that file and follow it.
• prune [map] to references/pruning.md: reclaim native sub-issue slots on a map near or at GitHub's 100 sub-issue cap by dropping the edges of closed and orphan tickets and re-adding missing ones, keeping every reference (Parent line, Decisions-so-far pointer, map label). With no argument it prunes the active map. Read that file and follow it.
• audit [map] [--all] to references/auditing.md: audit the closed tickets since the last audit (or all of them with --all) for regressions against the current code (a fast no-agent path for unchanged code), classing each as implemented, unchanged, evolved, implemented wrong, or not implemented, and compare the open tickets for duplicates and groupable clusters; every fix is a proposal applied only on an explicit yes. With no argument it covers every open map plus the whiteboard; with a map it covers that map only. Read that file and follow it.

The full config key reference is a single source, shared with the rest of the skill: ../_shared/configuration-reference.md (keys + guided setup).