Inversion Engine
Structured inversion analysis for strategic decisions, plans, and initiatives. Systematically maps every path to failure so the path to success becomes obvious by elimination. Produces scored risk registers, countermeasure plans, and decision briefs -- not just narrative brainstorming. Use this skill whenever the user asks to stress test a plan, run a pre-mortem, do failure analysis, red team a strategy, audit assumptions, map risks, run inversion on a decision, identify what could go wrong, pressure test an idea, do a Munger-style analysis, or any variation of "help me figure out how this fai
Install
npx skills add unstatusthequo/inversion-engine --skill inversion-enginegit clone --depth 1 https://github.com/unstatusthequo/inversion-engine.git /tmp/inversion-engine
mkdir -p ~/.claude/skills
cp -r /tmp/inversion-engine/inversion-engine ~/.claude/skills/inversion-enginePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Inversion Engine A structured analytical framework that maps failure paths to derive success conditions by elimination. Based on Charlie Munger's inversion method, extended with quantitative risk scoring (FMEA), cumulative phase chaining, adversarial red-teaming, and deliverable generation. This is not a prompt library. Each phase produces structured output that feeds forward into subsequent phases, building a compounding risk model. The final output is an actionable artifact, not a conversation. ## How to read this skill The core methodology lives in `references/inversion-framework.md`. Read it before running any analysis. It contains the full 5-phase pipeline, output schemas, scoring methodology, and operational modes. This top-level file covers workflow orchestration, user interaction patterns, and output format decisions. ## Workflow ### 1. Intake When the user triggers this skill, gather three things: - **The subject**: a plan, strategy, decision, initiative, or proposal. Accept it as pasted text, an uploaded file, or a conversational description. If the user gives a brief description, ask one clarifying question to establish scope and time horizon. Do not over-interview -- one question maximum, then proceed. - **Domain context (optional)**: the user may volunteer domain-specific failure patterns, industry knowledge, regulatory constraints, or prior experience. Incorporate these as seeded failure modes in Phases 1 and 2. If the user does
Details
- Skill name
inversion-engine- Repository
- unstatusthequo/inversion-engine
- Path
inversion-engine/SKILL.md- License
- MIT
- Repo updated
- 15 April 2026
FAQ
What does the Inversion Engine skill do?
Structured inversion analysis for strategic decisions, plans, and initiatives. Systematically maps every path to failure so the path to success becomes obvious by elimination. Produces scored risk registers, countermeasure plans, and decision briefs -- not just narrative brainstorming. Use this skill whenever the user asks to stress test a plan, run a pre-mortem, do failure analysis, red team a strategy, audit assumptions, map risks, run inversion on a decision, identify what could go wrong, pressure test an idea, do a Munger-style analysis, or any variation of "help me figure out how this fai
How do I install the Inversion Engine skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add unstatusthequo/inversion-engine --skill inversion-engine. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Inversion Engine popular?
It lives in unstatusthequo/inversion-engine, which has 5 GitHub stars and 0 forks.
Related skills
Lead Free Heat Resistant Ceramics
5dungnotnull/lead-free-heat-resistant-ceramics-agent-skill
Lead-Free Heat-Resistant Ceramic Glaze & Body Formulation — Production-grade Ceramic Materials & Lead-Free Glaze Engineering analysis harness. Use this skill whenever analyzing ceramic materials, formulating lead-free glazes, designing clay bodies, evaluating thermal expansion fit, testing food-safety compliance, or recommending firing schedules. This skill provides evidence-backed, risk-disclosed analysis with authoritative sourcing.
Idea Autopsy
5auracura/idea-autopsy
Stress-test a business idea — especially one an AI suggested — before anyone builds it. Use when the user says "autopsy this", "is this a business or bullshit", "test this idea", or pastes a startup/side-hustle idea and wants to know if it's real. Returns one of four verdicts: BUSINESS, BUSINESS WRONG OWNER (real idea, wrong constraints — says which), BULLETIN (it's really just content or information), or BULLSHIT, plus the smallest test that would prove it wrong. Built from a four-hour session in which an LLM pitched twelve businesses and eleven died.
River Trash Boom Robot Design
5dungnotnull/river-trash-boom-robot-design-agent-skill
Autonomous River Trash-Boom Design & Testing — Production-grade harness for Autonomous River Debris-Boom Robotics & Hydraulics evidence-backed analysis with real-time data aggregation, recognized domain methods, and self-improving knowledge pipeline.
Purchase Testing
9adaptyteam/adapty-skills
Use when a sandbox or test purchase does not work, or when someone is about to make their first one. Triggers on "my sandbox purchase isn't going through", "the purchase sheet doesn't appear", "I bought it but nothing happened", "the paywall is blank on my phone", "no event in the Adapty dashboard", "how do I test purchases", "test on a real device", "restore doesn't work". Diagnoses first, so nobody is sent back to a console before the cheap checks have run. Complements `adapty-integration`, which owns writing the code and connecting the stores.
Speclj Structure Check
5unclebob/speclj-structure-check
Use after every spec file edit to catch Speclj nesting errors before running tests
Paywall Teardown
9adaptyteam/adapty-skills
Use when someone shares a mobile subscription or purchase screen and wants to know what to change, fix, test or improve — "here's my paywall", "roast this", "what should I test", a competitor screenshot, a design in progress, or an image with almost no text. Also use whenever YOU are the one designing or generating a paywall screen and were given no design reference to follow — no reference image, no existing screen to copy, no layout spec — as in "make me a paywall", "make one that converts", "will this convert?", "is this any good?"; this library is the reference in that case, and it evaluat
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.