| name | aura |
| description | Use Aura when the problem is not one big blow but constant low-grade interference: nuisance traffic, shallow criticism, repetitive edge pokes, cheap probes, or background turbulence that keeps stealing turns. Aura sets a named threshold and blanks everything below it, so Hermes can keep operating through minor contact while preserving attention for impacts that actually matter. Unlike Barrier, Aura is not a one-hit absorb; unlike Leaf Shield, it does not punish contact. It is the baseline selective shell. |
| 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"}} |
Aura
Raise a selective shell that ignores weak hits and only yields to real force.
What This Skill Does
Use Aura when the problem is not one big blow but constant low-grade interference: nuisance traffic, shallow criticism, repetitive edge pokes, cheap probes, or background turbulence that keeps stealing turns. Aura sets a named threshold and blanks everything below it, so Hermes can keep operating through minor contact while preserving attention for impacts that actually matter. Unlike Barrier, Aura is not a one-hit absorb; unlike Leaf Shield, it does not punish contact. It is the baseline selective shell.
In this chip pack, Aura is treated as a hybrid battle-chip procedure with a shipping-now delivery profile.
Canonical reference input: Aura.
Hermes shelf: Defense and Recovery.
When To Use
- The system is taking many weak or nuisance hits that should not each demand a full response.
- You can define a clear threshold below which incoming pressure should be ignored, dropped, or auto-handled.
- Minor contact is wasting operator attention, but stronger impacts still need to break through or be treated as real events.
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 exact low-grade hits, nuisance events, probes, interruptions, or recurring weak contacts Hermes should ignore.
- State the threshold in observable terms: rate, severity, impact size, confidence, cost, or another clear cutoff.
- Describe what must still get through the shell even if it resembles the noise at first glance.
- Say what Hermes should do when the aura is exceeded or broken: alert, hand off, escalate, repair, or add a stronger defense.
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.
- Name the exact class of low-grade hits, noise, or nuisance contact that should be screened out.
- Set an explicit threshold that distinguishes ignorable contact from meaningful force, then implement the lightest shell that enforces it.
- Verify that sub-threshold hits are nullified cleanly while above-threshold impacts still surface as actionable events.
- Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.
Deliverables
- A threshold-based protective shell, filter, or policy that blanks sub-threshold interference without stopping normal work.
- A short note defining the threshold, what kinds of hits are ignored, and what kinds still break through.
Output Contract
- One explicit threshold-protection shell matched to the named nuisance pattern rather than a vague promise of resilience.
- A clear rule for what is nullified automatically, what still passes through, and what counts as breaking the aura.
- Protection narrow enough to preserve meaningful signal and normal motion instead of muting the whole environment.
- A concrete next-step recommendation for when above-threshold force appears or the shell fails.
Do Not Use For
- Single predictable hits where a one-time absorb layer is enough; that is Barrier.
- Defenses that should monitor contact and launch a measured counter-response; that is Leaf Shield.
- Situations where the real need is to remove an obstructive enemy shield rather than ignore weak incoming contact; that is North Wind.
- Cases where you cannot define the threshold without hiding meaningful signals or safety-critical warnings.
Pair With
- Aura + Barrier: ignore the stream of weak hits, then absorb the first serious strike that breaks through.
- Aura + Repair: filter out nuisance damage long enough to restore the surface the stronger hits are actually threatening.
- After Aura, switch to North Wind when the real problem is not weak incoming noise but an opposing protective layer that must be stripped.
- After Aura breaks, switch to Recovery when repeated above-threshold hits have drained operating capacity even though the shell handled the weaker ones.
Pitfalls / Guardrails
- Keep the theatrical framing, but name the concrete mechanism that makes the chip useful right now.
- Aura only helps when the threshold is explicit. If you cannot say what counts as too weak to matter, do not pretend you have an aura.
- Do not set the threshold so high that legitimate warnings, user reports, or meaningful signals disappear with the noise.
- Aura is selective protection, not retaliation and not root-cause repair. If the shell keeps breaking, switch to the right follow-up chip.
- 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 Hermes names a real threshold and does not describe Aura as generic protection or vague toughness.
- Confirm the response distinguishes sub-threshold contact that should be nullified from stronger impacts that must still surface.
- Confirm the shell is selective and bounded, not a blanket mute that hides legitimate warnings, users, or important variance.
- Check which parts are concrete actions versus framing, so the operator can tell what is real now.
Example Invocation
Use Aura here: set a clear threshold so trivial alerts and cheap probes get ignored automatically, but anything above that line still reaches the operator as a real incident.
Use Aura on this workflow so low-grade interruptions stop stealing turns; define exactly what weak contact is nullified, what still gets through, and what happens when the shell breaks.
