mcpbeat Sign in

Grad Governance Agent Skill

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'.

11k tokens
context cost
the whole folder, loaded on every use
4
files
instructions only
0
copies elsewhere
how many repositories repackaged it
223
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/asgard-ai-platform/skills --skill grad-governance

What comes with it

37 339 bytes besides the instruction
examples/sample_scenario.md
references/evaluation-criteria.md
references/multi-level.md

The instruction itself

12 sections, as written by the author

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

Other skills for the same job

different authors, same section of the catalogue
Doc Coauthoring
by anthropics
vendor ×10

Guide users through a structured workflow for co-authoring documentation. Use when user wants to write documentation, proposals, technical specs, decision docs, or similar structured content. This workflow helps users efficiently transfer context, refine content through iteration, and verify the doc works for readers. Trigger when user mentions writing docs, creating proposals, drafting specs, or similar documentation tasks.

4k tokens
File Organizer
by frostant
×10

Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.

3k tokens
Domain Name Brainstormer
by frostant
×8

Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.

1k tokens
Brainstorming
by ZhanlinCui
×4

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

626 tokens
Planning With Files
by ZhanlinCui
×3

Implements Manus-style file-based planning for complex tasks. Creates task_plan.md, findings.md, and progress.md. Use when starting complex multi-step tasks, research projects, or any task requiring >5 tool calls.

9k tokens scripts
Scientific Brainstorming
by christophacham
×3

Creative research ideation and exploration. Use for open-ended brainstorming sessions, exploring interdisciplinary connections, challenging assumptions, or identifying research gaps. Best for early-stage research planning when you do not have specific observations yet. For formulating testable hypotheses from data use hypothesis-generation.

5k tokens
GitHub Project Management
by ComeOnOliver
×3

Comprehensive GitHub project management with swarm-coordinated issue tracking, project board automation, and sprint planning

14k tokens
Grill Me
by ComeOnOliver
×3

Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".

3k tokens

How to use it

Copy the folder

Take asgard-ai-platform/grad-governance from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.