Hitl blocker
Skill wakqasahmed/ai-engineering-workflow-skills/skills/engineering/hitl-blocker
Canonical AI engineering workflow skills, aggregated by wakqasahmed/skills
npx -y skills add wakqasahmed/ai-engineering-workflow-skills --skill hitl-blockerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
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.
SKILL.md
1.1 KB, as published. Nobody here has run it
HITL Blocker
Use this before reporting a blocker back to the user.
Workflow
- Identify the exact missing human-held item.
- Create or reuse labels:
HITL taskandhigh prioritywhen launch/work is blocked. - Create a GitHub issue in the most relevant repo.
- Include where to set or obtain the value.
- Include why it blocks the work.
- Include the verification command to rerun afterward.
- 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.