/pending-approvals
Use when the user asks to list, inspect, approve, reject, or revoke pending approvals -- "qué aprobaciones tengo pendientes", "aprueba esto", "rechaza esa aprobación", "revoca el permiso", "show pending approvals", "approve this".
Claude Code
$ npx -y skills add metraton/gaia --skill pending-approvals --agent claude-code
Codex
$ npx skills add metraton/gaia --skill pending-approvals -a codex -y
Cursor
$ npx skills add metraton/gaia --skill pending-approvals -a cursor -y
Gemini CLI
$ npx skills add metraton/gaia --skill pending-approvals -a gemini-cli -y
GitHub Copilot
$ npx skills add metraton/gaia --skill pending-approvals -a github-copilot -y
OpenCode
$ npx skills add metraton/gaia --skill pending-approvals -a opencode -y
Windsurf
$ npx skills add metraton/gaia --skill pending-approvals -a windsurf -y
SKILL.md
pending-approvals.SKILL.mdname: pending-approvals
description: Use when the user asks to list, inspect, approve, reject, or revoke pending approvals -- "qué aprobaciones tengo pendientes", "aprueba esto", "rechaza esa aprobación", "revoca el permiso", "show pending approvals", "approve this".
Pending Approvals
Pending approvals are not resurfaced in later sessions on their own. Recovery is explicit: the user asks to list pendings or supplies an approval id. Every lookup and single-item decision takes the complete canonical `P-<32 lowercase hex>` id; a short label is never a lookup key.
Reading
- `gaia approvals pending` -- the undecided requests, all sessions by default
(`--session <id>` narrows).
- `gaia approvals list` -- grants with STATUS, GRANT_STATE and OUTCOME
columns, and the undecided requests beneath them with their STATE (`--session`, `--orphans-only` for the orphaned ones, `--json`).
- `gaia approvals show <approval_id>` -- one approval: State, Outcome, Reason,
Requester, Window, Directory, the grant and the sealed payload.
- `gaia approvals history [<approval_id>]` -- recent approvals, or one
approval's event chain.
- `gaia approvals stats` -- counts by state and outcome.
Every reader names an approval by one derived state; `reference.md` lists them.
Deciding
The user decides on the signature Gaia shows (`orchestrator-present-approval`). From a terminal, the user can also run `gaia approvals approve <approval_id>`: it creates the grant exactly as Approve on the question does.
The orchestrator withdraws but never approves. It may run `gaia approvals reject <approval_id>` (a pending request becomes `rejected`) and `gaia approvals revoke <approval_id>` (an armed grant can no longer be used) -- for example to retire an orphaned request. Both accept `--reason <text>`, which the withdrawal event records. Approving, replaying, and the bulk verbs (`reject --all`, `reject-all`, `clean`) are the user's, or a specialist's when the user asks for them.
A set that ended `failed` is frozen: show its completed, failed and untouched commands as history; anything still needed is a new request.
Read more
name: pending-approvals description: Use when the user asks to list, inspect, approve, reject, or revoke pending approvals -- "qué aprobaciones tengo pendientes", "aprueba esto", "rechaza esa aprobación", "revoca el permiso", "show pending approvals", "approve this".
Pending Approvals
Pending approvals are not resurfaced in later sessions on their own. Recovery is explicit: the user asks to list pendings or supplies an approval id. Every lookup and single-item decision takes the complete canonical `P-<32 lowercase hex>` id; a short label is never a lookup key.
Reading
- `gaia approvals pending` -- the undecided requests, all sessions by default
(`--session <id>` narrows).
- `gaia approvals list` -- grants with STATUS, GRANT_STATE and OUTCOME
columns, and the undecided requests beneath them with their STATE (`--session`, `--orphans-only` for the orphaned ones, `--json`).
- `gaia approvals show <approval_id>` -- one approval: State, Outcome, Reason,
Requester, Window, Directory, the grant and the sealed payload.
- `gaia approvals history [<approval_id>]` -- recent approvals, or one
approval's event chain.
- `gaia approvals stats` -- counts by state and outcome.
Every reader names an approval by one derived state; `reference.md` lists them.
Deciding
The user decides on the signature Gaia shows (`orchestrator-present-approval`). From a terminal, the user can also run `gaia approvals approve <approval_id>`: it creates the grant exactly as Approve on the question does.
The orchestrator withdraws but never approves. It may run `gaia approvals reject <approval_id>` (a pending request becomes `rejected`) and `gaia approvals revoke <approval_id>` (an armed grant can no longer be used) -- for example to retire an orphaned request. Both accept `--reason <text>`, which the withdrawal event records. Approving, replaying, and the bulk verbs (`reject --all`, `reject-all`, `clean`) are the user's, or a specialist's when the user asks for them.
A set that ended `failed` is frozen: show its completed, failed and untouched commands as history; anything still needed is a new request.
Generative AI Interface for Agents. Specialist agents for Claude Code and OpenCode, with a memory that outlives the session and a consent gate on everything that changes state.
Other skills on gaia.
More skills from other plugins.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or…
ask-matt
Ask which skill or flow fits your situation. A router over the skills in this repo.
Questions about pending-approvals.
- Which coding agents can use pending-approvals?
- pending-approvals installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.

