approval-skill

Gate privileged tool calls behind admin approval tokens and optional 2FA.

Updated Mar 27, 2026
One-click install
npx skills add https://github.com/misunders2d/ori --skill approval-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: approval-skill
Source: https://github.com/misunders2d/ori/tree/main/skills/approval-skill
Command: npx skills add https://github.com/misunders2d/ori --skill approval-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Privileged actions (delete, force-push, mass-modify, send-public-message, etc.) don't execute immediately. The plugin layer AdminGatePlugin intercepts the tool call and returns an action token instead.

Core Features & Use Cases

  • Token-based approvals: bound to actions that require authorization, ensuring human oversight before execution.
  • Action queuing and review: pending actions are stored in data/pending_actions.db until approved or canceled.
  • Optional 2FA: supports six-digit TOTPs when configured, enforcing stronger security for critical operations.

Quick Start

Approve a pending privileged action by sending "Approve ACT-XXXXXX" (and your 6-digit code if 2FA is enabled) to authorize the queued operation.

Frequently Asked Questions about approval-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I require admin approval for privileged actions like force-push or delete?

To require admin approval for privileged actions, this Skill uses an AdminGatePlugin to intercept sensitive tool calls and return an action token instead of executing immediately. Pending operations are queued for human review until explicitly approved.

How does token-based approval work for queued privileged operations?

Token-based approval works by intercepting sensitive tool calls and generating a unique action token. The pending action is stored in a local SQLite database until an administrator authorizes it by submitting the token and an optional 2FA code.

Can I use TOTP 2FA to secure sensitive mass-modify or delete operations?

Yes, you can secure sensitive operations with TOTP 2FA. When configured, the approval workflow requires a six-digit TOTP code alongside the action token to authorize queued privileged actions like mass-modify or delete.

What is the best way to authorize a pending privileged action in the workflow?

The best way to authorize a pending privileged action is to send an approval command containing the action token, such as "Approve ACT-XXXXXX". If 2FA is enabled, you must also include your six-digit TOTP code in the same message.

Do I need a database to queue pending admin approvals for destructive actions?

Yes, you need a database to queue pending admin approvals for destructive actions. The Skill uses a local SQLite database file to store intercepted privileged tool calls until they are explicitly approved or canceled by an administrator.

When should I use an approval gate for privileged tool calls?

You should use an approval gate for privileged tool calls whenever an action involves destructive or sensitive operations like delete, force-push, or mass-modify. This ensures human oversight before execution and prevents unintended system changes.