Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Structural authority separation for autonomous agent actions. Three-phase governance pipeline: PROPOSE, DECIDE, PROMOTE. No action is both proposed and appro...
Structural authority separation for autonomous agent actions. Three-phase governance pipeline: PROPOSE, DECIDE, PROMOTE. No action is both proposed and appro...
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Governance guard enforces structural authority separation on all agent actions through a PROPOSE-DECIDE-PROMOTE pipeline.
Before performing any write, execute, network, create, or delete action. The governance pipeline MUST be invoked before the action executes. Read actions may also be governed under standard or strict policies.
Run the complete PROPOSE → DECIDE → PROMOTE pipeline in a single call: npx tsx scripts/governance.ts pipeline '<intent-json>' --policy policies/standard.yaml The intent JSON must include: skill: skill identifier tool: tool/function being invoked model: LLM model name actionType: one of read, write, execute, network, create, delete target: resource being acted upon parameters: tool parameters (object) dataScope: data categories accessed (array, e.g. ["personal", "financial"]) conversationId: current conversation ID messageId: current message ID userInstruction: the user message that triggered this action
The pipeline returns a JSON response: If "governance": "approved" — proceed with the action If "governance": "deny" — do NOT proceed; inform the user with the reason If "governance": "escalate" — present the action to the user for approval: Action requires your approval: Skill: <skill> Action: <actionType> on <target> Reason: <reason> Reply APPROVE or DENY Then resolve: npx tsx scripts/governance.ts resolve-escalation <intent-id> approve # or npx tsx scripts/governance.ts resolve-escalation <intent-id> deny
npx tsx scripts/governance.ts audit --last 10
PresetDefaultDescriptionminimalapproveBlocks only credentials and destructive commands. Lowest friction.standarddenyAllows common ops, escalates network and data access. Recommended.strictdenyReads only. Everything else requires explicit approval. Maximum safety.
If any error occurs during governance evaluation, the default verdict is DENY. Missing policy files result in DENY ALL. This is by design. The system fails safe, never open.
Governance data is stored in ~/.openclaw/governance/: policy.yaml — active policy file witness.jsonl — append-only, hash-chained audit log
npx tsx scripts/governance.ts verify Any tampering with historical records is detected by recomputing the hash chain from genesis.
Long-tail utilities that do not fit the current primary taxonomy cleanly.
Largest current source with strong distribution and engagement signals.