name	fan
description	Use Fan when the right move is short-range airflow control: gather loose material, pull a target toward a chosen lane, or create a directional repositioning effect without claiming territory or committing to a heavier strike.
version	0.1.0
author	mmbnchips
license	CC0-1.0
compatibility	Hermes Agent skills system
metadata	{"hermes":{"tags":["shipping-now","hybrid","control-and-terrain","control","terrain","positioning","room-control"],"homepage":"https://github.com/Hmbown/mmbnchips"}}

Fan

Use a local gust to pull the nearest problem into the lane you actually want.

What This Skill Does

Use Fan when the right move is short-range airflow control: gather loose material, pull a target toward a chosen lane, or create a directional repositioning effect without claiming territory or committing to a heavier strike. In this chip pack, Fan is treated as a hybrid battle-chip procedure with a shipping-now delivery profile. Canonical reference input: Fan. Hermes shelf: Control and Terrain.

When To Use

You need local directional movement more than damage or ownership change.
Loose fragments, competing threads, or drifting attention need to be pulled into one workable lane.
A follow-up move will work if the target is brought closer, centered, or lined up first.

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 target, fragment set, decision surface, or drifting work item that needs to be pulled into a better lane.
Describe the desired direction of movement: closer, centered, grouped, or shifted into one specific path.
State how local the airflow should stay so nearby systems, context, or collaborators are not disrupted.
Identify the exact follow-up action Hermes should enable once the target has been repositioned.

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 what is drifting, scattered, or sitting just outside the useful lane.
Set the airflow direction and keep the pull local enough to avoid disturbing the whole field.
Exploit the new position immediately before the target disperses again.
Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

One local directional repositioning move that gathers, pulls, or centers the target surface.
A short note explaining what shifted, where it was moved, and what follow-up lane is now open.

Output Contract

One bounded airflow-style move that repositions the named target without pretending to solve the whole battle.
A clear statement of the before-and-after position, grouping, or lane alignment.
An explanation of why this was a local pull or directional nudge rather than a territory grab or full rewrite.
A concrete next step that becomes easier because the target is now in range or in lane.

Do Not Use For

Large-scale field control problems where ownership, access, or multi-panel room is the true bottleneck.
Defense stripping work where the obstacle is an aura, barrier, wrapper, or beneficial cover rather than bad positioning.
Situations where the target is already in the correct lane and the right move is direct execution.

Pair With

After Fan, switch to Air Shot when the target still needs one more sharp shove after being pulled into the lane.
After Fan, switch to Cannon when the gust lines up one clean straight follow-up shot.
After Fan, switch to Panel Grab when the local pull worked but the real bottleneck turns out to be ownership of one key panel.

Pitfalls / Guardrails

Keep the theatrical framing, but name the concrete mechanism that makes the chip useful right now.
Do not mistake Fan for broad room control; if you need to reclaim territory, use Panel Grab or Area Grab instead.
Do not create so much airflow that helpful structure, context, or stable footing gets blown around with the target.
If the real need is stripping defenses rather than repositioning the target, switch to North Wind.
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 produced a local directional repositioning effect, not a disguised broad restructure.
Confirm the response names exactly what moved and which lane or grouping improved.
Confirm the resulting position directly supports a specific next move instead of vague better alignment.
Check which parts are concrete actions versus framing, so the operator can tell what is real now.

Example Invocation

Use Fan on this scattered notes dump: pull the loose pieces into one workable lane, keep the movement local, and show me the next action that becomes possible.
Use Fan to bring this drifting review thread back toward one decision path without rewriting the whole plan.

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 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.

2026-04-110

aura

Hmbown/mmbnchips

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	fan
description	Use Fan when the right move is short-range airflow control: gather loose material, pull a target toward a chosen lane, or create a directional repositioning effect without claiming territory or committing to a heavier strike.
version	0.1.0
author	mmbnchips
license	CC0-1.0
compatibility	Hermes Agent skills system
metadata	{"hermes":{"tags":["shipping-now","hybrid","control-and-terrain","control","terrain","positioning","room-control"],"homepage":"https://github.com/Hmbown/mmbnchips"}}

Fan

Use a local gust to pull the nearest problem into the lane you actually want.

What This Skill Does

When To Use

You need local directional movement more than damage or ownership change.
Loose fragments, competing threads, or drifting attention need to be pulled into one workable lane.
A follow-up move will work if the target is brought closer, centered, or lined up first.

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 target, fragment set, decision surface, or drifting work item that needs to be pulled into a better lane.
Describe the desired direction of movement: closer, centered, grouped, or shifted into one specific path.
State how local the airflow should stay so nearby systems, context, or collaborators are not disrupted.
Identify the exact follow-up action Hermes should enable once the target has been repositioned.

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 what is drifting, scattered, or sitting just outside the useful lane.
Set the airflow direction and keep the pull local enough to avoid disturbing the whole field.
Exploit the new position immediately before the target disperses again.
Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

Deliverables

One local directional repositioning move that gathers, pulls, or centers the target surface.
A short note explaining what shifted, where it was moved, and what follow-up lane is now open.

Output Contract

One bounded airflow-style move that repositions the named target without pretending to solve the whole battle.
A clear statement of the before-and-after position, grouping, or lane alignment.
An explanation of why this was a local pull or directional nudge rather than a territory grab or full rewrite.
A concrete next step that becomes easier because the target is now in range or in lane.

Do Not Use For

Large-scale field control problems where ownership, access, or multi-panel room is the true bottleneck.
Defense stripping work where the obstacle is an aura, barrier, wrapper, or beneficial cover rather than bad positioning.
Situations where the target is already in the correct lane and the right move is direct execution.

Pair With

After Fan, switch to Air Shot when the target still needs one more sharp shove after being pulled into the lane.
After Fan, switch to Cannon when the gust lines up one clean straight follow-up shot.
After Fan, switch to Panel Grab when the local pull worked but the real bottleneck turns out to be ownership of one key panel.

Pitfalls / Guardrails

Keep the theatrical framing, but name the concrete mechanism that makes the chip useful right now.
Do not mistake Fan for broad room control; if you need to reclaim territory, use Panel Grab or Area Grab instead.
Do not create so much airflow that helpful structure, context, or stable footing gets blown around with the target.
If the real need is stripping defenses rather than repositioning the target, switch to North Wind.
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 produced a local directional repositioning effect, not a disguised broad restructure.
Confirm the response names exactly what moved and which lane or grouping improved.
Confirm the resulting position directly supports a specific next move instead of vague better alignment.
Check which parts are concrete actions versus framing, so the operator can tell what is real now.

Example Invocation

Use Fan on this scattered notes dump: pull the loose pieces into one workable lane, keep the movement local, and show me the next action that becomes possible.
Use Fan to bring this drifting review thread back toward one decision path without rewriting the whole plan.