Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Tragedy Of The Commons

ASecurity

Shared resources become depleted when individuals, acting in rational self-interest, overuse resources where costs are distributed but benefits are private

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
devopsrustgogitapi

Works with

cliapi

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill tragedy-of-the-commons --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Tragedy Of The Commons?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Tragedy Of The Commons
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-tragedy-of-the-commons/badge)](https://www.skillsdirectory.com/skills/lev-os-tragedy-of-the-commons)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: Tragedy of the Commons
description: Shared resources become depleted when individuals, acting in rational self-interest, overuse resources where costs are distributed but benefits are private
domain: domain-specific
subdomain: economics
track: mental-models
sources:
  - Garrett Hardin's 1968 Science paper
  - Elinor Ostrom's Nobel Prize research on commons governance
  - Game theory and collective action literature
  - Environmental economics
score: 45
---

## Overview

The Tragedy of the Commons describes how shared resources get destroyed through rational individual action. A pasture open to all herders: each rationally adds more cattle (personal benefit) even as overgrazing destroys the pasture (distributed cost). Individual rationality leads to collective ruin.

**The core dynamic**: When benefits are private and costs are socialized, individuals overconsume. Each user captures 100% of the benefit from additional use but bears only a fraction of the cost (shared among all users). This asymmetry drives overuse until the commons collapses.

**Classic examples**:
- **Fishing**: Individual boats maximize catch; fish stocks collapse
- **Pollution**: Factories externalize waste; air/water degrades for everyone
- **Traffic**: Each driver benefits from driving; roads become congested for all
- **Antibiotics**: Each patient wants antibiotics; overuse creates resistance for everyone

**Why it matters**: Many of humanity's most pressing problems are commons tragedies: climate change, ocean acidification, groundwater depletion, spectrum allocation, digital attention spans.

## When to Use

**Resource management:**
- Designing sustainable use policies for shared resources
- Identifying commons tragedies before collapse
- Evaluating natural resource governance structures

**Product and platform design:**
- Managing shared platform resources (API rate limits, storage)
- Preventing free-rider problems in communities
- Designing usage policies that sustain shared value

**Organizational dynamics:**
- Managing shared budgets, equipment, and facilities
- Preventing meeting overload and calendar tragedy
- Allocating limited engineering resources across teams

**Policy and regulation:**
- Structuring environmental regulations
- Designing public goods provision
- Managing spectrum, airspace, and other public resources

**Strategic analysis:**
- Identifying industry-level commons problems
- Understanding competitive dynamics that destroy value
- Evaluating collective action challenges

## Process

### 1. Identify the Commons
Recognize shared resource structures:

**Commons characteristics**:
- Multiple users with access
- Rivalrous consumption (my use reduces yours)
- Difficult to exclude users
- Benefits of use are private; costs are distributed

**Types of commons**:
| Type | Example | Depletion Risk |
|------|---------|----------------|
| Natural | Fisheries, forests, aquifers | Physical exhaustion |
| Environmental | Air quality, climate stability | Degradation |
| Infrastructure | Roads, networks, platforms | Congestion |
| Organizational | Budgets, attention, talent | Misallocation |
| Digital | Bandwidth, storage, API capacity | Overload |

### 2. Analyze the Incentive Structure
Map individual vs. collective interests:

**For each user, calculate**:
- Private benefit of additional consumption: B
- Private cost of additional consumption: C/N (where N = number of users)
- Net private benefit: B - (C/N)

**Tragedy occurs when**: B > C/N (individual gains exceed individual costs) but total cost exceeds total benefit for collective.

**Accelerating factors**:
- Large N (costs very diffuse)
- High individual benefit from marginal use
- Low visibility of aggregate impact
- Discounting future consequences

### 3. Evaluate Governance Options
Elinor Ostrom identified successful commons management approaches:

**Privatization**: Convert commons to private property
- Works when: Resource divisible, property rights enforceable
- Drawbacks: May exclude legitimate users, equity concerns
- Example: Tradable fishing quotas

**Government Regulation**: External authority limits use
- Works when: Authority has legitimacy, monitoring feasible, enforcement possible
- Drawbacks: Information problems, regulatory capture, enforcement costs
- Example: Pollution permits, hunting seasons

**Community Self-Governance**: Users collectively manage
- Works when: Community is defined, repeat interactions, monitoring by peers
- Drawbacks: Requires social cohesion, may not scale
- Example: Swiss alpine meadows, Maine lobster fisheries

**Ostrom's Design Principles for Successful Commons**:
1. Clear boundaries (who can access)
2. Congruence between rules and local conditions
3. Collective-choice arrangements (users participate in rule-making)
4. Monitoring (by users or accountable to users)
5. Graduated sanctions for violations
6. Conflict resolution mechanisms
7. Recognition of rights to organize
8. Nested enterprises (for larger systems)

### 4. Implement Solutions
Choose and execute appropriate intervention:

**Technical solutions**:
- Quotas and caps (hard limits on use)
- Pricing externalities (Pigouvian taxes)
- Tradable permits (market allocation within cap)
- Usage metering and accountability

**Social solutions**:
- Norm establishment and enforcement
- Reputation systems for sustainable use
- Education on collective consequences
- Community identity around stewardship

**Structural solutions**:
- Reduce number of users (exclusion)
- Increase visibility of individual impact
- Shorten feedback loops between use and consequence
- Create ownership or responsibility assignment

### 5. Monitor and Adapt
Commons management requires ongoing attention:

**Monitoring needs**:
- Resource stock levels and trends
- Individual and aggregate use patterns
- Compliance with rules and norms
- Emerging threats or changing conditions

**Adaptation triggers**:
- Resource declining despite rules
- Free-riders circumventing governance
- New users or use patterns emerging
- External conditions changing (technology, climate)

## Example

**Tech Company: The Meeting Room Tragedy**

**The Commons**: 10 conference rooms for 500 employees.

**The Tragedy**:
- Each team benefits from booking rooms (private benefit)
- Overbooking means rooms sit empty when "held" (distributed cost)
- Rational response: Book more rooms as insurance against unavailability
- Result: All rooms perpetually booked, actual utilization 30%, everyone frustrated

**Analysis**:
- Private benefit of booking: Certainty of having space
- Private cost: Minimal (time to book)
- Distributed cost: Reduced availability for all
- Classic commons tragedy

**Solutions Implemented**:
1. **Metering**: Dashboard showing individual/team booking patterns
2. **Pricing**: No-show penalties (booking without attending = team loses priority)
3. **Quotas**: Per-team weekly booking limits
4. **Decay**: Bookings auto-release if not confirmed 10 minutes before
5. **Transparency**: Public view of who books what

**Result**: Utilization increased to 75%, perceived availability improved, hoarding behavior eliminated.

## Anti-Patterns

**Assuming private ownership always solves commons**: Privatization works for some resources but creates equity issues and may be impractical (can't privatize atmosphere). Governance choice depends on resource characteristics.

**Ignoring Ostrom's research**: Hardin's original essay suggested only privatization or government control. Ostrom's Nobel Prize-winning research showed communities successfully self-govern commons for centuries. Community solutions often outperform top-down regulation.

**Treating all shared resources as commons**: Not all shared resources face tragedy. Non-rivalrous resources (ideas, digital goods with low marginal cost) don't deplete with use. Public goods provision is different from commons management.

**One-time solution mindset**: Commons management is ongoing. Rules degrade, new users arrive, conditions change. Successful commons require adaptive governance, not static rules.

**Underestimating social solutions**: Economists often jump to pricing or property rights. Norms, reputation, and community identity can manage commons effectively, especially at smaller scales.

## Related Frameworks

- **Externalities**: Costs imposed on third parties (commons tragedy is collective externality)
- **Game Theory**: Commons as multi-player prisoner's dilemma
- **Free Rider Problem**: Related collective action failure in public goods provision
- **Collective Action**: Broader framework for group coordination challenges
- **Moral Hazard**: Individual risk-taking when costs are distributed
- **Incentives**: Foundation for understanding why overuse occurs
- **Systems Thinking**: Commons as stock-and-flow system with depletion dynamics

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Terraform Module Library

Build reusable Terraform modules for AWS, Azure, and GCP infrastructure following infrastructure-as-code best practices. Use when creating infrastructure modules, standardizing cloud provisioning, or implementing reusable IaC components.

393431 votes

sematext-otel

Wire a service's OpenTelemetry output to Sematext Cloud. Walks through region, App-type, instrumentation flow (managed OTLP endpoint vs Sematext Agent), and signal selection (traces/metrics/logs), then produces the exact env-var block and points at a runnable reference example in this repo. Invoke when instrumenting a new app for Sematext.

01 votes

Deployment Patterns

Deployment workflows, CI/CD pipeline patterns, Docker containerization, health checks, rollback strategies, and production readiness checklists for web applications. Use when setting up deployment infrastructure or planning releases.

2459130 votes

Babysit

Watch a pull request or review cycle until it is ready to merge. Use when asked to babysit, monitor, or keep checking PR comments, reviews, and CI until all actionable issues are resolved.

929660 votes

V7 Roster

Interact with the Paperclip control plane API for task coordination and governance. Use when checking assignments, updating issue status, posting comments, delegating work, managing routines, or calling Paperclip API endpoints.

805540 votes
View all in devops →