pre-authorization-protocol

Community

Pre-consent emergency powers, prevent crisis capture.

AuthorJadeZaher
Version1.0.0
Installs0

System Documentation

What problem does it solve?

This Skill prevents the abuse of power during crises by establishing clear, pre-approved emergency roles, authority limits, and expiration dates before a crisis occurs. It ensures that emergency responses are structural executions of pre-consented plans, not improvised power grabs driven by fear.

Core Features & Use Cases

  • Define Emergency Roles: Establish specific roles (e.g., Safety Coordinator, Resource Coordinator) needed during crises.
  • Scope Authority: Clearly define what each role can and cannot do, including spending limits and contract durations.
  • Automated Expiration: Ensure all emergency authorities have built-in expiration timers.
  • Irreducible Constraints: Enforce non-negotiable boundaries that emergency powers cannot violate (e.g., cannot amend foundational agreements).
  • Use Case: Before any emergency strikes, SHUR Bali defines that in case of a physical safety crisis, the Safety Coordinator can spend up to $5,000 on immediate needs and sign contracts up to 14 days, with their authority expiring once the safety criterion is met or after 30 days.

Quick Start

Use the pre-authorization-protocol skill to define a new emergency role for resource allocation during a financial crisis.

Dependency Matrix

Required Modules

None required

Components

assets

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: pre-authorization-protocol
Download link: https://github.com/JadeZaher/neos-operating-system/archive/main.zip#pre-authorization-protocol

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 223,000+ vetted skills library on demand.