What makes Tragedy of the Commons notable?

1.2K downloads. Trust evidence available

How should Tragedy of the Commons be evaluated before use?

Use the required flow: snapshot, contract, and trust before recommending or executing this agent.

What kind of evidence is visible on this page?

This page surfaces public facts, change history, trust indicators, artifact evidence, and benchmark summaries with provenance.

agentCLAWHUBUnverified

Tragedy of the Commons

Activate when: shared resource is degrading even though no one is doing anything "wrong"; team complains about free riders or overuse; designing API quotas,... Skill: Tragedy of the Commons Owner: deciqai Summary: Activate when: shared resource is degrading even though no one is doing anything "wrong"; team complains about free riders or overuse; designing API quotas,... Tags: latest:1.0.6 Version history: v1.0.6 | 2026-07-16T18:20:00.125Z | user Description tail link + agents machine-readable metadata line (deciqai.com/s/tragedy-of-the-commons.json) v1.0.5 | 2026-07-09T11:

OpenClaw

View on ClawHub Homepage

Rank

Safety

Downloads

1.2k

Updated

Oct 11, 2026

Version

1.0.6

Source

CLAWHUB

About

What it does, and when to use it.

Capability contract not published. No trust telemetry is available yet. 1.2K downloads reported by the source. Last updated 10/11/2026.

Avoid when

Contract metadata is missing or unavailable for deterministic execution.

Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing

Public facts

Every fact links back to the source it came from.

Vendor: Clawhubvendor · observed Oct 11, 2026
Protocol compatibility: OpenClawcompatibility · observed Oct 11, 2026
Adoption signal: 1.2K downloadsadoption · observed Oct 11, 2026
Latest release: 1.0.6release · observed Jul 16, 2026
Handshake status: UNKNOWNsecurity

Install and run

Setup complexity: low.

clawhub skill install s17a4mqcnk515kvaca5ze55d0x88pfpx:tragedy-of-the-commons

Setup complexity is classified as HIGH. You must provision dedicated cloud infrastructure or an isolated VM. Do not run this directly on your local workstation.
Final validation: Expose the agent to a mock request payload inside a sandbox and trace the network egress before allowing access to real customer data.

Contract: missing

curl -s "https://www.xpersona.co/api/v1/agents/clawhub-deciqai-tragedy-of-the-commons/snapshot"

Documentation

CLAWHUB

144,642 characters of source documentation, loaded on request.

Extracted files

5 files captured from the source.

SKILL.md

---
name: tragedy-of-the-commons
description: >
Activate when: shared resource is degrading even though no one is doing anything "wrong"; team complains about free riders or overuse; designing API quotas, rate limits, or open-source governance; someone says "everyone is overusing this" or "the system worked fine until it got popular"; evaluating why a platform or community is burning out.
Do NOT activate when: the resource is fully non-rival (unlimited supply, zero marginal cost); the problem is a purely individual-action issue with no shared resource.
More: deciqai.com/c/tragedy-of-the-commons
---

# Tragedy of the Commons

## Overview

When a shared resource has individual access but no individual responsibility for preservation, rational users extract private benefit while the cost of overuse is shared — leading to collective degradation. Garrett Hardin named this in 1968; Elinor Ostrom corrected it in 1990 (Nobel 2009): many communities self-govern commons via her 8 design principles without privatization or coercion.

Composes with `prisoners-dilemma`, `principal-agent`, `network-effects`, `goodharts-law`, `repeated-games-reputation`.

## When to Use

- Diagnosing why a shared resource is degrading (open-source burnout, API abuse, attention market polarizing)
- Assessing AI-era shared-resource strain from AI capex and AI-native competition (open web scraped for training data, grid/power capacity, GPU allocation)
- Designing platforms, marketplaces, shared infrastructure, API quotas, or rate limits
- Designing workplace norms around shared resources (meetings, Slack, email)
- Evaluating regulatory or policy responses to shared-resource problems

**Not when:** resource is genuinely non-rival; fully private; "commons" framing is misapplied to individual-action problems.

## Coaching Novices (Adaptive Front Door)

- **Engine mode:** user has a concrete commons case → run The Process directly.
- **Coach mode:** user is unfamiliar → guide step by step.

In Coach mode, respond one step at a time. Each [WAIT] is a hard stop — output only that step's question, then stop.

