Run any Skill in Manus with one click

bestow-curse

Stars98

Forks12

UpdatedApril 5, 2026 at 03:15

Bestow Curse saddles a target with a lasting disadvantage. The real-world version is constraint injection: deliberately adding friction, limitations, or handicaps to see how a system, process, or team adapts. This is the skill of resilience testing through artificial adversity — bandwidth throttling, feature removal, resource reduction.

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/Wizards-of-the-Ghosts

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	bestow-curse
description	Bestow Curse saddles a target with a lasting disadvantage. The real-world version is constraint injection: deliberately adding friction, limitations, or handicaps to see how a system, process, or team adapts. This is the skill of resilience testing through artificial adversity — bandwidth throttling, feature removal, resource reduction.
user-invocable	true

Bestow Curse

Add persistent constraints or friction to test how a system copes.

Overview

Bestow Curse is interpreted here as a metaphorical spell with a prototype execution model.

Canonical source: Bestow Curse (spell)

Provider target: OpenClaw

When To Use

You want to test how a system performs under degraded conditions before those conditions occur naturally.
A process is too dependent on ideal circumstances and you need to know its failure boundaries.

Workflow

Identify the system or process to stress-test through constraint injection.
Design the curse: what specific limitation, degradation, or friction to introduce.
Define the measurement criteria: how will you know if the system coped well or poorly?
Deliver the constraint injection plan with expected outcomes and rollback procedures.

Deliverables

A constraint injection plan: what to degrade, by how much, for how long.
Success and failure criteria: what coping looks like vs. what breaking looks like.

Guardrails

Constraint injection must be reversible. The curse should reveal weaknesses, not create permanent damage.
Do not inject constraints into production systems without authorization and rollback plans.

Default Invocation

Use $bestow-curse to design a constraint injection test for this [system/process]. What happens when we deliberately degrade it?

More from this repository

same repository

mage-hand

Hmbown/Wizards-of-the-Ghosts

Use this skill for small, careful remote manipulations where dexterity matters more than force.

2026-04-0598

unseen-servant

Hmbown/Wizards-of-the-Ghosts

Use this spell when you need a tireless helper that organizes, tidies, triages, and maintains without requiring your constant attention.

2026-04-0598

arcana

Hmbown/Wizards-of-the-Ghosts

In D&D, Arcana is knowledge of magic, its traditions, symbols, and mechanisms. The real-world version is deep technical literacy: understanding how software architectures work, what protocols do at the wire level, how APIs behave beyond their documentation, and what the actual mechanisms are behind the abstractions everyone else takes on faith.

2026-04-0598

mirage-arcane

Hmbown/Wizards-of-the-Ghosts

In D&D, Mirage Arcane goes beyond Hallucinatory Terrain — the illusory terrain actually has substance. You can walk on illusory bridges, feel illusory walls. The real-world version is the deep simulation: digital twins, high-fidelity synthetic environments, test harnesses so realistic that systems under test cannot distinguish them from production. Mirage Arcane is the most dangerous illusion because its power is in being indistinguishable from reality. That same power makes it the most useful for stress testing, training, and scenario planning — but it requires the strongest labeling discipline.

2026-04-0598

project-image

Hmbown/Wizards-of-the-Ghosts

In D&D, Project Image creates an illusory copy of yourself at a distant location — you can see through its eyes, speak through its mouth, and cast spells through it. The real-world version is remote presence: avatars, recorded video stand-ins, bot representations, asynchronous video messages. Project Image is the spell for being in two places at once — attending a meeting via avatar while working on something else, leaving a recorded presence in a channel, or deploying an automated representative that speaks with your voice and authority within defined limits.

2026-04-0598

acrobatics

Hmbown/Wizards-of-the-Ghosts

Use this skill when the work is a choreography problem: brittle sequencing, async handoffs, or constrained flows that must stay upright end to end. It shines on API dances, dependency ordering, and recovery logic where grace matters more than brute force.

2026-04-0598

name	bestow-curse
description	Bestow Curse saddles a target with a lasting disadvantage. The real-world version is constraint injection: deliberately adding friction, limitations, or handicaps to see how a system, process, or team adapts. This is the skill of resilience testing through artificial adversity — bandwidth throttling, feature removal, resource reduction.
user-invocable	true

Bestow Curse

Add persistent constraints or friction to test how a system copes.

Overview

Bestow Curse is interpreted here as a metaphorical spell with a prototype execution model.

Canonical source: Bestow Curse (spell)

Provider target: OpenClaw

When To Use

You want to test how a system performs under degraded conditions before those conditions occur naturally.
A process is too dependent on ideal circumstances and you need to know its failure boundaries.

Workflow

Identify the system or process to stress-test through constraint injection.
Design the curse: what specific limitation, degradation, or friction to introduce.
Define the measurement criteria: how will you know if the system coped well or poorly?
Deliver the constraint injection plan with expected outcomes and rollback procedures.

Deliverables

A constraint injection plan: what to degrade, by how much, for how long.
Success and failure criteria: what coping looks like vs. what breaking looks like.

Guardrails

Constraint injection must be reversible. The curse should reveal weaknesses, not create permanent damage.
Do not inject constraints into production systems without authorization and rollback plans.

Default Invocation

Use $bestow-curse to design a constraint injection test for this [system/process]. What happens when we deliberately degrade it?