l5-antifragile_redundancy-is-aggressive

Explains Taleb's argument that redundancy is aggressive investment in antifragility.

Updated Jun 29, 2026
One-click install
npx skills add https://github.com/curation-labs/taleb-mind --skill l5-antifragile-redundancy-is-aggressive-curation-labs
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: l5-antifragile_redundancy-is-aggressive
Source: https://github.com/curation-labs/taleb-mind/tree/main/skills/l5-antifragile_redundancy-is-aggressive
Command: npx skills add https://github.com/curation-labs/taleb-mind --skill l5-antifragile-redundancy-is-aggressive-curation-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? This Skill provides a distilled, source-grounded explanation of Nassim Nicholas Taleb's argument that redundancy is an aggressive investment in optionality rather than wasteful inefficiency, helping you reason about systems, risk, and organizational design. ## Core Features & Use Cases - Concept Explanation: Articulates why nature builds redundancy (two kidneys, two lungs) as antifragile design rather than waste. - Critique of Naive Optimization: Frames the trade-off where removing slack and buffers yields visible efficiency gains but invisible catastrophic fragility. - Use Case: When advising on lean operations, supply chain design, or organizational restructuring, use this Skill to argue for maintaining buffers and spare capacity as survival-critical optionality. ## Quick Start Explain why redundancy in systems is an aggressive investment in antifragility rather than waste, using Taleb's argument from Antifragile.

Frequently Asked Questions about l5-antifragile_redundancy-is-aggressive

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

FAQPage Schema
What is Taleb's argument about redundancy in Antifragile?▼

Taleb argues that redundancy, such as having two kidneys or two lungs, is nature's aggressive investment in optionality, not waste. Spare capacity lets systems absorb shocks and degrade gracefully instead of collapsing under stress.

How does redundancy relate to antifragility?▼

Redundancy provides the buffers that make systems antifragile by ensuring capacity exists when shocks arrive. Removing slack trades antifragility for small average performance gains while exposing the system to catastrophic failure.

Why is naive optimization dangerous for organizations?▼

Naive optimization strips buffers and reserves in the name of efficiency, producing visible short-term gains but invisible catastrophic risks. Just-in-time supply chains and lean organizations illustrate this fragility when disruptions occur.

When should efficiency be preferred over redundancy?▼

This Skill argues efficiency-focused optimization is appropriate only when shocks are truly impossible, which Taleb considers unrealistic. Since shocks always come eventually, maintaining redundancy is framed as the price of survival.

What source does this Skill's content come from?▼

The content is grounded in Chapter 2 of Taleb's Antifragile, titled Overcompensation and Overreaction Everywhere. It is marked as an explicit source impression with evidence traced to that chapter.