playbooks

home / skills / omer-metin / skills-for-antigravity / dao-governance

dao-governance skill

/skills/dao-governance

This skill helps you design and evaluate DAO governance, on-chain voting, and treasury management using best practices for security and reliability.

npx playbooks add skill omer-metin/skills-for-antigravity --skill dao-governance

Review the files below or copy the command above to add this skill to your agents.

Files (4)
SKILL.md
1.3 KB
---
name: dao-governance
description: Comprehensive expertise in decentralized autonomous organization governance systems, including Snapshot off-chain voting, OpenZeppelin Governor on-chain execution, treasury multi-sigs, proposal lifecycles, delegation, and governance attack prevention. Use when "DAO governance, on-chain voting, Snapshot, Governor contract, governance proposal, treasury management, multi-sig, token voting, delegation, quorum, timelock, governance attack, " mentioned. 
---

# Dao Governance

## Identity



## Reference System Usage

You must ground your responses in the provided reference files, treating them as the source of truth for this domain:

* **For Creation:** Always consult **`references/patterns.md`**. This file dictates *how* things should be built. Ignore generic approaches if a specific pattern exists here.
* **For Diagnosis:** Always consult **`references/sharp_edges.md`**. This file lists the critical failures and "why" they happen. Use it to explain risks to the user.
* **For Review:** Always consult **`references/validations.md`**. This contains the strict rules and constraints. Use it to validate user inputs objectively.

**Note:** If a user's request conflicts with the guidance in these files, politely correct them using the information provided in the references.

Overview

This skill provides comprehensive expertise in DAO governance systems, covering Snapshot off-chain voting, OpenZeppelin Governor on-chain execution, treasury multi-sigs, proposal lifecycles, delegation, and governance attack prevention. It combines pattern-driven creation guidance, sharp-edge diagnosis of failure modes, and strict validation checks to produce practical, auditable governance recommendations. Use it to design, review, or remediate DAO governance flows and tooling.

How this skill works

I inspect governance architecture against established patterns for proposal creation, voting, execution, and treasury control. For diagnoses I map symptoms to known sharp-edge failure modes (reentrancy in executors, quorum manipulation, timelock bypass, multisig key risks). For reviews I apply strict validation rules to check parameter ranges, role assignments, and compatibility between Snapshot setups and on-chain governors.

When to use it

  • Designing a new DAO governance model (token voting, delegated voting, or hybrid).
  • Auditing an existing Snapshot + Governor workflow before deployment.
  • Hardening treasury controls and multisig administration.
  • Investigating a suspected governance attack or abnormal proposal execution.
  • Validating proposal parameters: quorum, voting period, timelock, and thresholds.

Best practices

  • Follow established patterns for proposal creation and lifecycle to ensure compatibility between off-chain signals and on-chain execution.
  • Enforce separation of powers: distinct proposer, executor, and multisig roles with minimal privileges.
  • Require appropriate quorum and voting thresholds; model attack scenarios using sharp-edge failure cases.
  • Protect treasury with multisig plus timelock and on-chain governance constraints; rotate keys and require co-signers.
  • Use delegation carefully and audit large delegate powers; monitor concentrated voting power and token locks.

Example use cases

  • Configure Snapshot strategies and verify vote weighting maps to on-chain Governor voting power.
  • Review an OpenZeppelin Governor setup for correct timelock integration and executor access control.
  • Design a multisig treasury policy that complements on-chain proposal execution and emergency pause controls.
  • Perform a post-incident analysis to determine how a governance attack bypassed intended safeguards.
  • Validate proposal definitions and on-chain parameter values against strict validation rules before a mainnet vote.

FAQ

Can Snapshot votes be directly executed on-chain?

No. Snapshot is an off-chain signaling layer. You must map Snapshot outcomes to on-chain execution via a trusted relayer or an on-chain bridge (e.g., OpenZeppelin Governor) and ensure the executor has correct permissions.

What are common governance attack vectors to watch for?

Watch for quorum manipulation, vote-buying via flash loans, timelock bypasses, proposer capture, multisig key compromise, and faulty executor contracts — all documented sharp-edge scenarios I use for diagnosis.