vulcan

name: vulcan description: "Use Vulcan when the right move is sustained low-friction pressure: a tight burst of repeated actions that can confirm progress, expose resistance, or suppress one stubborn target without committing to a larger restructure." 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"

Lay down a short burst of repeated fire that keeps pressure on one target line.

What This Skill Does

Use Vulcan when the right move is sustained low-friction pressure: a tight burst of repeated actions that can confirm progress, expose resistance, or suppress one stubborn target without committing to a larger restructure. In this chip pack, Vulcan is treated as a metaphorical battle-chip procedure with a shipping-now delivery profile. Canonical reference input: Vulcan. Hermes shelf: Direct Fire and Breach.

When To Use

You need multiple quick hits against one clear target, not a single heavyweight strike.
The job benefits from repetition, cadence, or a controlled burst of verification.
You want to keep pressure on a problem while staying inside a narrow line of fire.

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 one target line that can absorb repeated hits without widening scope.
Deliver a short burst of direct actions, checking after each pass for movement or resistance.
Stop as soon as the target is suppressed or the burst stops being efficient.
Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

A burst of small direct actions aimed at one concrete target.
A short readout showing whether repeated pressure exposed progress or stalled out.

Pitfalls / Guardrails

Keep the metaphor anchored to a real operator move instead of drifting into lore.
Do not spray across unrelated targets just because the chip fires quickly.
If the problem needs a single precise cut or a terrain change, switch to a different chip.
Do not keep firing after the target has clearly stopped moving.
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

/vulcan apply a brief burst of repeated direct pressure against one clear target, stop the moment the line stops paying out, and report what the burst revealed