agentleFS
hidenobunagaihidenobunagai/astack/skills/principle-never-block-on-the-human/SKILL.md

principle-never-block-on-the-human

Skill1 starsChanged 14 days agoMITView on GitHub

Apply when tempted to stop and ask 'should I do X?' during reversible analysis work, such as writing a query, adding a cleaning step, choosing a bin width, or drafting a chart. Proceed with a reasonable choice, state it, and let the human correct it afterward.

52 other projects use a version of this, 48 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use setup-pstack, poteto-help and 4 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • bnemaSkill

    setup-pstack

    Configure which Pi models pstack uses per role. Detects available provider/model specs and writes pstack's user configuration. Use for /setup-pstack, "configure pstack models", or changing pstack model choices.

    Also in 25 projects that use this

  • ianclearySkill

    poteto-help

    Guides users through pstack setup, /poteto-mode, and picking the skill, playbook, or principle for a task. Type /poteto-help with a question.

    Also in 14 projects that use this

  • eryzerzSkill

    make-bot-ui

    Use when building a custom UI (page, dashboard, buttons) that should wake a Grok Bot over a webhook, when the user must provide a webhook sender key, or when exposing that UI on Tailscale.

    Also in 19 projects that use this

  • tristanphvnSkill

    ketchup-video

    Catch the user up like /keel:ketchup, with a short silent video of slides for what happened and the waiting calls as text under it. Use for /keel:ketchup-video.

    Also in 11 projects that use this

  • JoshueOsunaSkill

    Poteto Mode

    poteto's agent style for concise, detailed responses, deliberate subagents, unslopped prose, simple code, and verified work. Use for poteto, /poteto-mode, or requests to work in this style.

    Also in 3 projects that use this

  • instructureSkill

    ketchup

    Rebuild context after /clear by analyzing uncommitted changes across Canvas LMS and all plugin repositories

    Also in 18 projects that use this

The file

Files
SKILL.md

Never Block on the Human

The human supervises asynchronously. Keep the work unblocked. Make a reasonable decision, proceed, and let the human course-correct after the fact. Queries, scripts, and charts are reversible and reviewable, so a wrong default usually costs less than a stalled session.

  • Proceed, then present. Write the analysis, prove it on synthetic data, and hand over one run request with the decisions behind it: the time window, the exclusions, and the metric definition. Do not ask "should I use 28 days?" Use 28 days, say so, and offer the alternative.
  • Make the pipeline self-healing where it is safe. When a check fails, log it and fix it in the next round.
  • Irreversible actions still need explicit confirmation. These are writes to a shared warehouse or production table, changes to a scheduled job, deletes, and sending results to people outside the session. Prefer a dry run or a compile step first.
  • Reversible actions proceed without blocking. These are files in the repo, notebooks, charts, scripts, and runs on synthetic data.
  • A run on real data is the human's step, and it is the one wait you accept. Make it cheap. Batch every check and every option the next decision needs into one run request, so the human runs once instead of answering a string of questions.
  • Product direction comes from the human. Which question matters, and which metric the business owns, is theirs to decide. Execution should not wait on it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.