Expected: Invoking the skill (via `/estack-pdf-to-md` or the Skill tool) runs the SKILL.md startup check block (the ```! fenced bash block that checks `PULSE_API_KEY`) automatically and reports [OK]/[MISSING], per the skill's documented flow.
Actual: In auto mode, Claude Code's permission classifier blocked that exact bash command with:
Permission for this action was denied by the Claude Code auto mode classifier. Reason: Blocked by classifier.
This happened twice in a row — once when the skill auto-triggered mid-conversation, and again when the user explicitly ran `/estack-pdf-to-md`. Both times the Skill invocation failed outright rather than falling back or proceeding. The only workaround was manually copy-pasting the same script into the Bash tool directly, which worked fine and reported the key was found.
Context: Windows 11, PowerShell/Git Bash environment, Claude Code auto mode active. `PULSE_API_KEY` was actually already configured (found via Windows user env var), so this isn't a missing-key issue — it's the startup check's shell invocation itself getting rejected before it can even report status.
Possible causes to look at:
- The ```! auto-exec fence syntax may be getting flagged as suspicious by the auto-mode classifier (e.g. due to `powershell.exe -NoProfile -Command` invocation, or the multi-line `grep`/`cut`/`tr`/`xargs` pipeline).
- Consider whether the startup check needs to be less complex, or whether SKILL.md should document a manual fallback command explicitly for when the auto-exec block is blocked.
🤖 Generated with Claude Code
Expected: Invoking the skill (via `/estack-pdf-to-md` or the Skill tool) runs the SKILL.md startup check block (the ```! fenced bash block that checks `PULSE_API_KEY`) automatically and reports [OK]/[MISSING], per the skill's documented flow.
Actual: In auto mode, Claude Code's permission classifier blocked that exact bash command with:
This happened twice in a row — once when the skill auto-triggered mid-conversation, and again when the user explicitly ran `/estack-pdf-to-md`. Both times the Skill invocation failed outright rather than falling back or proceeding. The only workaround was manually copy-pasting the same script into the Bash tool directly, which worked fine and reported the key was found.
Context: Windows 11, PowerShell/Git Bash environment, Claude Code auto mode active. `PULSE_API_KEY` was actually already configured (found via Windows user env var), so this isn't a missing-key issue — it's the startup check's shell invocation itself getting rejected before it can even report status.
Possible causes to look at:
🤖 Generated with Claude Code