request-approval

Request explicit user approval when a hook blocks a mutative command.

3|1|Updated Nov 10, 2025
One-click install
npx skills add https://github.com/metraton/gaia --skill request-approval
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: request-approval
Source: https://github.com/metraton/gaia/tree/main/skills/request-approval
Command: npx skills add https://github.com/metraton/gaia --skill request-approval

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Mutative commands can be blocked by safety hooks; this skill provides a disciplined pattern to request user approval and record the outcome so operations can continue with consent.

Core Features & Use Cases

  • Attempt-first flow: try the command, let the hook block it with an approval_id, then emit plan_status: "APPROVAL_REQUEST" with the approval_id in the approval_request object.
  • Approval lifecycle: orchestrator and user own approval; the agent only records the event.
  • Risk management: suitable for T3 and other mutative operations requiring safeguards.

Quick Start

Attempt the command first, let the hook block it with an approval_id, then emit APPROVAL_REQUEST with the approval_id in your approval_request object.

Frequently Asked Questions about request-approval

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

FAQPage Schema
How do I request user approval when a mutative command is blocked by a hook?

To request user approval when a mutative command is blocked, attempt the command first, let the hook block it with an approval_id, then emit plan_status: APPROVAL_REQUEST with the approval_id in your approval_request object.

What is the approval lifecycle when an agent requests consent for blocked T3 operations?

The approval lifecycle for blocked T3 operations dictates that the orchestrator and user own the approval process, while the agent only records the event and waits for consent before retrying the execution.

How do I manage mutative operations that require an explicit plan review before execution?

Managing mutative operations requiring a plan review involves emitting an approval_request payload with the specific approval_id, ensuring the orchestrator handles consent and safely retries the blocked command.

When should I emit an APPROVAL_REQUEST status during workflow orchestration?

You should emit an APPROVAL_REQUEST status during workflow orchestration immediately after a safety hook blocks a mutative command, providing the approval_id so the orchestrator can pause and handle user consent.

Can I bypass safety hooks for mutative commands without an explicit user approval request?

No, mutative commands blocked by safety hooks require emitting a plan_status of APPROVAL_REQUEST with a valid approval_id, ensuring the orchestrator secures explicit user consent before the operation continues.