| name | leaf-shield |
| description | Use Leaf Shield when you need sustained, active protection that makes aggression costly. The defense orbits your work and absorbs incoming damage; when triggered, it launches outward as a measured counter. |
| version | 0.1.0 |
| author | mmbnchips |
| license | CC0-1.0 |
| compatibility | Hermes Agent skills system |
| metadata | {"hermes":{"tags":["shipping-now","hybrid","defense-and-recovery","defense","recovery","stabilization","survivability"],"homepage":"https://github.com/Hmbown/mmbnchips"}} |
Leaf Shield
Orbiting guard that punishes whatever hits it.
What This Skill Does
Use Leaf Shield when you need sustained, active protection that makes aggression costly. The defense orbits your work and absorbs incoming damage; when triggered, it launches outward as a measured counter.
In this chip pack, Leaf Shield is treated as a hybrid battle-chip procedure with a shipping-now delivery profile.
Canonical reference input: Leaf Shield.
Hermes shelf: Defense and Recovery.
When To Use
- You need a defensive wrapper that actively monitors and responds to incidents, not just passively absorbs them.
- An adversarial environment means the defender should make every unwanted touch expensive for the attacker.
- You want protection that doubles as a deterrent: logging, alerting, or counteracting when triggered.
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.
Procedure
- Restate the target, success condition, and no-touch boundaries before you spend the chip.
- Identify the surface or process that needs sustained protection and define what counts as a hit against it.
- Wrap it with an orbiting defensive layer: structured logging, alert triggers, or automated incident responses.
- Configure the counter-release: when the shield absorbs a hit, launch a measured response.
- Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.
Deliverables
- A defensive wrapper around the target that monitors, absorbs, and responds to threats.
- A counter-attack playbook triggered by shield contact.
Pitfalls / Guardrails
- Keep the theatrical framing, but name the concrete mechanism that makes the chip useful right now.
- The primary purpose is protection, not retaliation. The counter-release deters future contact; it is not a license to go on offense.
- Leaf Shield absorbs a limited number of hits before launching. Know the threshold and plan for what happens after release.
- If you only need passive absorption, use Barrier. If you only need a reactive counter, use Anti Damage.
- 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 which parts are concrete actions versus framing, so the operator can tell what is real now.
Example Invocation
/leaf-shield wrap the target in orbiting protection that monitors for hits and launches a measured counter-response when triggered
