vscode-extension
Use when developing VS Code extensions including TextMate grammars, language configuration, and extension manifest
Third-Party Agent Skill: Review the code before installing. Agent skills execute in your AI assistant's environment and can access your files. Learn more about security
Installation for Agentic Skill
View all platforms →skilz install mcclowes/vague/vscode-extensionskilz install mcclowes/vague/vscode-extension --agent opencodeskilz install mcclowes/vague/vscode-extension --agent codexskilz install mcclowes/vague/vscode-extension --agent geminiFirst time? Install Skilz: pip install skilz
Works with 22+ AI coding assistants
Cursor, Aider, Copilot, Windsurf, Qwen, Kimi, and more...
Extract and copy to ~/.claude/skills/ then restart Claude Desktop
git clone https://github.com/mcclowes/vaguecp -r vague/.claude/skills/vscode-extension ~/.claude/skills/Need detailed installation help? Check our platform-specific guides:
Related Agentic Skills
command-name
by anthropics
This skill should be used when the user asks to "create a plugin", "scaffold a plugin", "understand plugin structure", "organize plugin components"...
mcp-integration
by anthropics
This skill should be used when the user asks to "add MCP server", "integrate MCP", "configure MCP in plugin", "use .mcp.json", "set up Model Contex...
rule-identifier
by anthropics
This skill should be used when the user asks to "create a hookify rule", "write a hook rule", "configure hookify", "add a hookify rule", or needs g...
bloblang-authoring
by redpanda-data
This skill should be used when users need to create or debug Bloblang transformation scripts. Trigger when users ask about transforming data, mappi...
Agentic Skill Details
- Repository
- vague
- Stars
- 1
- Type
- Non-Technical
- Meta-Domain
- productivity
- Primary Domain
- json
- Market Score
- 14
Agent Skill Grade
A Score: 92/100 Click to see breakdown
Score Breakdown
Areas to Improve
- Missing TOC in textmate.md
- Missing TOC in language-config.md
- Missing TOC in publishing.md
Recommendations
- Add trigger phrases to description for discoverability
- Add table of contents for files over 100 lines
Graded: 2026-01-24
Developer Feedback
I've been exploring how extension marketplaces handle the discovery problem, and your skill's approach to surfacing developer tools caught my attention—especially with that A-grade score backing it up. The way you've structured the guidance here suggests you've thought deeply about reducing friction for first-time extension developers.
Links:
The TL;DR
You're at 92/100, solid A territory. This is graded against Anthropic's best practices for skill design. Your strongest pillar is Utility (19/20)—the skill actually solves real problems with complete examples and templates. Weakest is Spec Compliance (12/15), mostly because you're only hitting 1-2 trigger phrases instead of a richer set.
What's Working Well
- Utility is chef's kiss – The grammar structure guidance, language configuration examples, and publishing checklist are genuinely useful. You've got concrete input/output pairs and templates that developers can actually use.
- Progressive Disclosure nailed – Three reference files (textmate.md, language-config.md, publishing.md) sit exactly one level deep from the main skill, and the token density is tight with zero fluff.
- Trigger terms are solid – Phrases like "TextMate grammars" and "language configuration" will surface this for the right use cases. The description connects clearly to VS Code extension development.
- Publishing checklist is structured – Numbered steps and validation checkpoints give developers a clear path to market.
The Big One: TOC Gap in Reference Files
Your three reference files (143, 157, and 151 lines) lack tables of contents. For a developer scanning textmate.md looking for "scope naming conventions," they're doing ctrl+F instead of jumping via TOC. This hurts discove...
Browse Category
More productivity Agentic SkillsReport Security Issue
Found a security vulnerability in this agent skill?
Report Security Issue
Thank you for helping keep SkillzWave secure. We'll review your report and take appropriate action.
Note: For critical security issues that require immediate attention, please also email security@skillzwave.ai directly.