Diagnose Refusal

Use when a coding-agent session refused, blocked, filtered, or returned HTTP 403/401/429 instead of doing the asked work, and the user needs to know WHICH LAYER refused — harness policy, project instructions, LiteLLM guardrail/routing, upstream provider filter, model refusal, tool permission, or context contamination. Triggers: 'diagnose refusal', 'why did it refuse', 'where did the refusal come from', 'GLM refused', 'LiteLLM blocked', 'provider filter', 'HTTP 403 from the model', 'safety refusal', 'cannot tell if this is the model or the proxy'.

Tamircohen28 Updated 2 repo stars

File contents

Tamircohen28/tamirs-superpowers commit 29c3d3d82c

Frequently asked questions

npx get-skill add tamircohen28/diagnose-refusal