Agent skill

thinking-via-negativa

Improve by removal rather than addition. Focus on what to stop doing, eliminate the negative, and subtract complexity. Use for system simplification, process improvement, and feature prioritization.

majiayu000534★ · 1 repos on radarProfile →
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill thinking-via-negativa --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 9 KB
Bundled scripts: none
Path: skills/analysis/thinking-via-negativa/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Via Negativa ## Overview Via Negativa, articulated by Nassim Taleb in "Antifragile," is the principle that improvement often comes from subtraction rather than addition. We're biased toward adding (features, processes, complexity) when removing (bugs, friction, unnecessary work) often provides more value with less risk. **Core Principle:** Focus on what to remove, not what to add. Subtraction is more robust than addition. ## When to Use - System simplification - Process improvement - Feature prioritization (what NOT to build) - Performance optimization - Reducing technical debt - Personal productivity - Decision-making (what to avoid) - Code review (what to delete) Decision flow: ``` Trying to improve something? → First instinct is to add? → yes → PAUSE, CONSIDER SUBTRACTION → Can you achieve the goal by removing instead? → yes → REMOVE FIRST → Is current complexity necessary? → no → SIMPLIFY VIA NEGATIVA ``` ## The Via Negativa Process ### Step 1: Identify What to Eliminate Instead of "What should we add?", ask: ``` - What's not working that we should remove? - What's causing harm we should stop? - What's unnecessary complexity we should eliminate? - What's outdated that we shou

What's inside
Steps it walks through
  1. Overview
  2. When to Use
  3. The Via Negativa Process
  4. Step 1: Identify What to Eliminate
  5. Step 2: Catalog Candidates for Removal
  6. Step 3: Evaluate Impact of Removal
  7. Step 4: Remove with Monitoring
  8. Via Negativa Patterns
  9. Subtractive Design
  10. The Pruning Principle
  11. Harm Reduction Over Benefit Addition
  12. The 80/20 Removal
  13. Application Areas
  14. Code
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the thinking-via-negativa skill do?

Improve by removal rather than addition. Focus on what to stop doing, eliminate the negative, and subtract complexity. Use for system simplification, process improvement, and feature prioritization.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill thinking-via-negativa --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going