Skill Crossroads

Check reference / Triggering & Discoverability

TRIGGER-05 Invocation flags are consistent

Triggering & Discoverability · 22% of the grade · deterministic · applies to skills · subagents

Deterministic — runs on every scan, no LLM or network needed.

Why it matters

`disable-model-invocation` and `user-invocable` decide who can fire the artifact — and YAML is unforgiving here. A quoted `"true"` is a string, not a boolean, so the flag silently does not do what you think. Worse, setting `user-invocable: false` AND `disable-model-invocation: true` together locks EVERYONE out: the artifact can never be invoked by the user or the model, yet still loads into every session as dead weight.

How to fix it

Use bare YAML booleans (`true`/`false`, never quoted strings) for both flags, and make sure at least one invocation path stays open. If nothing should ever invoke it, delete the artifact instead of shipping an uninvocable one.

Example

✗ flagged
---
user-invocable: false
disable-model-invocation: "true"   # a string AND, with the line above, uninvocable by anyone
---
✓ passes
---
name: deploy-prod
disable-model-invocation: true   # user-invocable stays true (the default)
---