Agent skill
approval-workflow
Manages Human-in-the-Loop (HITL) approval workflows for sensitive actions. Use when creating approval requests, processing approved items, or implementing safety controls for autonomous actions.
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/approval-workflow
SKILL.md
Approval Workflow Skill
This skill implements the Human-in-the-Loop (HITL) approval system that ensures human oversight for sensitive autonomous actions.
Core Concept
The approval workflow uses folder-based state management:
/Pending_Approval/ → Human reviews → /Approved/ → Execute
→ /Rejected/ → Archive
Approval Request Format
---
type: approval_request
action: [action_type]
created: [ISO timestamp]
expires: [ISO timestamp]
status: pending
priority: [critical|high|medium|low]
requestor: [agent_name]
risk_level: [low|medium|high]
reversible: [true|false]
---
## Action Summary
[Brief description of what will happen]
## Details
[Full action parameters]
## Risk Assessment
- **Reversible**: [Yes|No|Partial]
- **Impact**: [Description]
- **Sensitive Data**: [Yes|No]
## Instructions
- **Approve**: Move to `/Approved/`
- **Reject**: Move to `/Rejected/`
- **Edit**: Modify, then approve
Approval Thresholds
| Action Type | Auto-Approve | Human Required |
|---|---|---|
| Email (known contact) | Reply only | New recipients |
| Payment | < $50 recurring | New payee, > $100 |
| Social post | Scheduled | Immediate, replies |
| File operations | Create/read | Delete |
| Greetings | Business msgs |
Workflow States
- pending - Awaiting human decision
- approved - Cleared for execution
- rejected - Denied by human
- expired - Timed out without decision
- executed - Action completed
- failed - Execution error
Reference
For detailed implementation, see reference.md
For usage examples, see examples.md
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?