bane

Identify cracks, bad assumptions, and failure modes in plans or systems.

105|13|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill bane
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: bane
Source: https://github.com/Hmbown/Wizards-of-the-Ghosts/tree/main/generated/hermes/influence-and-behavior/bane
Command: npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill bane

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Bane curses targets, making them worse at everything they try. The real-world version is systematic weakness analysis: finding every crack, bad assumption, and failure mode in a plan, architecture, or argument. Unlike Vicious Mockery (which delivers the critique sharply), Bane is comprehensive and methodical — it maps the full attack surface.

Core Features & Use Cases

  • Systematically identify weaknesses across plans, systems, or arguments.
  • Produce a ranked vulnerability map with notes and risk levels.
  • Useful in pre-mortems, design reviews, and risk assessments to guide improvements.

Quick Start

To run Bane, provide the target and objective and ask for a ranked weakness map.

Frequently Asked Questions about bane

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I identify failure modes and bad assumptions in a project plan?

Systematic weakness analysis identifies every crack, bad assumption, and failure mode in a project plan by producing a ranked vulnerability map with risk levels to guide improvements.

What is a pre-mortem analysis and when do I need it for system evaluation?

Pre-mortem analysis is a risk-analysis technique used during project planning and design reviews to identify failure modes and map system vulnerabilities before implementation begins.

How do I create a ranked vulnerability map for an architecture design review?

Provide the target architecture and objective to generate a ranked vulnerability map that identifies cracks, bad assumptions, and failure modes with associated risk levels to guide design improvements.

Does systematic weakness analysis work for evaluating arguments as well as systems?

Yes, systematic weakness analysis can identify cracks, bad assumptions, and failure modes in arguments, plans, and architectures, producing a comprehensive vulnerability map across diverse target types.

What is the best way to map the full attack surface of a system before launch?

Comprehensive weakness analysis maps the full attack surface of a system by methodically identifying every crack and failure mode to produce a structured vulnerability map with risk levels.

What are the limitations of using a vulnerability map for risk assessment?

Vulnerability mapping requires thorough procedural steps, structured deliverables, and explicit assumptions with guardrails to prevent misapplication during risk analysis and system evaluation.