air-shot

name	air-shot
description	Use Air Shot when you need a lightweight interrupt, nudge, or repositioning move rather than a high-damage attack.
version	0.1.0
author	mmbnchips
license	CC0-1.0
compatibility	Hermes Agent skills system
metadata	{"hermes":{"tags":["shipping-now","metaphorical","control-and-terrain","control","terrain","positioning","room-control"],"homepage":"https://github.com/Hmbown/mmbnchips"}}

Air Shot

Interrupt momentum and push the target into a better position.

What This Skill Does

Use Air Shot when you need a lightweight interrupt, nudge, or repositioning move rather than a high-damage attack. In this chip pack, Air Shot is treated as a metaphorical battle-chip procedure with a shipping-now delivery profile. Canonical reference input: Air Shot. Hermes shelf: Control and Terrain.

When To Use

• A process or plan needs to be deflected, paused, or redirected.
• A draft needs a corrective shove more than a rewrite.
• You want to create breathing room before a stronger move.

Prerequisites

• These procedures rely on the normal tools already present in the active Hermes runtime; this repo does not ship a separate integration layer.

Operator Inputs

• Describe the momentum, plan, draft, or process that needs interrupting.
• Name the smallest shove or redirect that would create a better position.
• State what new lane, breathing room, or decision window you want to open.
• Say how the operator will judge that the board state improved.

Procedure

1. Restate the target, success condition, and no-touch boundaries before you spend the chip.
2. Collect the operator inputs below so the chip lands on the right panel.
3. Identify the momentum that needs interrupting.
4. Apply the smallest shove that changes the board state.
5. Reassess the room after the push.
6. Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

• A redirect, pause, or small corrective edit.
• A note describing the new position or operating window.

Output Contract

• One lightweight interrupt, redirect, pause, or corrective nudge.
• A short explanation of what changed in the target position or momentum.
• A clear statement of the new options or operating window created.
• No claim that the problem is solved outright unless the operator asked for only a shove.

Do Not Use For

• Final removal work that should be handled as a clean kill shot or cut.
• Large structural takeovers where ownership or room control is the actual need.
• Situations where the target position is already good and only direct execution remains.

Pair With

• After Air Shot, switch to Cannon when the interrupt creates one clean straight-line shot.
• After Air Shot, switch to Sword when the shove reveals one local block that should now be cut out.
• After Air Shot, switch to Panel Grab when the redirect worked but one narrow lane still needs to be claimed.

Pitfalls / Guardrails

• Keep the metaphor anchored to a real operator move instead of drifting into lore.
• Do not treat a shove like a kill shot.
• If the target should be removed outright, use another chip.
• Keep the chip metaphor anchored to a real operating move; do not let flavor substitute for procedure.

Verification

• Check that the response includes every promised deliverable and leaves an inspectable audit trail.
• Check that confirmed facts, assumptions, and proposed follow-up are visibly separated.
• Confirm Hermes applied a shove, not a disguised full rewrite.
• Confirm the interrupt changed timing, position, or momentum in a way the operator can inspect.
• Confirm the new room or next-step options are spelled out clearly.
• Check that the metaphor still maps cleanly to a real operator mechanism.

Example Invocation

Use Air Shot on this overcomplicated draft: make the smallest redirect that gets it back on brief, then tell me what that opened up next.
Use Air Shot to interrupt this failing rollout plan with a safer temporary path, without redesigning the whole deployment.