antifragility-and-tail-risk

Analyze software designs for fragility, tail risk, and ruin exposure.

2|Updated Apr 30, 2026
One-click install
npx skills add https://github.com/NlightNFotis/skills --skill antifragility-and-tail-risk
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: antifragility-and-tail-risk
Source: https://github.com/NlightNFotis/skills/tree/main/antifragility-and-tail-risk
Command: npx skills add https://github.com/NlightNFotis/skills --skill antifragility-and-tail-risk

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you evaluate whether a software design is merely working under normal conditions or is dangerously fragile under stress. It is built for situations where rare but severe failures matter more than average performance, such as migrations, critical dependencies, security-sensitive systems, and irreversible architectural bets.

Core Features & Use Cases

  • Ruin and Tail-Risk Review: Identifies absorbing failures, nonlinear downside, hidden coupling, and short-volatility tradeoffs that can turn small shocks into catastrophic outcomes.
  • Safer Design Recommendations: Reframes abstract risk concerns into concrete engineering moves such as deletion, isolation, rollback paths, canaries, kill switches, bounded experiments, and barbell design.
  • False Confidence Audit: Challenges overconfidence based on CI passes, staging success, uptime, or benchmarks by asking what evidence would still look good if the system were actually fragile.
  • Use Case: Before a major database migration or vendor integration, use this Skill to surface irreversible failure modes, identify where rollback is weak, and propose changes that cap downside while preserving learning and optionality.

Quick Start

Ask the antifragility-and-tail-risk skill to review your planned migration or architecture decision for ruin risks, false confidence, fragility surfaces, and the safest asymmetric changes.

Frequently Asked Questions about antifragility-and-tail-risk

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

FAQPage Schema
How do I identify tail risk and fragility in my software architecture before a migration?

Identify tail risk in your software architecture by analyzing designs for absorbing failures, nonlinear downside, and hidden coupling that turn small shocks into catastrophic ruin during irreversible migrations.

What is a false confidence audit in software engineering?

A false confidence audit challenges overconfidence in CI passes, staging success, or uptime by asking what evidence would still look good if the system were actually fragile under stress.

How do I design antifragile systems for critical-path dependencies?

Design antifragile systems by implementing barbell designs, isolation, rollback paths, kill switches, and bounded experiments to cap downside while preserving learning and optionality for critical-path dependencies.

What is the best way to review ruin exposure for irreversible architectural bets?

The best way to review ruin exposure is to analyze short-volatility tradeoffs and rollback limits, proposing safer asymmetric changes that cap downside while preserving optionality for irreversible architectural bets.

When should I not rely on uptime and benchmarks for risk analysis?

Do not rely on uptime and benchmarks for risk analysis when evaluating high-stakes engineering changes, because average performance hides rare but severe failures and creates false confidence in fragile systems.

Does this approach work for vendor integration and database migration reviews?

Yes, this approach works for vendor integration and database migration reviews by surfacing irreversible failure modes, identifying weak rollback paths, and proposing changes that cap downside.