grad-governance
Apply governance theory to analyze multi-level, network, and collaborative governance arrangements beyond traditional government. Use this skill when the user needs to evaluate public-private partnerships, analyze multi-stakeholder governance structures, compare governance models across sectors, or assess institutional arrangements for collective decision-making — even if they say 'who governs this', 'public-private collaboration', or 'how are decisions made across organizations'.
pinned to #4e7f4f8updated last month
Ask your AI client: “install skills/grad-governance”.
Requires the metahub MCP server installed in your client. Set up MCP.
mh install skills/grad-governancemetahub onboarded this repo on the author's behalf.
If you own github.com/asgard-ai-platform/skills on GitHub, claim the listing to take over publishing. Your claim preserves the existing eval history and badges; only the curator label is replaced with verified-publisher on your next publish.
Stars
225
Last commit
last month
Latest release
published
- #ai-agent
- #anthropic
- #claude
- #claude-agent-skills
- #claude-code
- #coding-agent
- #knowledge-base
- #mcp
- #methodology
- #open-source
- #prompt-engineering
- #skills
- #taiwan
Automated checks the publisher passed at publish time — structure, docs, safety, and whether the artifact behaves as claimed.4e7f4f8· last month
Behavioral checks ran but aren't published for this artifact; the static checks above ran at publish time.
Documentation
8 passed1 warningHomepage or repository declaredwarn
No homepage or repository declared.
Add a "homepage" or "repository" field to SKILL.md.
Description quality
58 words · 485 chars — "Apply governance theory to analyze multi-level, network, and collaborative gover…"
README is present and substantial
33,936 chars · 20 sections · 3 code blocks
Tags / topics declared
13 total — ai-agent, anthropic, claude, claude-agent-skills, claude-code, coding-agent (+7)
README has usage / example sections
no labeled section but 3 code blocks document usage
Homepage / docs URL declared
https://vault.asgard-ai.com/skills/
Description is substantive
Description is 58 words.
Documentation present and substantive
Documentation present (SKILL.md, 596 words).
Documentation shows usage
Documentation includes 2 code examples.
Release history
1- releasecurrent4e7f4f8warnlast month
Contents
Governance Theory
Overview
Governance theory examines how collective decisions are made and implemented through arrangements that extend beyond traditional government. It encompasses multi-level governance, network governance, public-private partnerships, and corporate governance, recognizing that governing increasingly involves non-state actors, markets, and networks.
When to Use
Trigger conditions:
- Analyzing decision-making structures involving multiple stakeholders across sectors
- Evaluating public-private partnerships or collaborative governance arrangements
- Comparing governance models (hierarchical, market, network)
When NOT to use:
- When analyzing individual policy decisions (use policy streams model)
- When studying stakeholder prioritization within a single organization (use stakeholder theory)
- When analyzing public official behavior as self-interested agents (use public choice theory)
Assumptions
IRON LAW: Governance Is NOT Government
Governance includes non-state actors, networks, and market mechanisms
in collective decision-making. Three ideal types:
1. HIERARCHY: authority-based, top-down, bureaucratic rules
2. MARKET: competition-based, price signals, contracts
3. NETWORK: trust-based, reciprocity, negotiation
No real-world arrangement is purely one type — governance analysis
identifies the MIX and evaluates its appropriateness for the context.
Methodology
Step 1: Map the Governance Arrangement
Identify all actors (state, private, civil society), their roles, authority relationships, and resource dependencies.
Step 2: Classify the Governance Mode
Determine the dominant governance mode (hierarchy, market, network) and assess the mix. Evaluate formal rules, informal norms, and power dynamics.
Step 3: Assess Performance
Evaluate against governance criteria: legitimacy, accountability, effectiveness, efficiency, equity, transparency. Identify trade-offs between criteria.
Step 4: Diagnose Failures
Identify governance failures: hierarchy failure (rigidity, bureaucratic pathology), market failure (externalities, information asymmetry), network failure (free-riding, exclusion, groupthink).
Output Format
# Governance Analysis: {Context/Policy Area}
## Actors and Roles
| Actor | Sector | Role | Resources | Authority |
|-------|--------|------|-----------|-----------|
| ... | State/Private/Civil Society | ... | ... | ... |
## Governance Mode
- Dominant mode: {hierarchy/market/network}
- Mix: {how modes combine}
- Formal rules: {legal/regulatory framework}
- Informal norms: {trust, reciprocity, power dynamics}
## Performance Assessment
| Criterion | Rating | Evidence |
|-----------|--------|----------|
| Legitimacy | ... | ... |
| Accountability | ... | ... |
| Effectiveness | ... | ... |
| Equity | ... | ... |
## Governance Failures
{Identified failures and their root causes}
## Recommendations
{Governance design improvements}
Gotchas
- Governance ≠ good governance: Governance is descriptive (how decisions ARE made). Good governance is normative (how decisions SHOULD be made). Don't conflate analysis with prescription.
- Network romanticism: Network governance is not inherently superior to hierarchy. Networks can exclude, reproduce inequality, and lack democratic accountability.
- Accountability gaps: Multi-level and network governance creates accountability challenges. When "everyone governs," no one may be accountable for outcomes.
- Context dependency: Governance arrangements that work in one institutional context may fail in another. Culture, legal tradition, and capacity affect governance effectiveness.
- Shadow of hierarchy: Even in network governance, government often retains ultimate authority. The "shadow of hierarchy" shapes network behavior even when not directly exercised.
References
- For multi-level governance frameworks, see
references/multi-level.md - For governance evaluation criteria and indicators, see
references/evaluation-criteria.md
Reviews
No reviews yet. Be the first.
Related
Verification Before Completion
Evidence before assertions, always
Writing Plans
Turn specs into phased implementation plans
Test-Driven Development
Red → green → refactor discipline for any feature or bugfix
mh install skills/grad-governance