Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

cure-wounds

Estrellas98

Forks12

Actualizado5 de abril de 2026, 03:15

Cure Wounds is the hotfix spell: immediate triage to stop bleeding and restore function. It is NOT root-cause analysis, refactoring, redesign, or long-term remediation. The goal is the minimum viable fix that stops the damage NOW. Deeper investigation comes after.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

Hmbown

Hmbown/Wizards-of-the-Ghosts

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

SKILL.md

readonly

name	cure-wounds
description	Cure Wounds is the hotfix spell: immediate triage to stop bleeding and restore function. It is NOT root-cause analysis, refactoring, redesign, or long-term remediation. The goal is the minimum viable fix that stops the damage NOW. Deeper investigation comes after.
user-invocable	true

Cure Wounds

Apply a targeted fix to stop the bleeding on an active problem.

Overview

Cure Wounds is interpreted here as a metaphorical spell with a shipping-now execution model.

Canonical source: Cure Wounds (spell)

Provider target: OpenClaw

When To Use

Active breakage: crashes, errors, failures, outages, data loss, blocked users
Urgency markers: "right now", "immediately", "production down", "losing money", "users can't", "team blocked"
Time-sensitive impact: revenue loss, customer complaints, SLA breach, on-call pages
Recent-change correlation: "after the deploy", "since the update", "broke 10 minutes ago"
Minimum-intervention request: "stop the bleeding", "quick fix", "get it working", "restore function"

Workflow

Identify the symptom: What exactly is failing? What error, crash, or outage is happening?
Diagnose the proximate cause: What changed or failed to produce this breakage? Check recent deploys, config changes, or environmental shifts.
Apply the minimum fix: The smallest change that restores function. Rollback, patch, restart, or reconfigure — whatever stops the bleeding with least risk.
Verify and document: Confirm the fix works. Note what caused the breakage and whether root-cause analysis is still needed.

Deliverables

The fix: the specific change that stops the bleeding.
A brief note on what caused the breakage and whether deeper investigation is needed.

Guardrails

Cure Wounds is triage, not treatment. Always flag whether deeper investigation is needed after the fix.
Preserve evidence: the minimum fix must not make the underlying problem harder to diagnose.
If the fix requires significant redesign or architectural change, this is the wrong spell.
Do not use for: Planned work: migrations, refactors, feature development, schema redesigns
Do not use for: Long-term degradation: "slowly getting worse", "needs comprehensive plan", "technical debt"
Do not use for: Presentation/formatting: reformatting logs, cleaning output, improving readability
Do not use for: Trivial typos: single-character corrections in config (use basic editing, not triage)
Do not use for: Communication only: "send a message", "notify the team", "update status"
Do not use for: Feature flag state issues: configuration toggles without active breakage
Do not use for: Root-cause analysis requests: "why did this happen", "investigate the underlying issue"

Default Invocation

Use $cure-wounds to diagnose and fix this [broken build/failing service/production issue] with the minimum change needed to restore function.

Más de este repositorio

mismo repositorio

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	cure-wounds
description	Cure Wounds is the hotfix spell: immediate triage to stop bleeding and restore function. It is NOT root-cause analysis, refactoring, redesign, or long-term remediation. The goal is the minimum viable fix that stops the damage NOW. Deeper investigation comes after.
user-invocable	true

Cure Wounds

Apply a targeted fix to stop the bleeding on an active problem.

Overview

Cure Wounds is interpreted here as a metaphorical spell with a shipping-now execution model.

Canonical source: Cure Wounds (spell)

Provider target: OpenClaw

When To Use

Active breakage: crashes, errors, failures, outages, data loss, blocked users
Urgency markers: "right now", "immediately", "production down", "losing money", "users can't", "team blocked"
Time-sensitive impact: revenue loss, customer complaints, SLA breach, on-call pages
Recent-change correlation: "after the deploy", "since the update", "broke 10 minutes ago"
Minimum-intervention request: "stop the bleeding", "quick fix", "get it working", "restore function"

Workflow

Identify the symptom: What exactly is failing? What error, crash, or outage is happening?
Diagnose the proximate cause: What changed or failed to produce this breakage? Check recent deploys, config changes, or environmental shifts.
Apply the minimum fix: The smallest change that restores function. Rollback, patch, restart, or reconfigure — whatever stops the bleeding with least risk.
Verify and document: Confirm the fix works. Note what caused the breakage and whether root-cause analysis is still needed.

Deliverables

The fix: the specific change that stops the bleeding.
A brief note on what caused the breakage and whether deeper investigation is needed.

Guardrails

Cure Wounds is triage, not treatment. Always flag whether deeper investigation is needed after the fix.
Preserve evidence: the minimum fix must not make the underlying problem harder to diagnose.
If the fix requires significant redesign or architectural change, this is the wrong spell.
Do not use for: Planned work: migrations, refactors, feature development, schema redesigns
Do not use for: Long-term degradation: "slowly getting worse", "needs comprehensive plan", "technical debt"
Do not use for: Presentation/formatting: reformatting logs, cleaning output, improving readability
Do not use for: Trivial typos: single-character corrections in config (use basic editing, not triage)
Do not use for: Communication only: "send a message", "notify the team", "update status"
Do not use for: Feature flag state issues: configuration toggles without active breakage
Do not use for: Root-cause analysis requests: "why did this happen", "investigate the underlying issue"

Default Invocation

Use $cure-wounds to diagnose and fix this [broken build/failing service/production issue] with the minimum change needed to restore function.