Skip to content

Skill definition files are inconsistent with the way copilot/vscode does things. #294606

@BryanDollery

Description

@BryanDollery
No, that tool isn't helpful

Does this issue occur when all extensions are disabled?: Yes, it's not an extension issue

  • VS Code Version: insiders, latest
  • OS Version: osx latest

The problem is that the current conventions for skill definitions are horrible and badly conceived. I get that this is basically a feature copied from claude code, but it's really shitty to give every file the same name, and its worse to make them all upper case. And, create a folder to hold a single file - why?

I'd like to see skills follow the conventions already set by vscode for agents. Have the name include ".skill.md" to make it a skill and put it in the .github/skills folder. Having two different approaches to defining instructions is ugly and unnecessary. Please fix it. You can leave in the current format for people working in claude code as well as vscode, but we don't need to maintain their crappy standards here - this is for professionals, not script kiddy vibe-coders. We need consistency and, believe it or not, some of us don't use claude code because we think it's shit and we actually prefer vscode...

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions