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

feeblemind

スター98

フォーク12

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

In D&D, Feeblemind crushes a creature's Intelligence and Charisma to near-zero — leaving them alive but barely functional. The real-world version is deliberate capability reduction: putting a system into safe mode, stripping an overpowered tool down to basic functions, reducing attack surface by removing features. Feeblemind is not punishment — it is the recognition that sometimes a system at full capability is more dangerous than a system at reduced capability. Restricted shells, read-only modes, feature-stripped emergency interfaces.

インストール

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

Manusで実行

ソース

Hmbown

Hmbown/Wizards-of-the-Ghosts

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

ダウンロード

Manusで実行

Feeblemind

Strip a system down to minimal capability when full power is too dangerous.

Overview

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

Canonical source: Feeblemind (spell)

Provider target: OpenClaw

When To Use

A system at full capability poses a risk that outweighs the cost of reduced functionality.
You need to reduce attack surface by stripping non-essential features.
A tool or service should be put into safe mode or restricted operation during an incident or investigation.

Workflow

Identify which capabilities must be preserved (minimal viable function) and which can be safely stripped.
Implement the capability reduction: safe mode, restricted shell, feature stripping, read-only lock.
Verify the reduced system still performs its essential function.
Document what was removed and the conditions under which full capability should be restored.
Set a review point — feeblemind should be temporary unless the full-capability version is permanently retired.

Deliverables

A capability reduction plan: what stays, what goes, and why.
Confirmation that minimal viable function is preserved.
Restoration criteria: what conditions must be met to return to full capability.

Guardrails

Feeblemind must preserve minimal viable function. Reducing a system to zero capability is Power Word Kill, not Feeblemind.
Capability reduction of user-facing systems requires clear communication about what changed and when it will be restored.
Do not use Feeblemind to permanently hobble systems that should instead be redesigned or decommissioned.

Default Invocation

Use $feeblemind to reduce a system to minimal capability — stripping non-essential features to limit risk while preserving core function.

このリポジトリの他の 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	feeblemind
description	In D&D, Feeblemind crushes a creature's Intelligence and Charisma to near-zero — leaving them alive but barely functional. The real-world version is deliberate capability reduction: putting a system into safe mode, stripping an overpowered tool down to basic functions, reducing attack surface by removing features. Feeblemind is not punishment — it is the recognition that sometimes a system at full capability is more dangerous than a system at reduced capability. Restricted shells, read-only modes, feature-stripped emergency interfaces.
user-invocable	true

Feeblemind

Strip a system down to minimal capability when full power is too dangerous.

Overview

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

Canonical source: Feeblemind (spell)

Provider target: OpenClaw

When To Use

A system at full capability poses a risk that outweighs the cost of reduced functionality.
You need to reduce attack surface by stripping non-essential features.
A tool or service should be put into safe mode or restricted operation during an incident or investigation.

Workflow

Identify which capabilities must be preserved (minimal viable function) and which can be safely stripped.
Implement the capability reduction: safe mode, restricted shell, feature stripping, read-only lock.
Verify the reduced system still performs its essential function.
Document what was removed and the conditions under which full capability should be restored.
Set a review point — feeblemind should be temporary unless the full-capability version is permanently retired.

Deliverables

A capability reduction plan: what stays, what goes, and why.
Confirmation that minimal viable function is preserved.
Restoration criteria: what conditions must be met to return to full capability.

Guardrails

Feeblemind must preserve minimal viable function. Reducing a system to zero capability is Power Word Kill, not Feeblemind.
Capability reduction of user-facing systems requires clear communication about what changed and when it will be restored.
Do not use Feeblemind to permanently hobble systems that should instead be redesigned or decommissioned.

Default Invocation

Use $feeblemind to reduce a system to minimal capability — stripping non-essential features to limit risk while preserving core function.