[BUG] Skills which manually invoke do not automatically invoke

Status Fixed / completed
Reported on v2.1.7
Maintainer reply None cached
Activity 5 comments · opened Jan 21, 2026 · closed Feb 3, 2026

Preflight Checklist

  • [x] I have searched existing issues and this hasn't been reported yet
  • [x] This is a single bug report (please file separate reports for different bugs)
  • [x] I am using the latest version of Claude Code

What's Wrong?

I created a series of Claude skills, but one of them—an orchestration skill called "jira-router"—no longer shows up when I ask Claude to list available skills. All my other skills (12 total) appear normally, and jira-router used to work without issues.

Normally, I could say something like "I need to refine OA‑12771", and jira-router would automatically run: it would query JIRA, determine whether the item was a bug, epic, story, etc., and then route the request to the correct skill. That automatic invocation has stopped working. However, manual invocation (e.g., typing /jira-router) still works perfectly, which proves the skill format and content are valid.

Core Issue: This appears to be persistent skill registry corruption tied specifically to the jira-router name/directory. The corruption has survived:

  • Multiple Claude Code version upgrades (tested 2.1.7, 2.1.12, 2.1.14, 2.1.15)
  • Directory rename jira-router -> `jira-routing'
  • Complete removal and reinstallation
  • Metadata updates (SKILL.md frontmatter, .dependency-manifest.json, settings.local.json permissions)

Proof it's name-specific corruption:

  • Created a brand new skill called jira-router-v2 with identical SKILL.md content → FAILED
  • Created a brand new skill called issue-orchestrator with identical SKILL.md content → worked immediately
  • This proves the skill content/format is valid and the problem is tied to the corrupted directory/name

Proof it's system-specific:

  • Same exact jira-router skill files work perfectly on my laptop (Claude Code 2.1.15)
  • Only broken on my desktop system
  • This proves it's local state corruption, not a configuration file issue

To troubleshoot, I also tested:

  • Running from my user skill path (C:\Users\[username]\.claude\skills\)
  • Running from project skill path (.claude\skills\)
  • Neither location fixed the issue

Suspected trigger: This problem started after I tested distributing skills to others using custom skill-packager/skill-installer tools. I installed skills to the user path (C:\Users\[username]\.claude\skills\) for testing, then deleted that entire .claude directory (including skills, hooks, settings.json, settings.local.json). It's possible that operation left behind hidden state that permanently corrupted the jira-router skill registry entry on this system.

Attachments:

  • claude-code-skill-loading-bug-report.md - Complete technical investigation with evidence
  • jira-router-setup-1.9.1-sanitized.zip - The packaged skill for reproduction

jira-router-setup-1.9.1-sanitized.zip
claude-code-skill-loading-bug-report.md

What Should Happen?

When I launch claude it should automatically invoke the jira-router skill when prompts like "i need to refine a JIRA ticket" or "I want to add criteria to an epic" are sent.

Error Messages/Logs

Steps to Reproduce

I am unsure how to replicate, as it seems to be environmental, but Claude and I can't figure out what environmental information would be blocking this skill from loading properly.

Claude Model

Sonnet (default)

Is this a regression?

Yes, this worked in a previous version

Last Working Version

2.1.15

Claude Code Version

2.1.15

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

5 Comments

github-actions[bot] · 8 months ago

Found 3 possible duplicate issues:

  1. https://github.com/anthropics/claude-code/issues/18440
  2. https://github.com/anthropics/claude-code/issues/10768
  3. https://github.com/anthropics/claude-code/issues/9716

This issue will be automatically closed as a duplicate in 3 days.

  • If your issue is a duplicate, please close it and 👍 the existing issue instead
  • To prevent auto-closure, add a comment or 👎 this comment

🤖 Generated with Claude Code

grendal1974 · 8 months ago

This is not a duplicate. I mistyped the bug title originally and said it was a hook that wasn't invoking when it was a skill. I have since updated this. I also updated the what's wrong to make it more clear. I have attached a .md file of the analysis surrounding the 3 possible duplicate issues and why they are not duplicates.

issue-19913-not-duplicate-analysis.md

grendal1974 · 8 months ago

Additional Context - Possible Trigger Sequence:

I believe this corruption occurred when I had the same skill (jira-router) installed in BOTH user-level
and project-level paths simultaneously, then deleted the user-level installation.

Sequence:

  1. Tested skill distribution by installing to C:\Users\[username]\.claude\skills\ - all skills worked

including jira-router

  1. Launched Claude from that user path location - jira-router auto-invoked correctly
  2. Returned to project path C:\Workspace\git\primary - copied skills back to project .claude\skills\
  3. Now had TWO copies of jira-router (user-level + project-level)
  4. Worked on other skills, launched Claude from both locations during this period
  5. Manually deleted entire user-level .claude directory (skills, hooks, settings.json,

settings.local.json)

  1. jira-router stopped loading after this cleanup

Hypothesis: Claude Code may have created internal tracking entries for BOTH skill locations
(user-level and project-level). When I deleted the user-level copy, it may have left orphaned references
in Claude's skill discovery system
that corrupted the project-level skill entry.

Why this theory fits the symptoms:

  • Manual invocation works (/jira-router) because it bypasses skill discovery and loads directly from the

file

  • Skill doesn't appear in available skills list because the discovery system has conflicting/corrupted

state

  • Creating a new skill with different name (issue-orchestrator) works because it has no dual-path history
  • System-specific issue because only my desktop went through this dual-path installation sequence
grendal1974 · 8 months ago

The jira-router skill (version 1.9.1 attached to this issue) contains invalid YAML syntax in the frontmatter that causes the skill discovery system to silently fail.

github-issue-19913-update.md

github-actions[bot] · 8 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.