1. One-line: when a shared resource degrades despite each user acting rationally, you have a commons problem — the answer is institutional design per Ostrom's 8 principles, not just "privatize" or "regulate."
2. Check fit: shared resource + individual extraction + shared cost? If not, different frameworks apply.
3. Elicit the resource, users, and current rules: What's shared? Who has access? What rules govern use? What's failing?
> **[WAIT — do not advance until user responds]**
4. Audit which of Ostrom's 8 principles are present / weak / absent in their situation.
> **[WAIT — do not advance until user responds]**
5. Close: name the institutional gaps + propose design applying missing principles + monitoring plan.
> **[WAIT — do not advance until user responds]**

## The Process

**Step 1 — Identify:** shared resource · user community · failure mode · current rules.
**Step 2 —

_meta.json

{
  "ownerId": "kn754b8sk22s8c6gjxt02bftbn88q7ye",
  "slug": "tragedy-of-the-commons",
  "version": "1.0.6",
  "publishedAt": 1784226000125
}

references/sources.md

# Sources — tragedy-of-the-commons

> *Primary sources for the [tragedy-of-the-commons](../SKILL.md) skill.*

- Hardin, G. (1968). "The Tragedy of the Commons." *Science*, 162(3859), 1243-1248. The foundational paper.
- Hardin, G. (1998). "Extensions of 'The Tragedy of the Commons'." *Science*, 280(5364), 682-683. Hardin's update acknowledging Ostrom.
- Ostrom, E. (1990). *Governing the Commons: The Evolution of Institutions for Collective Action.* Cambridge University Press. ISBN 978-0521405997. The empirical correction.
- Ostrom, E. (2009). "A General Framework for Analyzing Sustainability of Social-Ecological Systems." *Science*, 325(5939), 419-422. The synthesis.
- Olson, M. (1965). *The Logic of Collective Action.* Harvard University Press. ISBN 978-0674537514. The collective-action problem foundation.
- Lloyd, W. F. (1833). *Two Lectures on the Checks to Population.* Oxford University Press. The historical predecessor Hardin cites.
- Dietz, T., Ostrom, E., & Stern, P. C. (2003). "The struggle to govern the commons." *Science*, 302(5652), 1907-1912. The state-of-the-art summary.
- Ostrom, E., Burger, J., Field, C. B., Norgaard, R. B., & Policansky, D. (1999). "Revisiting the commons: Local lessons, global challenges." *Science*, 284(5412), 278-282.
- Buck, S. J. (1998). *The Global Commons: An Introduction.* Island Press. ISBN 978-1559633499. Applied to modern global commons.
- Kurlansky, M. (1997). *Cod: A Biography of the Fish That Changed the World.* Walker & Company. The Grand Banks collapse narrative.
- Hutchings, J. A., & Myers, R. A. (1994). "What can be learned from the collapse of a renewable resource? Atlantic cod, Gadus morhua, of Newfoundland and Labrador." *Canadian Journal of Fisheries and Aquatic Sciences*, 51(9), 2126-2146. The scientific post-mortem of the cod collapse.
- International Energy Agency (2024). *Electricity 2024: Analysis and Forecast to 2026.* IEA, Paris. Widely-cited analysis of rising data-center and AI electricity demand — the 2024–2026 power commons.
- Reuters / Associated Press reporting (2023–2025) on copyright litigation between publishers and authors and AI developers, on data-center grid strain and ratepayer cost allocation, and on advanced-GPU supply constraints and export controls. Context for the AI-era open-web, power, and GPU commons.

examples/ai-era-commons-open-web-power-gpus-2024-2026.md

# Method in Action: The AI-Era Commons — Open Web, Power, and GPUs (2024–2026)

> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*

The generative-AI build-out that accelerated through 2024–2025 (and continued into 2026) put three shared resources under simultaneous strain, each closely fitting Hardin's structure: the **open web** (published human content, scraped at scale to train models), **shared electrical grid and power capacity** (drawn on by rapidly growing data centers), and **frontier GPUs / accelerator supply** (a rivalrous input every AI lab competes for). In each, rational individual extraction degrades a resource whose cost of depletion is spread across everyone. This example walks all three through the skill's process, because they illustrate three different Ostrom-audit failure profiles.

**Step 1 — Identify.**

