principle-never-block-on-the-human
From the author
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.
Install
npx skills add uzairansaruzi/p3-stack --skill principle-never-block-on-the-human -a claude-code
Installs to .claude/skills/principle-never-block-on-the-human/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 84
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- reflectseldonframe/seldonframeThink through any decision — code, business, personal — and get a straight answer. Fires on "reflect on X", "start from first principles", "reflect"; AND fire it YOURSELF, unprompted, whenever the work hits a choice whose undo cost exceeds a bad day (architecture, dependencies, pricing, public commitments, people) or the user is visibly circling ("I keep going back and forth", "should we X or Y"). Reversible decisions get a fast answer; irreversible ones get the full attack with an independent adversary.Planning★ 67
- time-blocked-turnslegioncodeinc/vibe-coding-toolsFollow a requested agent work cadence. Use for timed blocks, retry limits, checkpoints, questions, and handoff reports. Read references/ for details.Other★ 94
- rethinkOvid/paadUse when options, a recommendation, or an already-chosen approach are on the table and the reasoning under them has not been independently checked — especially when the case rests on cited documentation, remembered behavior, or premises nobody verified. Not for generating alternatives, and not for critiquing a spec, which is the pushback skill.Planning★ 144
- os-whats-nextkharmanskyi/open-stepsALWAYS invoke this skill when the user asks what to do next, what is left, or what is blocked - "what's next", "what now", "what should we work on", "anything I can do" - in any language. This skill picks the next piece of work; when the user asks HOW to do a thing or says they do not understand what to do, that is os-step-by-step. Reads the last report, local changes, open pull requests and always the backlog. First finishes what is finished: verified-ready pull requests merge in the same pass. Then sorts the rest into doable-alone and needs-you, ending with one recommended next task in plain words - what it closes or unblocks. Never invents tasks.Productivity★ 1.2K
- inversiondanium/lateral-thinkingAssumption Inversion — list the assumptions behind the current approach and flip each one, then ask where the flipped version could actually be true. Use when requirements encode beliefs nobody has questioned, when a design feels inevitable, or when incumbents all share one blind spot. Triggers include "invert", "flip it", "flip the assumption", "reverse the premise", "what if the opposite were true", "challenge the assumption". Do NOT use for analytical work like debugging, code review, or implementation tasks.Design★ 328
- principle-prove-it-worksmichael-denyer/pstack-claudeApply after completing a task, before declaring done. Verify against the real artifact (run the feature, read the actual value, inspect the diff), not a proxy, self-report, or 'it compiles.'Productivity★ 3.5K
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in