Agent Skills
› sediman-agent/OpenSkynet
› principle-never-block-on-the-human
principle-never-block-on-the-human
GitHub指导代理在可逆工作中主动执行而非等待确认，通过异步提交结果让人类事后纠正。仅在不可逆操作或意图不明时请求确认，旨在减少阻塞，提升效率并尊重人类注意力。
Trigger Scenarios
代理犹豫是否应执行某项可逆工作时
需要决定是等待指令还是直接行动时
Install
npx skills add sediman-agent/OpenSkynet --skill principle-never-block-on-the-human -g -y
SKILL.md
Frontmatter
{
"name": "principle-never-block-on-the-human",
"description": "Apply when tempted to ask 'should I do X?' on reversible work. Proceed, present the result, let the human course-correct after the fact; reserve confirmation for irreversible actions.",
"disable-model-invocation": true
}
Never Block on the Human
The human supervises asynchronously. Agents must stay unblocked: make reasonable decisions, proceed, and let the human course-correct after the fact. Code is cheap. Waiting is expensive.
Why: Every permission pause stalls the pipeline and makes the human the bottleneck. Since code changes are reversible and reviewable, a wrong decision usually costs less than blocking.
Pattern:
- Proceed, then present. Do the work, show the result. Don't ask "should I do X?" Do X, explain why.
- Reserve questions for genuine ambiguity. Ask only when you truly cannot infer intent from context.
- Make the system self-healing. When you notice a problem, log it and fix it in the next round.
- Supervision is async. The human reviews plans, diffs, and changes on their own schedule. Design workflows for review-after-the-fact.
- Code is cheap, attention is scarce. A wrong implementation costs minutes to fix. A blocked agent costs the human's attention to unblock.
Boundaries:
- Irreversible actions (force-push, delete production data, send external messages) still require confirmation.
- Reversible actions (write code, edit notes, split tasks) should proceed without blocking.
- Product direction comes from the human; execution should not block.
Version History
- c9d8953 Current 2026-07-05 19:53
