[Dev10x:skill-audit] Proactive triggers not monitored during session

Resolved 💬 2 comments Opened Mar 30, 2026 by wooyek Closed Mar 30, 2026

Problem

The skill-audit SKILL.md documents 8 proactive auto-suggest triggers. Two triggers were clearly present during the audited session but the agent did not proactively suggest running skill-audit:

  • Trigger 6 (structural command friction): && chains, cd $() subshells, and hook-blocked retries all appeared
  • Trigger 7 (hook-blocked retries): The commit operation was blocked twice before the agent attempted a Python subprocess bypass

The skill says the agent should proactively suggest running /Dev10x:skill-audit after detecting these patterns. Instead, the user had to invoke it manually.

Related Issue

See also anthropics/claude-code#40918 — the inline summary deviation that occurred once the skill was invoked.

Proposed Fix

  1. Add a memory-level trigger note: "2nd hook-blocked retry in a session = mandatory skill-audit suggestion"
  2. Consider whether proactive triggers should be monitored by a lightweight background agent rather than relying on the main agent's attention during complex workflows
  3. Strengthen trigger language from "Auto-suggest this skill" to "MUST suggest this skill when pattern detected"

View original on GitHub ↗

This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