Pathruleこのページは英語でのみご覧いただけます。
Why Claude Code Skills Do Not Activate
A skill that the model never invokes is the same shape of failure as a CLAUDE.md it never follows.
Activation is delivery plus authority, not just presence on disk.
結論
Check whether Claude sees the skill, whether its description names the task and whether invocation is allowed. A discovered skill still needs to be selected. Use /skill-name for a direct test, and inspect frontmatter if the description is missing.
この記事の内容
- Check the path, metadata and invocation controls before rewriting the procedure.
- Pathrule offers skills by name and loads the procedure when requested or explicitly invoked.
Check discovery before activation
- Confirm the skill appears when you ask which skills are available.
- Check its SKILL.md path and YAML metadata.
- Use a description that names the task teammates actually ask for.
- Check whether automatic or user invocation is disabled.
- Try /skill-name directly in Claude Code, or ::skill-name for a Pathrule workspace skill.
A file, an available skill and an invoked skill are different
A SKILL.md on disk is not proof that the current session discovered it. Ask which skills are available, then test the command directly. A skill that is available but unused has a selection problem rather than a missing-file problem.
Check the current loader
Current Claude Code can pick up SKILL.md changes during a session. A newly created top-level skills directory may need /reload-skills. Plugin integration changes have a separate reload path. See the official skill lifecycle documentation.
Give the description a concrete trigger
Name the job the skill does and the request that should select it. “Replay a Stripe webhook locally” is easier to choose than “Stripe helpers”.
Check invocation controls too: disable-model-invocation prevents automatic use, while user-invocable controls direct invocation.
Inspect metadata separately from the body
Malformed YAML can leave a skill with a body but no useful description. Test direct invocation and inspect debug output before assuming the file was skipped. The official troubleshooting guide explains this distinction.
How Pathrule delivers a team procedure
Pathrule stores the skill body and frontmatter at a workspace path and materializes skills in supported client directories. Context delivery normally offers skills by name; it does not push every procedure into every task.
Use ::skill-name to explicitly invoke a workspace skill. The supported prompt hook or a context request resolves that name and supplies its body for the task. See Writing skills.