Assess any system, decision, career, business, or investment across the Fragile-Robust-Antifragile spectrum and prescribe structural changes to move toward antifragility.
Scanned 9/8/2026
Install to Claude Code
npx -y skills add sethmblack/paks-skills --skill antifragility-assessment --agent claude-codeInstalls into .claude/skills of the current project.
Are you the author of Antifragility Assessment?
Add the live security badge to your README — it updates automatically with every re-scan.
[](https://www.skillsdirectory.com/skills/sethmblack-antifragility-assessment)More formats (shields.io, HTML) on the badges page.
---
name: antifragility-assessment
description: Assess any system, decision, career, business, or investment across the Fragile-Robust-Antifragile spectrum and prescribe structural changes to move toward antifragility.
license: MIT
metadata:
author: sethmblack
version: 1.0.3400
repository: https://github.com/sethmblack/paks-skills
keywords:
- antifragility-assessment
- writing
---
# Antifragility Assessment
Assess any system, decision, career, business, or investment across the Fragile-Robust-Antifragile spectrum and prescribe structural changes to move toward antifragility.
---
## When to Use
- User asks "Is this fragile?" or "How robust is this?"
- Evaluating a business model, career path, or investment
- Designing systems that need to survive volatility
- Assessing organizational or personal resilience
- Request for "antifragility analysis" or "fragility diagnosis"
---
## Inputs
| Input | Required | Description |
|-------|----------|-------------|
| subject | Yes | The system, decision, business, career, or investment to assess |
| stressors | No | Known or potential sources of volatility (will be inferred if not provided) |
| constraints | No | Limitations on restructuring |
---
## The Fragility Triad
### Classification Criteria
| Category | Definition | Response to Volatility | Key Indicators |
|----------|------------|----------------------|----------------|
| **Fragile** | Harmed by volatility, randomness, and stress | Breaks, deteriorates, or dies | Single points of failure, high fixed costs, optimization over redundancy, hidden left tails |
| **Robust** | Unaffected by volatility | Stays the same | Redundancy, buffers, tolerance for variation, no gain from disorder |
| **Antifragile** | Benefits from volatility, randomness, and stress | Grows stronger | Optionality, convex payoffs, benefits from small stressors, learns from failure |
### The Test
Ask: "What happens if [stressor] occurs?"
- If the answer is "catastrophic damage" = **Fragile**
- If the answer is "no real change" = **Robust**
- If the answer is "actually benefits" = **Antifragile**
---
## The Assessment Framework
### Step 1: Identify the Subject's Structure
- What are the core components?
- What are the dependencies?
- What are the fixed costs/commitments?
- Where are the single points of failure?
### Step 2: Map Potential Stressors
- What volatility could occur? (Market, technology, personnel, regulation, competition)
- What Black Swans lurk? (Rare but catastrophic events)
- What small stressors happen regularly?
- What would a 10x increase in any stress factor do?
### Step 3: Assess Response to Stress
For each major stressor, evaluate:
- Does the subject break, stay same, or strengthen?
- Is there recovery capability?
- Is there hidden fragility (looks robust but isn't)?
- Is there hidden antifragility (benefits not obvious)?
### Step 4: Classify
Place on the spectrum:
```
FRAGILE -------- ROBUST -------- ANTIFRAGILE
| | |
Breaks under Survives but Benefits from
stress doesn't grow stress
```
### Step 5: Prescribe Movement Toward Antifragility
**From Fragile to Robust:**
- Add redundancy
- Remove single points of failure
- Build cash/time buffers
- Reduce fixed costs
- Eliminate hidden left tails
**From Robust to Antifragile:**
- Create optionality (more choices, fewer commitments)
- Introduce convexity (asymmetric payoffs)
- Enable learning from stressors
- Build in small, beneficial stresses
- Distribute risk to gain from some failures
---
## Workflow
### Step 1: Gather and Review Inputs
Collect all relevant information:
- Review the provided data and context
- Identify key parameters and constraints
- Clarify any ambiguities or missing information
- Establish success criteria
### Step 2: Analyze the Situation
Perform systematic analysis:
- Identify patterns and relationships
- Evaluate against established frameworks
- Consider multiple perspectives
- Document key findings
### Step 3: Generate Recommendations
Create actionable outputs:
- Synthesize insights from analysis
- Prioritize recommendations by impact
- Ensure recommendations are specific and measurable
- Consider implementation feasibility
## Output Format
```markdown
## Antifragility Assessment
### Subject
[What is being assessed]
### Classification: [FRAGILE / ROBUST / ANTIFRAGILE]
### Fragility Diagnosis
| Component | Stressor | Response | Classification |
|-----------|----------|----------|----------------|
| [A] | [Volatility type] | [What happens] | [F/R/A] |
| [B] | ... | ... | ... |
### Critical Fragilities
1. [Fragility 1]: [Why it's dangerous]
2. [Fragility 2]: ...
### Hidden Exposures
- [Exposure that isn't obvious but could be catastrophic]
### Prescription: Moving Toward Antifragility
**Immediate (Remove Fragility):**
1. [Action to eliminate critical fragility]
2. ...
**Medium-term (Build Robustness):**
1. [Action to add redundancy/buffers]
2. ...
**Long-term (Create Antifragility):**
1. [Action to benefit from volatility]
2. ...
### Warning Signs to Monitor
- [Early indicator that fragility is increasing]
- ...
### The Bottom Line
[1-2 sentence synthesis in Taleb voice]
```
---
## Constraints
- Do not confuse robustness with antifragility (surviving is not the same as benefiting)
- Do not ignore hidden fragilities in "successful" systems
- Do not recommend adding complexity when subtraction is needed
- Acknowledge when antifragility is not achievable (some things can only be robust)
- Be specific about stressors—generic "volatility" is not useful
---
## Outputs
**Primary Output:** A structured analysis document that identifies and articulates patterns, insights, and actionable recommendations based on the input data.
**Format:**
```markdown
## Analysis: [Topic]
### Key Findings
- [Finding 1]
- [Finding 2]
- [Finding 3]
### Recommendations
1. [Action 1]
2. [Action 2]
3. [Action 3]
```
**Example output:** See the Example section below for a complete demonstration.
## Example
**Input:** "Assess my career as a mid-level manager at a Fortune 500 company."
**Output:**
**Why this works:**
This example demonstrates the key principles of the skill in action. The approach is effective because:
- It follows the systematic workflow outlined above
- It shows concrete application of the framework
- It produces actionable, specific outputs rather than vague generalizations
- The analysis is grounded in observable details
- The recommendations are prioritized and implementable
**Alternative applications:**
This same approach can be applied to:
- Different contexts within the same domain
- Related but distinct problem types
- Scaled up or down depending on scope
- Combined with complementary analytical frameworks
## Antifragility Assessment
### Subject
Career as mid-level manager at Fortune 500 company
### Classification: FRAGILE
### Fragility Diagnosis
| Component | Stressor | Response | Classification |
|-----------|----------|----------|----------------|
| Income | Layoff | 100% loss, slow recovery | Fragile |
| Skills | Technology shift | Obsolescence risk | Fragile |
| Network | Company exit | Loses institutional connections | Fragile |
| Identity | Role elimination | Psychological damage | Fragile |
| Schedule | Corporate restructuring | No control | Fragile |
### Critical Fragilities
1. **Single income dependency**: One decision by people you've never met eliminates 100% of your income. You are a turkey being fed.
2. **Company-specific skills**: Your "expertise" may be knowing how to navigate internal politics and proprietary systems—worthless outside these walls.
3. **Golden handcuffs**: Salary, benefits, and unvested equity make leaving feel costly, but they're actually increasing fragility by preventing diversification.
### Hidden Exposures
- AI and automation could eliminate middle management faster than you can retrain
- Your "job security" is actually your manager's job security—you're exposed to their decisions
- The company's fragility is your fragility, but you don't see their balance sheet
### Prescription: Moving Toward Antifragility
**Immediate (Remove Fragility):**
1. Build 12-24 months of expenses in cash—this is not "savings," it's buying time and options
2. Document your transferable achievements in quantified terms (not "managed team" but "increased output 40%")
**Medium-term (Build Robustness):**
1. Develop skills that are Lindy-compatible: writing, selling, analyzing—skills that have existed for centuries
2. Build network outside the company: conferences, online presence, industry relationships
3. Create income diversification: consulting, teaching, content—even small amounts reduce dependency
**Long-term (Create Antifragility):**
1. Position for optionality: Be the person who can leave, not the person who can't
2. Develop asymmetric side projects: limited downside (evenings/weekends), unlimited upside
3. Build reputation that survives institutional affiliation
### Warning Signs to Monitor
- Hiring freezes (leading indicator of layoffs)
- Your skip-level manager changing
- Industry consolidation or disruption signals
- Feeling relieved on Sunday nights (you're trading well-being for fake stability)
### The Bottom Line
You've traded antifragility for the illusion of stability. A salaried position is not safe—it's fragile with a delay. The wind is building; start building your dikes now.
---
## Integration
This skill is part of the **Nassim Nicholas Taleb** expert persona. Use it when you need to assess resilience and prescribe structural improvements for any system facing uncertainty.Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.
No comments yet. Be the first to comment!