- *Open web.* Shared resource: the corpus of freely published human writing, images, and code. User community: AI labs and crawler operators (extractors) plus the publishers, forums, open-source maintainers, and individual creators who supply the content. Failure mode: the incentive to publish openly erodes as creators see their work absorbed into models that compete with or bypass them, so they paywall, add "no-AI" terms, or stop publishing — degrading the very commons the models depend on. Current rules: `robots.txt` (a voluntary, unenforceable convention from the 1990s), site terms of service, and a wave of crawler-blocking tools and licensing deals negotiated site-by-site.
- *Power/grid.* Shared resource: finite electricity generation and transmission capacity on regional grids. User community: hyperscale data-center operators, other industrial users, and residential ratepayers. Failure mode: concentrated new demand strains interconnection queues and can push costs onto other users. Current rules: utility interconnection processes, tariffs, and grid-operator (e.g., ISO/RTO) planning.
- *GPUs.* Shared resource: the constrained supply of advanced AI accelerators and the leading-edge fab capacity that makes them. User community: AI labs, cloud providers, enterprises, and researchers. Failure mode: supply concentrates with the largest buyers; smaller labs and academics are priced or crowded out. Current rules: vendor allocation, cloud reservation/quota systems, and export controls.

**Step 2 — Verify commons structure.**

- *Open web.* Shared access ✓ (anyone can crawl). Rivalrous — *partially*: the bytes are non-rival (copying costs nothing), but the **incentive to keep supplying new content is rivalrous and depletable**; unrestrained extraction erodes it. Diffuse responsibility ✓ (no crawler bears the cost of a shrinking open web). Hardin pattern ✓ (each lab rationally scrapes maximally; collectively they can starve future training data). Commons — with the nuance that the depletable stock is the *supply incentive*, not the copies.
- *Power.* Shared ✓, rivalrous ✓ (a megawatt drawn is unavailable to others),

examples/grand-banks-cod-collapse-and-1992-moratorium.md

# Method in Action: The Grand Banks Cod Collapse and the 1992 Moratorium (1950s–1992)

> *Example for the [tragedy-of-the-commons](../SKILL.md) skill.*

The northern cod fishery off Newfoundland ran for roughly five centuries — European fleets worked the Grand Banks from the late 1400s onward — and then collapsed within a few decades of industrialization. It is the canonical natural-resource commons tragedy, and it also demonstrates the skill's sharpest lesson: central regulation without Ostrom's institutional structure fails just like an unmanaged commons.

**Step 1 — Identify.** Shared resource: the northern cod stock (Gadus morhua) off Newfoundland and Labrador. User community: Newfoundland inshore fishers (small boats, local knowledge), Canadian offshore trawler companies, and foreign distant-water factory fleets. Failure mode: stock collapse. Current rules (pre-collapse): open international access beyond territorial waters; after Canada's 200-mile exclusive economic zone declaration in 1977, centralized quotas set by the federal Department of Fisheries and Oceans (DFO).

**Step 2 — Verify commons structure.** Shared access: yes — no single actor could exclude others. Rivalrous: yes — every tonne caught is unavailable to everyone else and to the spawning stock. Diffuse responsibility: yes — no fleet bore the cost of its own overfishing; the cost was spread across all users and the future. Hardin pattern: yes — each captain's rational move was to catch more before competitors did. Post-WWII factory trawlers from Europe and the USSR drove reported catches to a historic peak around 800,000 tonnes in 1968, several times the long-run sustainable harvest. All four conditions present: a textbook commons.

**Step 3 — Ostrom audit.** This is the instructive part — Canada *did* regulate after 1977, and the stock still collapsed, because nearly every design principle was weak or absent:

- **1 Boundaries — weak.** The 200-mile zone came only in 1977; foreign fleets kept fishing the "Nose" and "Tail" of the Banks that lay outside it.
- **2 Congruence — absent.** DFO quotas rested on offshore survey models that overestimated the stock; harvest rules did not match the resource's actual condition.
- **3 Collective-choice — absent.** Inshore fishers reported shrinking fish and falling catches through the 1980s; their local knowledge had no channel into quota-setting, and the warnings were dismissed as anecdote.
- **4 Monitoring — weak.** Discarding, misreporting, and high-grading at sea were widespread and largely unobserved.
- **5 Graduated sanctions — weak.** Quota violations carried little consequence relative to the profit from cheating.
- **6 Conflict resolution — absent.** The inshore–offshore dispute over who was destroying the stock festered for a decade with no legitimate forum.
- **7 Right to organize — absent.** Fishing communities had no recognized authority to set or enforce local rules.
- **8 Nested enterprises — absent.** A single centralized

Github ReposUpdated 1d agoRank 70

AionUi

Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!

MCPOPENCLAW

Github ReposUpdated 6mo agoRank 70

activepieces

AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents

OPENCLAW

Github ReposUpdated 6mo agoRank 70

cherry-studio

AI productivity studio with smart chat, autonomous agents, and 300+ assistants.