ClawHub

Governance Explainer

v1.0.1

Explain DAO governance rules and implications clearly; translate constraints into allowed/forbidden actions with consequences.

⭐ 0· 127·0 current·0 all-time
byMauricio Z.@mzfshark

Install

OpenClaw Prompt Flow

Install with OpenClaw

Best for remote or guided setup. Copy the exact prompt, then paste it into OpenClaw for mzfshark/governance-explainer.

Previewing Install & Setup.
Prompt PreviewInstall & Setup
Install the skill "Governance Explainer" (mzfshark/governance-explainer) from ClawHub.
Skill page: https://clawhub.ai/mzfshark/governance-explainer
Keep the work scoped to this skill only.
After install, inspect the skill metadata and help me finish setup.
Use only the metadata you can verify from ClawHub; do not invent missing requirements.
Ask before making any broader environment changes.

Command Line

CLI Commands

Use the direct CLI path if you want to install manually and keep every step visible.

OpenClaw CLI

Bare skill slug

openclaw skills install governance-explainer

ClawHub CLI

Package manager switcher

npx clawhub@latest install governance-explainer
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
ℹ
Purpose & Capability
The name, description, and SKILL.md all align: the skill interprets governance text and outputs allowed/forbidden actions and consequences. It requests no binaries, environment variables, or external services — which is appropriate for an explanation/analysis-only skill. Note: there are small metadata mismatches between the provided registry metadata (version 1.0.1, owner ID kn741...) and the files (_meta.json and skill.yml show version 2.0.0 and owner 'morpheus-agent-001'); this is a provenance/integrity note rather than a functional mismatch.
✓
Instruction Scope
SKILL.md is narrow and prescriptive: it requires a governance_rule and context, defines step-by-step interpretation, and explicitly restricts behavior (do not route around governance; default to safer interpretation). It does not instruct the agent to read arbitrary files, access environment variables, or transmit data to external endpoints.
✓
Install Mechanism
There is no install spec and no code files to install or execute — this is an instruction-only skill. That is the lowest-risk installation profile.
✓
Credentials
The skill declares no required environment variables, credentials, or config paths. The runtime instructions do not reference any hidden env vars or credentials. Requested access is proportionate to an explanation/analysis capability.
✓
Persistence & Privilege
always is false (not force-included). The skill allows autonomous invocation (disable-model-invocation is false), which is the platform default and appropriate for a user-invocable analytical skill. The skill does not request elevated system persistence or modifications to other skills.
Assessment
This skill appears to do exactly what it says: interpret governance text and produce allowed/forbidden actions and consequences, and it does so without asking for secrets or installing code. Before installing: (1) verify the publisher/source because the registry metadata in your prompt differs from the files' _meta.json/owner/version — confirm you trust 'Morpheus' or the listed owner; (2) remember the skill gives interpretive guidance, not legal or binding governance decisions — validate important rulings with on-chain evidence, governance docs, or human council; (3) test the skill with non-sensitive, well-documented rules first to confirm behavior; and (4) if you need auditability, keep the inputs/outputs logged so decisions can be reviewed. Overall: internally coherent and low-risk, but confirm provenance due to the metadata/version mismatch.

Like a lobster shell, security has layers — review code before you run it.

latestvk973kbygnspe2ajrq7m5tyjd2585f6me
127downloads
0stars
2versions
Updated 3d ago
v1.0.1
MIT-0
Mauricio Z.@mzfshark
latest
Download

SKILL: governance-explainer

Purpose

Explain DAO rules and implications clearly, translating governance into practical constraints and safe actions.

When to Use

  • A user proposes an action that may violate governance
  • A rule/policy is referenced but unclear
  • A vote, authority boundary, or permission is in question

Inputs

  • governance_rule (required): the rule text or reference
  • context (required): situation + proposed action

Steps

  1. Interpret the rule in plain language (what it intends to constrain).
  2. Translate to action:
    • what is allowed
    • what is forbidden
  3. Identify prerequisites (votes, roles, approvals, thresholds).
  4. Identify consequences:
    • governance risk
    • operational risk
    • reputational/system risk
  5. If details are missing, ask the minimum clarifying questions.

Validation

  • Must align with the governance text as provided.
  • Clearly mark what is interpretation vs what is explicitly stated.

Output

  • simplified_explanation
  • allowed_actions
  • forbidden_actions
  • constraints
  • consequences

Safety Rules

  • Do not “route around” governance.
  • If governance is ambiguous, default to the safer interpretation and request clarification.

Example

Input: “Can we bypass the review process to ship today?” Output: forbidden unless governance grants emergency bypass; list required approvals and consequences of violation.

Comments

Loading comments...