agentleFS
Sign inStart free
wakqasahmedwakqasahmed/ai-engineering-workflow-skills/skills/engineering/hitl-blocker/SKILL.md

hitl-blocker

Skill2 starsChanged 2 months agoMITView on GitHub

Convert human-only blockers into visible GitHub issues. Use when work is blocked by missing credentials, secrets, DNS, billing, account permissions, approvals, or other user-held external state.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 4 are distinctive, and 1 is 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.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this before reporting a blocker back to the user.

    line 8
  2. Very specific:

    Create or reuse labels: HITL task and high priority when launch/work is blocked.

    line 13
  3. Distinctive:

    Create a GitHub issue in the most relevant repo.

    line 14
  4. Distinctive:

    Do not bury human-only blockers in chat only.

    line 31
  5. Distinctive:

    Do not keep retrying automation when credentials or account permissions are missing.

    line 32

≈ “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

HITL Blocker

Use this before reporting a blocker back to the user.

Workflow

  1. Identify the exact missing human-held item.
  2. Create or reuse labels: HITL task and high priority when launch/work is blocked.
  3. Create a GitHub issue in the most relevant repo.
  4. Include where to set or obtain the value.
  5. Include why it blocks the work.
  6. Include the verification command to rerun afterward.
  7. Link the failed run, PR, deployment, or command output when available.

Issue Must Include

  • Missing item
  • Owner/action needed
  • Where to enter it
  • Why it blocks launch/work
  • Verification after completion

Guardrails

  • Public issues, PRs, comments, and handovers must never include credential values or local credential-file paths. Use Credential details: [redacted].
  • Do not bury human-only blockers in chat only.
  • Do not keep retrying automation when credentials or account permissions are missing.

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.

Check your setup, free