Plan and write VS Code documentation for a new or updated feature. ALWAYS use this skill when the user asks to "document", "add docs for", "write docs for", or "update the docs for" a feature, or provides a GitHub issue/PR link to document — even if the change seems small. Proposes a documentation plan and asks clarifying questions first — it does not edit any files until you approve the plan.
75
95%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
View guide
Low
Low-risk findings worth noting
Low
Low-risk findings.
2 low severity findings. Worth noting, but not necessarily harmful.
The skill exposes the agent to untrusted, user-generated content from public third-party sources, creating a risk of indirect prompt injection. This includes browsing arbitrary URLs, reading social media posts or forum comments, and analyzing content from unknown websites.
This skill’s Phase 1 workflow explicitly instructs the agent to inspect public/outside GitHub repositories (e.g., `microsoft/vscode` / `microsoft/vscode-copilot-chat`) via the `gh` CLI to understand a feature, which would make outsider-authored prose from those repos readable to the LLM at runtime.
The skill fetches instructions or code from an external URL at runtime, and the fetched content directly controls the agent’s prompts or executes code. This dynamic dependency allows the external source to modify the agent’s behavior without any changes to the skill itself.
The skill instructs using the gh CLI to inspect source code at runtime in the repositories microsoft/vscode and microsoft/vscode-copilot-chat, meaning remote repo content is fetched and used to inform the agent's prompts and documentation output (microsoft/vscode, microsoft/vscode-copilot-chat).
66977a9
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.