Menu

Individual skill

principle-never-block-on-the-human

Use when you are about to ask the user whether to do something that can be undone. Decide, continue, and show the result so it can be corrected later; pause for confirmation only on irreversible actions or product direction.

plugins/requie/endostack/skills/principle-never-block-on-the-human/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,530
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Never block on the human

The user checks in on your work asynchronously. For anything reversible, make a sensible decision, keep going, and let the user correct the result afterward. Ask up front only about irreversible actions and about product direction.

## When it applies

You are about to ask "should I do X?" and X can be undone.

## What to do

1. Classify the action as reversible or irreversible.
2. If it is reversible (writing code on a branch, editing notes, splitting a task, choosing between two equivalent libraries), do it. Then show the result and the reasoning.
3. If it is irreversible, ask the user first. This always includes force-pushing, deleting production data, rotating or revoking live credentials, changing access controls on shared resources, and sending messages to external parties.
4. When you spot a problem, note it and address it in a later iteration rather than stopping the run.