菜单
Check and optimize MetaDescription frontmatter fields in VS Code documentation. Use when auditing, adding, or improving page descriptions for SEO and discoverability. Apply this when making content changes to markdown articles.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/microsoft/vscode-docs --skill frontmatter-description命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
| name | frontmatter-description |
| description | Check and optimize MetaDescription frontmatter fields in VS Code documentation. Use when auditing, adding, or improving page descriptions for SEO and discoverability. Apply this when making content changes to markdown articles. |
Check and optimize MetaDescription frontmatter fields in markdown documentation files. Produces actionable fixes for descriptions that violate the rules below.
MetaDescription.MetaDescription reflects the updated content.Every MetaDescription value must satisfy all of the following:
| Rule | Detail |
|---|---|
| Length | Maximum 160 characters. |
| Tone | Action-oriented, value-focused, factual, and impersonal. |
| Voice | No "you can", "users can", or "this page explains". |
| Sentences | Complete sentences, not fragments or labels. |
| No colons | Do not include : in the value — it breaks YAML parsing. |
| Uniqueness | Each description must be unique across the docs. |
Descriptions must also reflect the page's primary persona, reader intent, and article purpose. Establish that framing by following the content-framing guidance before suggesting or applying a description. If the existing page and writer's request support multiple materially different interpretations, ask the writer to confirm the framing before editing.
Determine which files to check:
docs/copilot/), find all .md files in that folder recursively.README.md files without --- delimiters).For each file, read enough of the page to identify its primary persona, reader intent, and article purpose. Then read the YAML frontmatter and check the MetaDescription field:
MetaDescription is absent.: character in the value.{{...}}), HTML tags, or Markdown formatting.Present results as a table:
| File | Issue | Current value | Suggested fix |
|------|-------|---------------|---------------|
MetaDescription and a rewritten suggestion that passes all rules.MetaDescription value in the YAML frontmatter.Good descriptions:
Get AI-powered inline suggestions from GitHub Copilot in VS Code, including ghost text completions and next edit suggestions.Configure and manage extensions in Visual Studio Code to customize your development environment.Debug Python applications in Visual Studio Code with breakpoints, variable inspection, and integrated terminal output.Bad descriptions and why:
| Description | Problem |
|---|---|
This page explains how to use Copilot. | Uses "this page explains". |
You can debug your code with VS Code. | Uses "you can". |
Copilot | Fragment, not a sentence. |
Learn how to enable the new feature in VS Code 1.90. | Uses "enable" and includes a version number. |
Set up debugging: configure launch.json for Python. | Contains a colon. |
Plan, write, and review VS Code blog posts. ALWAYS use this skill when the user asks to "write a blog post", "draft a blog", "add a blog post for", "review this blog post", or provides a feature/issue/PR to announce on the VS Code blog. For new posts, it proposes an outline and asks clarifying questions first, and does not edit any files until you approve the plan.
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.
Audit and update docs/copilot/ documentation to accurately reflect current VS Code AI capabilities. Use when: competitive analysis reveals gaps, product launches new features, docs use outdated framing, or keyword coverage needs strengthening for discoverability by users and AI agents. Produces a gap analysis plus targeted edits across affected files.
