# Mini Bomb

> Use Mini Bomb when the right move is a small indirect strike: you know where the effect needs to land, but a straight-line shot is blocked, too predictable, or aimed at the wrong surface.

- Skill: `hmbown/mini-bomb-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add hmbown/mini-bomb-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hmbown/mini-bomb-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: CC0-1.0
- Author: Hmbown (https://skillmd.com/u/hmbown)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/hmbown/mini-bomb-2

---

# Mini Bomb
Lob a compact payload over the nearest blocker and force the landing zone to matter.
## What This Skill Does
Use Mini Bomb when the right move is a small indirect strike: you know where the effect needs to land, but a straight-line shot is blocked, too predictable, or aimed at the wrong surface.
In this chip pack, Mini Bomb is treated as a hybrid battle-chip procedure with a shipping-now delivery profile.
Canonical reference input: Mini Bomb.
Hermes shelf: [Direct Fire and Breach](../DESCRIPTION.md).
## When To Use

- The direct lane is blocked, defended, or otherwise not the cleanest approach.
- A fixed landing zone matters more than continuous forward pressure.
- A small burst at destination is better than a line attack through the front.

## Prerequisites

- Name which part of this move is real tool use versus battle-chip framing before you act.
- These procedures rely on the normal tools already present in the active Hermes runtime; this repo does not ship a separate integration layer.

## Procedure

1. Restate the target, success condition, and no-touch boundaries before you spend the chip.
2. Pick the landing zone and name what the arc is meant to bypass.
3. Lob the smallest payload that can land where it matters without widening the field.
4. Check whether the blast cleared the blocker, flushed movement, or exposed the need for a heavier follow-up.
5. Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

## Deliverables

- One indirect action aimed at a specific landing zone beyond the nearest obstacle.
- A short note describing what the arc bypassed and what the impact changed.

## Pitfalls / Guardrails

- Keep the theatrical framing, but name the concrete mechanism that makes the chip useful right now.
- Do not use Mini Bomb when the target needs precise zero-splash contact.
- Do not confuse an indirect lob with a delayed trap; if timing pressure is the point, switch to Time Bomb.
- If the landing zone is vague, scout first instead of guessing the arc.
- 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.
- Check which parts are concrete actions versus framing, so the operator can tell what is real now.

## Example Invocation
```text
/mini-bomb place one compact indirect hit on the landing zone that matters most, explain what obstacle the arc bypasses, and verify the blast changed the board the way you intended
```

