القائمة
Use Long Sword when the problem is visible locally but the fix must extend further — across file boundaries, into deeper call stacks, or through intermediary layers that a normal Sword cannot reach.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
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 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.
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.
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.
| name | long-sword |
| description | Use Long Sword when the problem is visible locally but the fix must extend further — across file boundaries, into deeper call stacks, or through intermediary layers that a normal Sword cannot reach. |
| version | 0.1.0 |
| author | mmbnchips |
| license | CC0-1.0 |
| compatibility | Hermes Agent skills system |
| metadata | {"hermes":{"tags":["shipping-now","metaphorical","direct-fire-and-breach","direct-fire","offense","breach","decisive-action"],"homepage":"https://github.com/Hmbown/mmbnchips"}} |
Reach past the first layer and cut through to the real target.
Use Long Sword when the problem is visible locally but the fix must extend further — across file boundaries, into deeper call stacks, or through intermediary layers that a normal Sword cannot reach. In this chip pack, Long Sword is treated as a metaphorical battle-chip procedure with a shipping-now delivery profile. Canonical reference input: Long Sword. Hermes shelf: Direct Fire and Breach.
/long-sword trace the problem past the local surface and cut through to the root cause: edit the deepest layer that needs to change, then propagate the fix outward, verifying each layer stays intact