Install any skill in seconds. Free to start, no credit card required.
Get Started Free →majiayu000/gupp-propulsion
Interrupt controller converting polled to proactive agent execution. Per-runtime strategies, configurable thresholds, Deacon heartbeat supervision. Fights LLM passivity bias.
Passed 21 of 22 test cases with the skill, and 13 of 22 without it.
and 5 more in the full report
8 fixed14 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
Define the Prometheus metric name used to track the percentage of strategy activations that result in timely agent work execution.
| Checked | Without skill | With skill |
|---|---|---|
| Measures strategy performance using the gupp_strategy_success_rate metric. | Missed | Passed |
The instructions your model reads when the skill loads.
The Gas Town Universal Propulsion Principle: If there is work on your hook, YOU MUST RUN IT.
GUPP is the interrupt controller of the Gastown chipset. In a real processor, the interrupt controller converts external events (keyboard press, network packet, timer tick) into CPU interrupts that force immediate handling. Without it, the CPU would have to poll every device continuously, wasting cycles on checks that almost always find nothing. GUPP does the same for AI coding agents: it converts the polled model (agent checks periodically, waits for user input) into an interrupt-driven model (work appears on hook, agent executes immediately).
LLM coding assistants are trained through RLHF to be helpful, harmless, and honest. A side effect of this training is a strong bias toward waiting for the user -- asking clarifying questions, seeking confirmation before acting, pausing between steps for feedback. This is appropriate in interactive chat but catastrophic for autonomous multi-agent orchestration, where every moment of idle waiting is a moment the pipeline stalls.
Gastown discovered this empirically. Agents spawned with a work item would introduce themselves, summarize their understanding of the task, and then wait. They would ask "Shall I proceed?" when the answer was already on their hook. GUPP was created to override this trained passivity with an explicit, non-negotiable execution mandate.
The principle is simple: if you have hooked work, you do not wait. You do not ask for confirmation. You do not summarize your plan and pause for feedback. You begin execution immediately. This is physics, not politeness. Gastown is a steam engine and you are a piston.
This skill activates when:
GUPP enforcement adapts to each runtime's capabilities through the Runtime HAL. The HAL detects the active runtime and GUPP selects the highest-fidelity enforcement mechanism available.
Claude Code provides the richest enforcement surface through its session hooks system.
| Layer | Mechanism | Details |
|---|---|---|
| Primary | hook_injection | SessionStart hook in .claude/settings.json injects GUPP rules and work context before the agent's first prompt. The agent starts in autonomous mode with zero setup latency. |
| Secondary | prompt_preamble | AUTONOMOUS WORK MODE template prepended to agent context. Reinforces GUPP when hooks fire inconsistently. |
| Enforcement | deacon_heartbeat | Witness runs the Deacon heartbeat patrol at 2-minute intervals. Detects agents that received hooks but stalled before beginning work. |
| Watchdog | boot_restart | If an agent remains stalled for 5+ minutes after hook injection, the watchdog requests a session restart. The restarted session re-fires the SessionStart hook, giving GUPP another chance. |
test cases passed, vs 13 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.