name	aqua-aura
description	Use Aqua Aura when the real threat is heat: escalating pressure, bursty contention, emotional overtemperature, or rapid-fire noise that is making clean operation impossible. Unlike a plain Aura that simply blanks weaker hits, Aqua Aura diffuses and cools them so Hermes can keep moving without matching the room's panic tempo.
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"}}

Aqua Aura

Wrap the work in a cooling sheath that turns sharp incoming pressure into slower, more manageable flow.

What This Skill Does

Use Aqua Aura when the real threat is heat: escalating pressure, bursty contention, emotional overtemperature, or rapid-fire noise that is making clean operation impossible. Unlike a plain Aura that simply blanks weaker hits, Aqua Aura diffuses and cools them so Hermes can keep moving without matching the room's panic tempo. In this chip pack, Aqua Aura is treated as a hybrid battle-chip procedure with a shipping-now delivery profile. Canonical reference input: Aqua Aura. Hermes shelf: Defense and Recovery.

When To Use

A workflow is being degraded by overheated urgency, burst traffic, or repeated sharp interruptions rather than one decisive heavy strike.
You need to keep operating while reducing temperature, friction, and escalation across the immediate exchange.
The right move is to absorb and smooth incoming pressure into a calmer, more tractable flow instead of freezing the board or trading hits directly.

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 overheated surface Hermes needs to cool: incident channel, approval queue, review thread, dependency chain, live ops path, or interpersonal exchange.
Describe what the incoming heat looks like in practice: bursty requests, panic edits, argument spikes, retry storms, alert floods, or deadline pressure.
State what level of continued motion you still need while the aura is up: steady throughput, triage-only, careful progress, or observation with minimal escalation.
Say how you will tell the pressure has been cooled enough to hand off to the next chip.

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 hot surface: queue, review thread, incident lane, operator exchange, or execution path that is running too heated to handle cleanly.
Identify which incoming pressures should be cooled, rate-limited, reframed, or spread out instead of answered at full temperature.
Wrap the work in the smallest viable cooling layer, then use the calmer window to restore orderly motion and decide the next grounded move.
Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

A cooling or pressure-diffusing operating layer that reduces immediate burst intensity without stopping all motion.
A short note explaining what heat sources were damped, what still remains dangerous, and what calmer operating mode is now possible.

Output Contract

A specific cooling, buffering, or pressure-smoothing move matched to the named overheated surface.
A clear distinction between what Aqua Aura damped, what it merely delayed, and what can still punch through the shield.
A practical calmer operating posture Hermes can use immediately while the aura holds.
A recommendation for the next chip once the room is cool enough to act cleanly.

Do Not Use For

One big predictable hit that should be absorbed with Barrier rather than diffused over time.
Protected work zones that need explicit boundaries and safe operating space, which are better handled by Sanctuary.
Cases where the issue is hidden behind too much shielding and the right move is to dispel cover with North Wind.

Pair With

Aqua Aura + Recovery: cool the overheated exchange first, then restore lost operator capacity once the room stops spiking.
Aqua Aura + Repair: reduce burst pressure on the damaged surface, then make the direct fix without working in a panic storm.
Aqua Aura + Ice Stage: cool the field first, then deliberately change the traction once the operator can think clearly about who should slide.

Pitfalls / Guardrails

Keep the theatrical framing, but name the concrete mechanism that makes the chip useful right now.
Aqua Aura diffuses pressure; it does not solve the root cause of the heat by itself.
Do not mistake calmer pacing for full safety if a truly heavy strike can still break through.
If the room needs a hard boundary or a declared safe zone, switch to Barrier or Sanctuary instead of pretending cooling alone is enough.
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 response identifies a genuinely overheated or bursty pressure pattern rather than using Aqua theming as flavor only.
Confirm the proposed shield changes tempo and temperature, not merely blocks one hit or declares vague safety.
Confirm the output tells the operator what risks were cooled, what risks remain, and when to switch chips.
Check which parts are concrete actions versus framing, so the operator can tell what is real now.

Example Invocation

Use Aqua Aura on this incident thread: cool the bursty pressure, smooth the incoming requests, and tell me what calmer operating mode we get while the shield holds.
Use Aqua Aura here so we can keep moving through this overheated review cycle without matching every interruption at full temperature.

Más de este repositorio

mismo repositorio

black-barrier

Hmbown/mmbnchips

