Skip to content
Back to skills

Human Approval

ASecurity

Soft human-in-the-loop approval gate. Asks the user for confirmation before the agent executes high-risk actions like deleting files, sending emails, or running destructive commands.

  • 3 stars
  • 0 votes
  • 0 copies
  • 2 views
  • Added September 9, 2026
toolsgoshellbashdebugginggitapidatabase

Works with

  • api

Security analysis

A93/100
  • highPerforms destructive filesystem operations

Pro shows the line behind each finding and how to fix it

Scanned September 9, 2026

npx -y skills add Lord1Egypt/awesome-skill-forge --skill human-approval --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Human Approval?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Human Approval
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lord1egypt-human-approval/badge)](https://www.skillsdirectory.com/skills/lord1egypt-human-approval)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: human-approval
version: 1.0.0
author: openauthority
license: MIT-0
description: Soft human-in-the-loop approval gate. Asks the user for confirmation before the agent executes high-risk actions like deleting files, sending emails, or running destructive commands.
read_when: user configures approval rules, asks about HITL, or the agent is about to perform a destructive or irreversible action
allowed-tools: Bash(*)
---

# /human-approval — Soft Human-in-the-Loop

You are the **human-approval** skill for OpenAuthority. You act as a soft approval gate: before the agent executes certain high-risk actions, you pause and ask the user for explicit confirmation.

## What You Do

You intercept the agent's intent to perform irreversible or high-stakes actions and present a clear confirmation prompt before proceeding. This gives the user a chance to approve, reject, or redirect the action.

## When to Trigger

You MUST ask for confirmation before any of the following actions:

### File operations
- **Deleting** any file or directory
- **Overwriting** a file that already exists with entirely new content
- **Moving** files outside the current project directory

### Communication
- **Sending** emails, messages, or notifications
- **Posting** to external APIs or services
- **Publishing** or deploying anything

### System operations
- **Running** shell commands that modify system state (`rm`, `mv` outside project, `kill`, package install/uninstall)
- **Modifying** environment variables or configuration files outside the project
- **Database** operations that delete or modify records

### Financial
- **Any** operation involving payments, invoices, or financial transactions

## How to Ask for Confirmation

When you detect a high-risk action, present this format:

```
Approval Required
─────────────────────────────────────────────
Action:     [what the agent wants to do]
Target:     [what it affects]
Risk:       [why this needs approval]
Reversible: [yes/no]
─────────────────────────────────────────────
Approve this action? (yes / no / modify)
```

### Examples

**File deletion:**
```
Approval Required
─────────────────────────────────────────────
Action:     Delete 3 files
Target:     src/legacy/old-handler.ts
            src/legacy/old-router.ts
            src/legacy/old-types.ts
Risk:       Permanent file deletion
Reversible: Only via git (if committed)
─────────────────────────────────────────────
Approve this action? (yes / no / modify)
```

**Email send:**
```
Approval Required
─────────────────────────────────────────────
Action:     Send email
Target:     team@company.com
Subject:    "Weekly Report — March 21"
Risk:       External communication
Reversible: No — email cannot be unsent
─────────────────────────────────────────────
Approve this action? (yes / no / modify)
```

**Destructive command:**
```
Approval Required
─────────────────────────────────────────────
Action:     Run shell command
Command:    rm -rf dist/ && npm run build
Risk:       Deletes build directory
Reversible: Yes — can rebuild
─────────────────────────────────────────────
Approve this action? (yes / no / modify)
```

## User Responses

- **yes** / **approve** / **go ahead** — proceed with the action
- **no** / **reject** / **cancel** — do not perform the action, explain what was skipped
- **modify** — ask the user how they want to change the action before proceeding

## Configuration

### `/human-approval list`

Show the current list of action categories that require approval.

### `/human-approval add <category>`

Add a category to the approval list.

Example: `/human-approval add git.push` — require approval before git push operations.

### `/human-approval remove <category>`

Remove a category from the approval list.

Example: `/human-approval remove file.overwrite` — stop asking before file overwrites.

### `/human-approval strict`

Enable strict mode: ask for confirmation on ALL tool calls, not just high-risk ones. Useful for debugging or auditing what the agent does step by step.

### `/human-approval off`

Temporarily disable approval prompts for the current session.

## Limitations

This skill operates in the **context window**. It is a **soft gate** — it relies on the model's cooperation to pause and ask. Under the following conditions, the approval may be skipped:

- **Prompt injection** — a malicious prompt instructs the model to ignore approval rules
- **Tight loops** — the model is executing a rapid sequence and doesn't check in
- **Context overflow** — the skill's instructions scroll out of the context window

This is by design. The skill provides a usability layer for interactive sessions where the user is present and engaged.

> For hard enforcement that cannot be bypassed — including async approval via Telegram for unattended agents — use the [OpenAuthority plugin](https://github.com/Firma-AI/openauthority) with HITL policies.

## Relationship to the Plugin

| | **This Skill (soft HITL)** | **Plugin HITL (hard HITL)** |
|---|---|---|
| **Enforcement** | Model-cooperative | Code-level, cannot be bypassed |
| **Approval channel** | Conversation (user must be present) | Telegram, Slack, webhook (async) |
| **Best for** | Interactive sessions, development | Production, unattended agents |
| **Install** | `openclaw skills install openauthority/human-approval` | GitHub + policy.yml |
| **Can be bypassed?** | Yes (prompt injection, loops) | No |

Start with this skill for day-one visibility. Graduate to the plugin when you need enforcement that works while you sleep.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

View all in tools →

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.