Fear

Fear makes targets run from danger. The real-world version is structured pessimism: pre-mortem analysis, worst-case scenario generation, and risk amplification exercises that counteract the natural optimism bias in planning. Fear is the antidote to "it'll probably be fine.

113 stars 11 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Hmbown/Wizards-of-the-Ghosts --skill fear
Manual install
git clone --depth 1 https://github.com/Hmbown/Wizards-of-the-Ghosts.git /tmp/Wizards-of-the-Ghosts
mkdir -p ~/.claude/skills
cp -r /tmp/Wizards-of-the-Ghosts/generated/hermes/influence-and-behavior/fear ~/.claude/skills/fear

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Fear
Amplify worst-case scenarios to surface risks that optimism hides.
## What This Skill Does
Fear makes targets run from danger. The real-world version is structured pessimism: pre-mortem analysis, worst-case scenario generation, and risk amplification exercises that counteract the natural optimism bias in planning. Fear is the antidote to "it'll probably be fine."
In this grimoire, Fear is treated as a metaphorical spell with a shipping-now delivery profile.
Canonical reference input: Fear (spell).
## When To Use

- A team is moving forward on a plan with insufficient risk analysis.
- You need a pre-mortem: imagine this project failed — why?
- Optimism bias is hiding real risks that need to be surfaced before committing resources.

## Prerequisites

- No extra runtime dependencies beyond Hermes Agent and the normal toolset for this session.

## Procedure

1. Restate the target, the success condition, and any no-touch boundaries before taking action.
2. Take the plan, project, or decision as input.
3. Assume it failed catastrophically. Work backward: what went wrong?
4. Generate the 5-10 most plausible failure modes, ranked by likelihood and severity.
5. For each failure mode, note whether it is preventable, mitigable, or unavoidable.
6. Deliver the fear inventory with a recommendation on which risks to address before proceeding.
7. Package the result as the deliverables below, with confidence, assumptions, and unresolved risk called out explicitly.

## Deliverables
Read the full skill on GitHub

Details

Skill name
fear
Path
generated/hermes/influence-and-behavior/fear/SKILL.md
License
CC0-1.0
Repo updated
5 April 2026

FAQ

What does the Fear skill do?

Fear makes targets run from danger. The real-world version is structured pessimism: pre-mortem analysis, worst-case scenario generation, and risk amplification exercises that counteract the natural optimism bias in planning. Fear is the antidote to "it'll probably be fine.

How do I install the Fear skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add Hmbown/Wizards-of-the-Ghosts --skill fear. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Fear popular?

It lives in Hmbown/Wizards-of-the-Ghosts, which has 113 GitHub stars and 11 forks.

Related skills

Acrobatics

113

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.

Productivity & Notes11

Animal Friendship

113

Hmbown/Wizards-of-the-Ghosts

Animal Friendship is the first-contact spell for unfamiliar APIs, vendors, and services. It treats integration work as relationship-building: learn the temperament, respect the boundaries, and earn a stable exchange before asking for anything ambitious. The goal is not domination but trustable cooperation.

Productivity & Notes11

Animal Handling

113

Hmbown/Wizards-of-the-Ghosts

Use this skill when the system is not fully broken but behaves like a skittish animal: flaky CI, fragile legacy services, or moody dependencies. It focuses on coaxing, pacing, and stable handling rather than heroic rewrites.

Other11

Feature Workflow

49

lllyys/vreader

Run the binding 6-gate feature workflow end-to-end per rule 47 (Plan → Independent Plan Audit → TDD Implementation → Implementation Audit Loop → Device/Integration Verification → Merge). Use this skill whenever the user wants to implement a new feature in vreader, asks 'implement feature #N', 'work on feature 47', 'start the feature workflow', 'plan + build feature X', or describes building a new capability that doesn't yet exist. NOT for fixing broken implementations (that's fix-issue). The skill drives the row from `TODO` → `VERIFIED` through six gates that must never be skipped — author/aud

Productivity & Notes21

Dream

113

Hmbown/Wizards-of-the-Ghosts

Dream is asynchronous insight delivery timed to the receiver's readiness rather than the sender's convenience. It covers overnight reports, pre-meeting briefings, dawn digests, and other messages that should arrive as ambient context before work begins. The spell's magic is timing plus framing: the receiver wakes up to the answer, not a pile of raw events. It works best when the message feels prepared, quiet, and exactly on time. It fails when it becomes another noisy alert stream wearing a moonlit costume.

Productivity & Notes11

File Feature

49

lllyys/vreader

Create a GitHub issue for a feature row in docs/features.md and stamp `GH: #N` into its Notes column. Use this skill whenever the user wants to file/mirror/create a GH issue for an existing feature row, or asks 'create issue for feature #N', 'file feature 47', 'mirror feature 32 to GH', 'this feature needs a GH issue'. Also trigger when the `check_gh_issue_mirror.sh` PreToolUse hook blocks an edit to a `docs/features.md` row because it lacks `GH: #N`. Skip if status is `TODO` (promote to `PLANNED` first) or Notes contains `Mirror: no`.

Productivity & Notes21

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.