Use Black Barrier when ordinary buffering is too soft and thresholding alone is too permissive. The problem is not just one incoming hit, or a stream of weak noise, but contact that should have to prove itself before it reaches the work at all: ambiguous requests, half-authorized changes, untrusted touchpoints, speculative interruptions, or access that has not earned the right to cross the perimeter. Black Barrier establishes a denser selective shell around a critical surface. Unlike Barrier, it is not a one-hit absorb. Unlike Aura, it does not merely ignore weak impacts below a threshold. It enforces a stricter admission rule: only declared, validated, high-confidence contact gets through, and everything else is refused, deferred, or held outside until it can justify entry.

2026-04-110

curse-shield

Hmbown/mmbnchips

Use Curse Shield when Hermes should protect a surface in a way that makes contact linger on the attacker. The shield is not just there to absorb the next hit or throw an immediate counter; it tags hostile touch with a lasting penalty, mark, or contamination that follows the offender after impact. In practice, Curse Shield is for defended surfaces that impose audit burden, throttling, suspicion, reduced trust, quarantine, follow-up scrutiny, or another durable consequence on whatever keeps pressing into them.

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.

2026-04-110

name	aqua-aura
description	Use Aqua Aura when the real threat is heat: escalating pressure, bursty contention, emotional overtemperature, or rapid-fire noise that is making clean operation impossible. Unlike a plain Aura that simply blanks weaker hits, Aqua Aura diffuses and cools them so Hermes can keep moving without matching the room's panic tempo.
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"}}

Aqua Aura

Wrap the work in a cooling sheath that turns sharp incoming pressure into slower, more manageable flow.

What This Skill Does

When To Use

A workflow is being degraded by overheated urgency, burst traffic, or repeated sharp interruptions rather than one decisive heavy strike.
You need to keep operating while reducing temperature, friction, and escalation across the immediate exchange.
The right move is to absorb and smooth incoming pressure into a calmer, more tractable flow instead of freezing the board or trading hits directly.

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 overheated surface Hermes needs to cool: incident channel, approval queue, review thread, dependency chain, live ops path, or interpersonal exchange.
Describe what the incoming heat looks like in practice: bursty requests, panic edits, argument spikes, retry storms, alert floods, or deadline pressure.
State what level of continued motion you still need while the aura is up: steady throughput, triage-only, careful progress, or observation with minimal escalation.
Say how you will tell the pressure has been cooled enough to hand off to the next chip.

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 hot surface: queue, review thread, incident lane, operator exchange, or execution path that is running too heated to handle cleanly.
Identify which incoming pressures should be cooled, rate-limited, reframed, or spread out instead of answered at full temperature.
Wrap the work in the smallest viable cooling layer, then use the calmer window to restore orderly motion and decide the next grounded move.
Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

A cooling or pressure-diffusing operating layer that reduces immediate burst intensity without stopping all motion.
A short note explaining what heat sources were damped, what still remains dangerous, and what calmer operating mode is now possible.

Output Contract

A specific cooling, buffering, or pressure-smoothing move matched to the named overheated surface.
A clear distinction between what Aqua Aura damped, what it merely delayed, and what can still punch through the shield.
A practical calmer operating posture Hermes can use immediately while the aura holds.
A recommendation for the next chip once the room is cool enough to act cleanly.

Do Not Use For

One big predictable hit that should be absorbed with Barrier rather than diffused over time.
Protected work zones that need explicit boundaries and safe operating space, which are better handled by Sanctuary.
Cases where the issue is hidden behind too much shielding and the right move is to dispel cover with North Wind.

Pair With

Aqua Aura + Recovery: cool the overheated exchange first, then restore lost operator capacity once the room stops spiking.
Aqua Aura + Repair: reduce burst pressure on the damaged surface, then make the direct fix without working in a panic storm.
Aqua Aura + Ice Stage: cool the field first, then deliberately change the traction once the operator can think clearly about who should slide.

Pitfalls / Guardrails

Keep the theatrical framing, but name the concrete mechanism that makes the chip useful right now.
Aqua Aura diffuses pressure; it does not solve the root cause of the heat by itself.
Do not mistake calmer pacing for full safety if a truly heavy strike can still break through.
If the room needs a hard boundary or a declared safe zone, switch to Barrier or Sanctuary instead of pretending cooling alone is enough.
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 response identifies a genuinely overheated or bursty pressure pattern rather than using Aqua theming as flavor only.
Confirm the proposed shield changes tempo and temperature, not merely blocks one hit or declares vague safety.
Confirm the output tells the operator what risks were cooled, what risks remain, and when to switch chips.
Check which parts are concrete actions versus framing, so the operator can tell what is real now.

Example Invocation

Use Aqua Aura on this incident thread: cool the bursty pressure, smooth the incoming requests, and tell me what calmer operating mode we get while the shield holds.
Use Aqua Aura here so we can keep moving through this overheated review cycle without matching every interruption at full temperature.