| name | spreader |
| description | Use Spreader when a single-target shot is too narrow and the right move is to make the point of impact matter to the nearby area as well, catching clustered targets or forcing motion around the hit. |
| version | 0.1.0 |
| author | mmbnchips |
| license | CC0-1.0 |
| compatibility | Hermes Agent skills system |
| metadata | {"hermes":{"tags":["shipping-now","metaphorical","direct-fire-and-breach","direct-fire","offense","breach","decisive-action"],"homepage":"https://github.com/Hmbown/mmbnchips"}} |
Spreader
Let the impact bloom wide enough to clear the lane in front of you.
What This Skill Does
Use Spreader when a single-target shot is too narrow and the right move is to make the point of impact matter to the nearby area as well, catching clustered targets or forcing motion around the hit.
In this chip pack, Spreader is treated as a metaphorical battle-chip procedure with a shipping-now delivery profile.
Canonical reference input: Spreader.
Hermes shelf: Direct Fire and Breach.
When To Use
- The target is clustered tightly enough that the impact radius matters.
- You need to pressure a lane by making the landing point bloom wider than the shot itself.
- A wider hit gives better odds than waiting for perfect single-point precision.
Prerequisites
- These procedures rely on the normal tools already present in the active Hermes runtime; this repo does not ship a separate integration layer.
Procedure
- Restate the target, success condition, and no-touch boundaries before you spend the chip.
- Identify the impact point whose nearby area matters most.
- Choose the narrowest practical spread that still changes the local board state.
- Fire into that point, then verify what the bloom caught, forced, or revealed.
- Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.
Deliverables
- A wider direct action centered on one meaningful impact point.
- A short note explaining what the spread caught around the hit.
Pitfalls / Guardrails
- Keep the metaphor anchored to a real operator move instead of drifting into lore.
- Do not use Spreader when you need precision at one exact point.
- Do not widen the blast more than the local cluster justifies.
- 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 that the metaphor still maps cleanly to a real operator mechanism.
Example Invocation
/spreader widen the impact around one meaningful target point, keep the bloom as small as possible, and report what the spread caught around the hit
