Run any Skill in Manus with one click

curse-shield

Stars0

Forks0

UpdatedApril 11, 2026 at 22:30

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

Hmbown

Hmbown/mmbnchips

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Information Security AnalystsComputer and Mathematical Occupations·SOC 15-1212

SKILL.md

readonly

More from this repository

same repository

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.

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

elec-aura

Hmbown/mmbnchips

Use Elec Aura when the problem is not raw heat but constant probing, interruption, and low-commitment contact that keeps stealing focus or touching the work without paying a real cost. Unlike a plain Aura that mostly blanks weak hits, Elec Aura makes contact loud: minor touches get rejected, surfaced, or bounced, and anything that persists reveals itself fast. This makes it a strong Hermes skill for preserving a critical focus window or defended operating edge under active interference.

2026-04-110

name

curse-shield

description

Curse Shield

Raise a shield that protects the target and curses whatever makes hostile contact with it.

Overview

This is the secondary Codex compatibility rendering of a hybrid battle-chip pattern with a shipping-now execution model.

Canonical chip family: Curse Shield Codex shelf: Defense and Recovery Provider target: Codex compatibility surface.

When To Use

You need a protective layer that does more than soak damage: hostile contact should leave a durable mark or penalty behind.
The same actor, process, or source keeps touching a protected surface and should become easier to track, rate-limit, isolate, or distrust after doing so.
Immediate retaliation is less useful than making future contact progressively more expensive, visible, or constrained.

Workflow

Name the exact surface, boundary, or workflow Hermes should shield and define what counts as hostile contact with it.
Choose the curse Hermes should attach to contact: mark, quarantine, audit trail, trust reduction, cooldown, rate limit, or another persistent penalty that survives the initial hit.
Apply the shield so it protects the defended surface now while ensuring any hostile toucher leaves carrying the curse into later interactions.

Deliverables

One bounded defensive layer around a named surface that both protects it and applies a durable consequence to hostile contact.
A short note defining the curse itself: what mark or penalty is applied, how long it lasts, and how operators should use that information afterward.

Guardrails

Curse Shield must defend first. If there is no real protected surface, you are inventing a curse mechanic without a shield.
The curse should persist beyond the triggering touch, but it must stay proportionate and reviewable; do not smuggle in uncontrolled retaliation.
Do not confuse a cursed marker with general suspicion. The penalty needs a concrete operational effect, expiry, or cleanse condition.
If you only need one reactive hit back on the next attack, use Anti Damage. If you need a threshold shell that ignores weak hits, use Aura. If you need a defensive wrapper that mainly counters on release, use Leaf Shield.

Default Invocation

Use Curse Shield to defend one named surface and make hostile contact leave a durable mark, restriction, or audit burden on the toucher, with a clear expiry or cleanse path.