| name | north-wind |
| description | Use North Wind when progress is blocked by protective layering rather than distance: aura, barrier, wrapper, soft shield, ceremonial safety language, or stacked cover that keeps the real issue from being touched. North Wind strips the protection cleanly so a truthful next move can land. |
| 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"}} |
North Wind
Blow away beneficial cover so the real target is exposed again.
What This Skill Does
Use North Wind when progress is blocked by protective layering rather than distance: aura, barrier, wrapper, soft shield, ceremonial safety language, or stacked cover that keeps the real issue from being touched. North Wind strips the protection cleanly so a truthful next move can land.
In this chip pack, North Wind is treated as a hybrid battle-chip procedure with a shipping-now delivery profile.
Canonical reference input: North Wind.
Hermes shelf: Defense and Recovery.
When To Use
- A target is reachable in principle, but beneficial cover or layered protections are soaking every meaningful hit.
- Temporary safeguards, wrappers, or comfort layers have outlived their purpose and now block honest contact.
- You need to expose the underlying surface before choosing whether to cut, repair, inspect, or attack.
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 protective layer, buffer, barrier, aura, wrapper, or beneficial cover that is stopping real contact.
- State why that protection is now obstructive rather than necessary.
- Describe what underlying surface, issue, or target Hermes expects to expose once the layer is gone.
- Identify any protections that must remain untouched because they are still legitimate safeguards.
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.
- Identify the exact protective layer, aura, or shielding behavior that is preventing real contact.
- Strip only the layers that are distorting the board, leaving legitimate safety requirements named and intact when they truly must remain.
- Reassess the newly exposed surface immediately and hand off to the right follow-up chip.
- Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.
Deliverables
- A clean removal of the named barrier, aura, wrapper, or stacked cover that is blocking meaningful action.
- A short note explaining what protection was removed, what remains, and what is now exposed.
Output Contract
- A precise dispelling move that removes the named protective layer or stacked cover without expanding into unrelated demolition.
- A clear distinction between protections removed, protections intentionally preserved, and the newly exposed target surface.
- A short explanation of why the stripped layer had become obstructive rather than protective.
- A concrete recommendation for the next chip now that the barrier or aura is gone.
Do Not Use For
- Cases where the obstacle is distance, alignment, or drift rather than layered protection.
- Indiscriminate teardown of safety mechanisms that are still necessary and correctly placed.
- Problems where the exposed target is already known and can be acted on directly without first dispelling cover.
Pair With
- After North Wind, switch to Cannon when removing the barrier reveals one clean direct shot.
- After North Wind, switch to Sword when the stripped cover exposes one local block that should now be cut out cleanly.
- After North Wind, switch to Repair when the removed shielding reveals damaged infrastructure that needs restoration instead of attack.
Pitfalls / Guardrails
- Keep the theatrical framing, but name the concrete mechanism that makes the chip useful right now.
- Do not use North Wind to tear down protections that are still genuinely required for safety, legality, or system integrity.
- Do not confuse exposure with resolution; after the shield is gone, Hermes still needs the right follow-up chip.
- If the real need is only to reposition the target locally, use Fan instead of stripping protections.
- 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 identified a real protective layer or aura and removed that layer specifically, not the whole surrounding system.
- Confirm the response distinguishes obstructive cover from protections that still need to remain in place.
- Confirm the newly exposed target or surface is explicitly named and actionable.
- Check which parts are concrete actions versus framing, so the operator can tell what is real now.
Example Invocation
Use North Wind on this workflow: strip away the temporary wrappers and protective language that are preventing honest review, but keep any safeguards that are still truly required.
Use North Wind to clear the layered barrier around this issue so we can see the real target surface and choose the right next chip.
