Skip to content
Back to skills

Human In The Loop Workflows

ASecurity

Implement approval-gated workflows for risky or irreversible actions. Use when users need plan-preview-approve execution, escalation on ambiguity, and clear checkpoints before changes are applied.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 29, 2026
businessrailssecurity

Security analysis

A100/100

Scanned September 29, 2026

npx -y skills add Arry8/openclaw-edge --skill human-in-the-loop-workflows --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Human In The Loop Workflows?

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

Security grade badge for Human In The Loop Workflows
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/arry8-human-in-the-loop-workflows/badge)](https://www.skillsdirectory.com/skills/arry8-human-in-the-loop-workflows)

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-in-the-loop-workflows
description: Implement approval-gated workflows for risky or irreversible actions. Use when users need plan-preview-approve execution, escalation on ambiguity, and clear checkpoints before changes are applied.
---

# Human-in-the-Loop Workflows

Use explicit approval gates for sensitive actions.

## Standard HITL pattern

Run this sequence:

1. Plan
2. Preview impact
3. Request approval
4. Execute approved step
5. Verify outcome
6. Summarize results

## Require approvals for

- destructive file/system changes
- external communications/actions
- privilege/access changes
- cost-impacting operations
- policy/security changes

## Approval request format

Keep approvals easy to answer:

- action
- exact command(s)
- expected impact
- rollback option
- reply choices (Approve / Revise / Cancel)

## Ambiguity handling

If user intent is unclear:

- pause execution
- ask one focused clarification
- do not guess on high-risk actions

## Batch approvals

For multiple related steps:

- group low-risk steps together
- isolate high-risk steps into separate approvals
- include checkpoint after each high-risk step

## Verification

After execution, report:

- what changed
- what was skipped
- evidence of success/failure
- recommended next step

## Guardrails

- No approval bypass.
- No hidden side-effects outside approved scope.
- Stop immediately on unexpected output and re-confirm.

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.

Comments

Loading comments…