Hmbown Killer Eye
Put a watchful sensor on the field that fires when something crosses the line.
What This Skill Does
Use Killer Eye for tripwires, passive monitors, and sightline-based alerts that should fire only when the trigger is real. In this chip pack, Killer Eye is treated as a hybrid battle-chip procedure with a shipping-now delivery profile. Canonical reference input: Killer Eye. Hermes shelf: Traps and Obstacles.
When To Use
- You need a lightweight watch on a narrow path.
- The valuable signal is a crossing event, not continuous telemetry.
- A visible monitor is acceptable or desirable.
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.
Operator Inputs
- Name the narrow lane, threshold, or crossing event worth watching.
- Define what should count as a real trigger versus a harmless pass.
- Say how visible the monitor can be to the target or surrounding operators.
- State what action should follow if the eye fires.
Procedure
- Restate the target, success condition, and no-touch boundaries before you spend the chip.
- Collect the operator inputs below so the chip lands on the right panel.
- Pick the lane or threshold worth watching.
- Attach the sensor and define what counts as a crossing.
- Verify the alert is sharp enough to matter.
- Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.
Deliverables
- A tripwire, watch, or threshold alert.
- A short note on false-positive risk.
Output Contract
- A threshold-based watch, tripwire, or crossing alert on the narrowest useful lane.
- A trigger defined in simple, testable terms with clear false-positive boundaries.
- A named operator response for when the eye fires.
- A monitor lightweight enough to avoid turning a lane check into telemetry sprawl.
Do Not Use For
- Broad observability projects that need continuous instrumentation.
- High-noise environments where simple crossing logic will trigger constantly.
- Hidden counters where a visible monitor would compromise the plan.
Pair With
- Killer Eye + Rock Cube: constrain movement first so the eye watches a lane that truly matters.
- Killer Eye + Time Bomb: use the crossing alert to justify or time a delayed payload.
- Killer Eye + Anti Damage: detect the approach and pair it with a narrow reactive counter.
Pitfalls / Guardrails
- Keep the theatrical framing, but name the concrete mechanism that makes the chip useful right now.
- Do not install a noisy eye that everyone learns to ignore.
- Keep the trigger condition simple and testable.
- 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 the watched lane is specific enough that crossing events are meaningful.
- Confirm the trigger condition can be tested without interpretation drift.
- Confirm the operator knows what to do when the monitor fires; it is not alert theater.
- Check which parts are concrete actions versus framing, so the operator can tell what is real now.
Example Invocation
Use Killer Eye to watch the narrowest useful lane in this process and define exactly what crossing event should trip it.
Use Killer Eye here so I get one meaningful alert instead of more dashboard noise.