Eyebite
Fix your attention on a target and selectively degrade its capabilities.
Overview
Eyebite is interpreted here as a metaphorical spell with a prototype execution model.
Canonical source: Eyebite (spell)
Provider target: OpenClaw
When To Use
- A specific system, service, or feature needs to be selectively degraded rather than fully shut down.
- You are responding to an incident and need to disable specific capabilities while keeping the rest operational.
- Targeted throttling or feature disabling is more appropriate than a full kill or freeze.
Workflow
- Identify the specific target and the capability you want to degrade or disable.
- Assess dependencies — what else relies on the capability you are about to remove?
- Execute the selective degradation: feature flag, targeted throttle, capability restriction.
- Monitor the target to confirm the degradation is working as intended without cascading side effects.
- Document the intervention and set a review point for restoration.
Deliverables
- Confirmation of which capabilities were degraded and how.
- A dependency impact assessment.
- A restoration plan for when the degradation should be reversed.
Guardrails
- Eyebite is surgical, not punitive. Degrade only what is necessary to address the specific problem.
- Selective degradation of user-facing features requires clear communication to affected users.
- Do not use targeted degradation as a substitute for fixing the underlying issue.
Default Invocation
Use $eyebite to selectively degrade a specific capability of a system or service while keeping the rest operational.