principle-never-block-on-the-human
From the author
Apply when tempted to ask 'should I do X?' on reversible work.
Install
npx skills add backnotprop/pstack --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.
Download .zip
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 90
Security100
Provenance82
Maintenance100
Licence100
Adoption55
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.
- principlesOutlineDriven/outline-driven-developmentUse when a request names a working principle (subtract before you add, idempotent operations, never block on the human) or asks which principle applies. Not for running a repair: use strike-the-root.Other★ 55
- 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
- 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
- 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★ 329
- 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 /pushback.Planning★ 146
- prompt-engineeringericrisco/rsc-harnessUse when one prompt must give the same right answer across reruns, models, and pasted-in hostile input: forcing a fixed schema, picking the few-shot set, ordering the prompt blocks, or the inline cases you run while tuning. NOT the agent loop, tools, or retrieval (that is `building-agents`), NOT a standing CI eval harness (that is `agent-eval`).Other★ 350
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in