The intent gate blocks file edits when no relevant skill exists, causing agents to get stuck

[skyz1]

I'm using TanStack Intent to load skills in Claude Code, and it's working well overall. One feature I really like is the hook that forces the agent to pull in the right skill before touching anything.

However, this has become an issue, when no relevant skill exists, as there's nothing for the agent to load to disable the hook. The agent then tends to get confused and the only solution is loading an irrelevant skill just to unblock itself.

Would it be possible to add an escape hatch for this? For example, a way for the agent to explicitly acknowledge "no relevant skill applies" and proceed?. That would keep the guardrail intact when a skill does exist, while avoiding the deadlock when one doesn't.

Has anyone else run into this, and if so, how have you worked around it?

[LadyBluenotes]

I'm hopefully going to be doing a release later this week that should solve some of that, but I'll make sure I test for this case before doing so. The idea will be to inject the catalog on session start (or after compaction, when a subagent is spawned etc) and pull skills that are relevant based on the descriptions, rather than being a blocking factor. It should make things a bit more context efficient, too.

I can notify you of the release, if that helps, so you can update the hook for it