What problem does it solve?
Agents running inside gh-aw workflows with narrow tools: allowlists can burn through a hard, non-renewable denial budget (commonly 3 denied tool calls) by retrying disallowed commands, causing the harness to abort the entire session with guard.tool_denials_exceeded.
Core Features & Use Cases
- Allowlist-first execution: Read the workflow's declared
tools: block (bash list, MCP toolsets, edit permissions) before issuing any shell, file, or MCP command.
- Denial triage procedure: On the first denial, pivot to an allowed capability substitute instead of retrying variants of the same disallowed command.
- Accurate gap reporting: Avoid misreporting intentional least-privilege restrictions as credential or permission bugs, and cite the exact denied commands when reporting a genuine missing capability.
- Use Case: An agent in a gh-aw workflow with a short
bash: allowlist gets "permission denied" on git status; instead of probing variants, it switches to an allowed git diff command, completes the task, and notes the constraint.
Quick Start
When a tool call is denied inside a gh-aw workflow, apply this skill to check the declared tools allowlist, switch to an allowed capability, and finish the task without exhausting the denial budget.