approver

Defines the human approval task spec that parks requests until a person marks them done.

Updated Sep 2, 2026
One-click install
npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill approver-volter-ai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: approver
Source: https://github.com/volter-ai/open-autonomy-compiler/tree/main/profiles/hello-human/skills/approver
Command: npx skills add https://github.com/volter-ai/open-autonomy-compiler --skill approver-volter-ai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? In automated agent workflows, human approval steps can be silently skipped or auto-completed, breaking accountability. This Skill defines the human actor's task spec in the open-autonomy hello-human example so approval requests genuinely reach a person and wait for explicit confirmation. ## Core Features & Use Cases - Human-in-the-loop handoff: The requester agent engages the approver through the runner seam, which parks the ask and never completes it on its own. - Multiple notification channels: Asks are printed to the console, appended to .open-autonomy/runner-state/human-attention.md, and optionally sent via a configured AUTONOMY_HUMAN_ENGAGE_CMD hook. - Verified completion: The flow only resumes when the person runs bun scripts/runner.ts update <id> --status done, guaranteeing completion is verified rather than presumed. - Use Case: In a local open-autonomy installation, a requester agent needs sign-off before proceeding; the approver spec ensures the request reaches a human and blocks until that human explicitly marks it done. ## Quick Start Watch the human-attention file for new approval asks, then mark the parked session done with the runner update command once you have reviewed it.

Frequently Asked Questions about approver

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

FAQPage Schema
How do I handle human approval steps in an open-autonomy workflow?▼

Declare a kind: human actor like the approver and have the requester agent engage it via the runner launch command with an ask and completion condition. The runner parks the session until the person runs the update command with status done.

How are human approval requests delivered to the approver?▼

The runner prints the ask to the console and appends it to .open-autonomy/runner-state/human-attention.md. If the operator configured AUTONOMY_HUMAN_ENGAGE_CMD, that command also receives the session as JSON on stdin for paging or Slack notification.

Does the approver skill run an AI model or agent job?▼

No. The approver is a kind: human actor, so no model runs this skill and the local substrate emits no job or session for it. It is a task spec handed to a person, not an executable agent.

What happens if the human never marks the approval done?▼

The session stays in running state as bookkeeping only, and the requester keeps reporting it as pending. There is no other path to done, so the flow waits indefinitely rather than presuming completion.

Can the runner auto-complete a human approval session?▼

No. The runner parks the ask and never completes it on its own. Per the handoffs spec, a human's done status is verified, not presumed, and only the explicit update command resumes the flow.