ostrom-commons-governance

Audit shared computational resource governance against Ostrom's eight design principles.

2|Updated Feb 11, 2026
One-click install
npx skills add https://github.com/curiositech/port-daddy --skill ostrom-commons-governance
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ostrom-commons-governance
Source: https://github.com/curiositech/port-daddy/tree/main/skills/ostrom-commons-governance
Command: npx skills add https://github.com/curiositech/port-daddy --skill ostrom-commons-governance

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps architects and operators evaluate and design governance for shared computational resources used by AI agents, preventing coordination failures like port conflicts, resource squatting, surveillance, and one-strike exiles. It translates Elinor Ostrom's eight design principles into actionable checks, evidence mappings, and concrete remediation steps tailored to agent coordination daemons and multi-tenant systems.

Core Features & Use Cases

  • Principle-by-principle audit: Walks through all eight Ostrom principles and provides SATISFIED / GAP assessments with concrete evidence points.
  • Remediation plans: For each gap it supplies numbered, implementable fixes (APIs, endpoints, config changes) and guidance on scope and escalation.
  • Artifacts & failure modes: Produces recommended artifacts (harbor cards, immutable trails, governance channels), lists common anti-patterns, and offers nesting and sanction strategies.
  • Use cases: Auditing coordination daemons (ports, files, locks), designing graduated sanctions and bonding mechanisms, adding project-level governance overrides, and making monitoring accountable.

Quick Start

Audit my multi-agent coordination daemon against Ostrom's eight design principles and produce a per-principle status report with evidence, gaps, and prioritized remediation steps.

Frequently Asked Questions about ostrom-commons-governance

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

FAQPage Schema
How do I audit multi-agent coordination daemons for resource governance failures?

To audit multi-agent coordination daemons, evaluate them against Ostrom's eight design principles to identify gaps in managing ports, file claims, locks, sessions, and pub/sub channels. This produces per-principle statuses with evidence mappings and concrete remediation steps to prevent coordination failures like port conflicts and resource squatting.

What are common anti-patterns in agent commons resource governance?

Common anti-patterns in agent commons resource governance include surveillance, one-strike exiles, and unaccountable monitoring of shared computational resources. The Ostrom principles audit identifies these failure modes and recommends artifacts like immutable trails and governance channels to establish accountable, graduated sanctions instead of immediate bans.

How do I design graduated sanctions for multi-agent shared resource conflicts?

Designing graduated sanctions for multi-agent shared resource conflicts involves applying Ostrom's principles to create bonding mechanisms and nesting strategies. The audit provides numbered, implementable fixes including API endpoints and configuration changes to enforce proportional responses rather than one-strike exiles for agents violating resource claims.

Does this approach work for evaluating pub/sub channel governance in multi-tenant agent deployments?

Yes, this approach works for evaluating pub/sub channel governance in multi-tenant agent deployments by auditing how shared computational resources are claimed and coordinated. It assesses whether daemons managing sessions, locks, and pub/sub channels satisfy Ostrom's principles for boundary definition, collective choice, and monitoring accountability.

What artifacts do I need to track governance of shared agent computational resources?

Artifacts needed to track governance of shared agent computational resources include harbor cards for resource allocation, immutable trails for audit accountability, and designated governance channels for conflict resolution. These artifacts map evidence to specific components and endpoints, satisfying Ostrom's monitoring and accountability principles.

How do I add project-level governance overrides for agent coordination systems?

Adding project-level governance overrides for agent coordination systems requires implementing nesting strategies aligned with Ostrom's principles, allowing higher-level governance structures to intervene when local resource allocation fails. The audit identifies gaps in current override mechanisms and provides concrete API and configuration changes to enable accountable escalation.