ワンクリックでManusで任意のスキルを実行

blindness-deafness

スター98

フォーク12

更新日2026年4月5日 03:15

In D&D, Blindness/Deafness selectively removes one sense — the target can still act but loses critical awareness. The real-world version is selective channel muting: blocking a process from seeing certain inputs (input filtering, API response redaction), deafening it to specific signals (suppressing webhooks, ignoring certain event streams), or cutting telemetry so a system operates without awareness of a specific data source. Unlike containment (forcecage) which restricts everything, Blindness/Deafness surgically removes one information channel while leaving the rest intact.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

Hmbown

Hmbown/Wizards-of-the-Ghosts

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

Blindness/Deafness

Cut a system's eyes or ears — let it run, but blind to specific inputs or deaf to specific signals.

Overview

Blindness/Deafness is interpreted here as a literal spell with a shipping-now execution model.

Canonical source: Blindness/Deafness (spell)

Provider target: OpenClaw

When To Use

A process should keep running, but one input, signal, or telemetry source needs to be removed from its awareness.
You need to suppress a specific webhook, event stream, API field, or sensor channel without containing the whole system.
You want to test or control behavior under selective sensory loss rather than full isolation.

Workflow

Identify the exact channel to mute and the decisions the system currently makes from it.
Verify the channel is not safety-critical or load-bearing for core correctness.
Choose the muting mechanism: input filtering, response redaction, event suppression, or telemetry cutoff.
Define restoration triggers, operators, and monitoring so everyone knows the system is partially blind or deaf.
Return the channel-muting plan with expected behavioral changes and rollback steps.

Deliverables

A selective channel-muting plan naming exactly what input, signal, or telemetry was removed.
A dependency note explaining what decisions will proceed without that awareness channel.
Restoration triggers, rollback steps, and operator-facing documentation.

Guardrails

Muting a channel the system needs for safety decisions is dangerous. Verify the blinded input is not load-bearing before cutting it.
Always document what was muted and set a restoration trigger. A system that forgets it is blind will make confident wrong decisions.

Default Invocation

Use $blindness-deafness to selectively blind or deafen this system to one input, signal, or telemetry source while keeping the rest of it running safely.

このリポジトリの他の Skills

同じリポジトリ

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

blindness-deafness

description

Blindness/Deafness

Cut a system's eyes or ears — let it run, but blind to specific inputs or deaf to specific signals.

Overview

Blindness/Deafness is interpreted here as a literal spell with a shipping-now execution model.

Canonical source: Blindness/Deafness (spell)

Provider target: OpenClaw

When To Use

A process should keep running, but one input, signal, or telemetry source needs to be removed from its awareness.
You need to suppress a specific webhook, event stream, API field, or sensor channel without containing the whole system.
You want to test or control behavior under selective sensory loss rather than full isolation.

Workflow

Identify the exact channel to mute and the decisions the system currently makes from it.
Verify the channel is not safety-critical or load-bearing for core correctness.
Choose the muting mechanism: input filtering, response redaction, event suppression, or telemetry cutoff.
Define restoration triggers, operators, and monitoring so everyone knows the system is partially blind or deaf.
Return the channel-muting plan with expected behavioral changes and rollback steps.

Deliverables

A selective channel-muting plan naming exactly what input, signal, or telemetry was removed.
A dependency note explaining what decisions will proceed without that awareness channel.
Restoration triggers, rollback steps, and operator-facing documentation.

Guardrails

Muting a channel the system needs for safety decisions is dangerous. Verify the blinded input is not load-bearing before cutting it.
Always document what was muted and set a restoration trigger. A system that forgets it is blind will make confident wrong decisions.

Default Invocation

Use $blindness-deafness to selectively blind or deafen this system to one input, signal, or telemetry source while keeping the rest of it running safely.