[BUG] (lsp) skill name validation rejects valid colon-namespaced names

Resolved 💬 3 comments Opened Mar 10, 2026 by kellymears Closed May 4, 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?

Skills using colon namespaces (eg git:co) produce a VS Code hint diagnostic:

The skill name 'git:co' should match the folder name 'git-co'.

Colons can't appear in directory names, so the convention is to use hyphens in the folder name (git-co/SKILL.md) and colons in the name frontmatter (name: git:co).

What Should Happen?

Skills using colon namespaces should match against their directory name if the name replaces the : with a -.

The CLI already handles this mapping. There's a replace(/:/g, "-") call (internal function T1$) that resolves colon-namespaced skill names to their directories. The validation that generates this hint doesn't appear to have been updated to use it.

Error Messages/Logs

> The skill name 'git:co' should match the folder name 'git-co'.

Steps to Reproduce

  1. Create .claude/skills/git-co/SKILL.md with frontmatter name: git:co
  2. Open the file in VS Code with the Claude Code extension active
  3. Observe hint diagnostic: "The skill name 'git:co' should match the folder name 'git-co'."

Claude Model

Opus

Is this a regression?

I don't know

Last Working Version

_No response_

Claude Code Version

2.1.71 (Claude Code)

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Other

Additional Information

The skill works correctly at runtime. Invocation via /git:co resolves to the git-co directory as expected. The diagnostic is cosmetic but is confusing since it flags intentionally correct configuration.

View original on GitHub ↗

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