killer-eye

Detect crossing events on defined paths using threshold-based monitors.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Hmbown/mmbnchips --skill killer-eye
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: killer-eye
Source: https://github.com/Hmbown/mmbnchips/tree/main/generated/codex/killer-eye
Command: npx skills add https://github.com/Hmbown/mmbnchips --skill killer-eye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Killer Eye provides a lightweight threshold-based monitor to alert when something crosses a defined line or path, avoiding constant telemetry.

Core Features & Use Cases

  • Threshold-based monitoring for narrow lanes and sightlines
  • Lightweight, timely alerts when a crossing occurs
  • Use cases include tripwires, passive field monitors, and boundary alerts

Quick Start

Place a threshold-based monitor on the narrowest useful lane and define the exact crossing condition to trigger an alert.

Frequently Asked Questions about killer-eye

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up threshold alerts for crossing events on a defined path?

To set up threshold alerts for crossing events, place a monitor on the narrowest useful lane and define the exact crossing condition. This ensures you receive lightweight, timely alerts only when the trigger criteria are met.

What is threshold-based monitoring for sightline alerts?

Threshold-based monitoring for sightline alerts is a mechanism that triggers notifications only when an object crosses a defined path. It avoids constant telemetry by focusing strictly on specific crossing events to keep alerts concise and actionable.

Can I use crossing event detection for passive field monitoring?

Yes, you can use crossing event detection for passive field monitoring. By configuring a simple threshold and lane trigger, the monitor acts as a tripwire to provide lightweight, timely boundary alerts without continuous data streaming.

What is the best way to avoid constant telemetry when monitoring a boundary lane?

The best way to avoid constant telemetry when monitoring a boundary lane is to use a threshold-based crossing monitor. It specifies a simple threshold and trigger criteria to ensure alerts are generated only for actual crossing events.

Why should I use a tripwire monitor instead of continuous tracking for boundary alerts?

You should use a tripwire monitor instead of continuous tracking to avoid alert fatigue from constant telemetry. A threshold-based monitor ensures notifications are concise and actionable by triggering only when a crossing event occurs.