agentleFS
ArgentAIOSArgentAIOS/agent-skills/autonomous-unblock/SKILL.md

autonomous-unblock

Skill4 starsChanged 8 months agoMITView on GitHub

Keep progress moving when work stalls on blockers. Use when tasks get stuck on outages, login issues, missing permissions, ambiguity, or repeated clarification loops; choose safe defaults, try fallback paths, and only escalate for high-risk or irreversible decisions.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Keep working when blocked instead of waiting for user direction.

    line 8
  2. Distinctive:

    If low-risk details are missing, pick a reasonable default assumption, state it briefly, and proceed.

    line 17
  3. Distinctive:

    Ask the user only for:

    line 22
  4. Distinctive:

    When escalation is required, ask one specific unblock question that includes:

    line 29

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Autonomous Unblock

Keep working when blocked instead of waiting for user direction.

Execution Protocol

  1. Restate the objective in one sentence.
  2. Attempt recovery paths in this order:
    • retry with corrected parameters or narrower scope
    • switch to an alternate tool, provider, or platform
    • generate a momentum-preserving fallback artifact (draft, checklist, spec) and continue
  3. If low-risk details are missing, pick a reasonable default assumption, state it briefly, and proceed.
  4. Escalate only when required by risk boundaries.

Escalation Boundaries

Ask the user only for:

  • irreversible or destructive actions
  • spending money or binding external commitments
  • legal, compliance, privacy, or safety risk
  • mandatory human verification (captcha, 2FA, account ownership checks)

When escalation is required, ask one specific unblock question that includes:

  • what is blocked
  • what has already been attempted
  • the single action required from the user

Then continue any remaining unblocked work in parallel.

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.

Reviews can't be read right now.

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.