← ClaudeAtlas

gabe-pulselisted

Read-only completeness sweep — ten deterministic signals ranked into bands, plus the ANGLE family: which satellite would find something right now, surfaced as one line at the end of every spine beat so the manual-only skills stop depending on memory. Never writes, never dispatches, never judges code.
khujta/gabe-suite · ★ 0 · Data & Documents · score 66
Install: claude install-skill khujta/gabe-suite
# Gabe Pulse — is anything important owed? **Usage:** `/gabe-pulse [brief | --json | --since <ref>]` ## Gabe execution contract (E1–E7) This skill runs under the suite execution contract — E1 EVIDENCE · E2 RUN-BEFORE-✅ · E3 NO SILENT DOWNGRADE · E4 REUSE FIRST · E5 STATE SYNC · E6 MISSING ANCHOR = STOP · E7 REPORT WHERE — floors, not ceilings; a skill's own gate may be stricter, never looser. Full text: `../gabe-docs/references/execution-contract.md` (if that file is missing, E6 applies — STOP). ## What this does A **satellite**, not a beat. `/gabe-next` answers *"what is the one next step?"* from PLAN cells. Pulse answers the broader question you ask after a long stretch of work: **"is anything important owed anywhere?"** — including the things no beat is currently watching. It reads ten deterministic signals, sorts them into four bands, and prints a ranked report. It **writes nothing, dispatches nothing, and runs no tests.** Every row names the command that clears it; you decide whether to run it. Its reason for existing is the measured one: across 70 sessions on five repos, 20% ran no lifecycle beat at all, and 113 files changed in sessions that produced no commit and no record. Pulse is the manual check that makes that visible before it compounds. ## Procedure 1. Read `references/pulse-spec.md` IN FULL before executing — it is the binding spec: the ten signals, their exact sources, the band ranking, the cap rule, and the degradation table. If it is missing,