[BUG] Claude Code doesn't proactively use available skills when troubleshooting domain-specific problems

Resolved 💬 3 comments Opened Apr 5, 2026 by ft5-roshan Closed Apr 9, 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?

When debugging Zitadel API integration issues (wrong endpoint paths, wrong field names), Claude used WebFetch to look up documentation instead of
using the already-available zitadel skill that was specifically designed for Zitadel API work.

This resulted in 3+ rounds of trial-and-error:

  1. Used /v2/orgs/_search → 404
  2. Changed to /admin/v1/orgs/_search → worked, but then /admin/v1/orgs/_setup failed
  3. Used givenName/familyName instead of firstName/lastName → 500 error
  4. Fixed field names → finally worked

All of this could have been avoided by using the zitadel skill from the start.

What Should Happen?

Check the zitadel skills in the .claude/skills/zitadel prior to looking into web using Wedfetch

Expected behavior

When encountering domain-specific errors, Claude should:

  1. Check the available skills list for a matching skill
  2. Use the matching skill before falling back to generic tools like WebFetch
  3. This is especially important when skills explicitly describe the relevant domain (e.g., "Use when working with ZITADEL identity and access

management - APIs, authentication...")

Error Messages/Logs

Steps to Reproduce

  1. Ensure the zitadel skill is available in your Claude Code session (via skill pack or configuration)
  2. Have a project with Zitadel API integration code that uses incorrect API paths (e.g., /v2/orgs/_search instead of /admin/v1/orgs/_search)
  3. Share a Zitadel API error with Claude, e.g.:

Zitadel /v2/orgs/_search failed (404): {"code":5,"message":"Not Found"}

  1. Ask Claude to fix the issue
  2. Observe: Claude uses WebFetch to look up Zitadel docs or guesses at endpoint paths, instead of invoking the available zitadel skill which has

domain-specific knowledge of correct API endpoints and field names

  1. Expected: Claude should check available skills, find the zitadel skill matches the problem domain, and invoke it to get the correct answer

immediately

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.92

Platform

Other

Operating System

Windows

Terminal/Shell

PowerShell

Additional Information

_No response_

View original on GitHub ↗

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