frontmatter-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.

Quality

100%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

High

Do not use without reviewing

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a concise, well-organized instruction-only skill with concrete validation rules, a clear sequenced procedure including a fix-verification checkpoint, and useful good/bad examples. It assumes Claude's competence and stays within token budget.

Dimension	Reasoning	Score
Conciseness	The body is lean and table/list-driven, assumes Claude's competence without explaining what frontmatter or SEO are, and every line earns its place — matching the top anchor for token efficiency.	3 / 3
Actionability	Provides a concrete rules table, a 9-point validation checklist with specific failure conditions, a report table format, and worked good/bad examples — fully actionable instruction-only guidance with copy-ready templates.	3 / 3
Workflow Clarity	A clear four-step sequence (Identify → Extract and validate → Report → Apply fixes) with an explicit validation checkpoint ('Verify the fix passes all rules before applying') for the destructive edit step, matching the top anchor.	3 / 3
Progressive Disclosure	A self-contained skill under 50 body lines with no external references and no bundle files, organized into clear sections (When to Use, Rules, Procedure, Examples); per the rubric's simple-skills note this merits the top score.	3 / 3
	Total	12 / 12 Passed

Description

100%Weight 40%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that states concrete capabilities and provides explicit 'Use when' trigger guidance covering both what and when. It is specific, distinctive, and concise without fluff.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'Check and optimize MetaDescription frontmatter fields', 'auditing, adding, or improving page descriptions' — matching the anchor that lists several specific actions rather than vague language.	3 / 3
Completeness	Clearly answers both 'what' (check and optimize MetaDescription fields) and 'when' via explicit 'Use when auditing, adding, or improving...' and 'Apply this when making content changes' triggers, matching the top anchor.	3 / 3
Trigger Term Quality	Covers natural terms a user would say — 'auditing', 'page descriptions', 'SEO and discoverability', 'content changes to markdown articles' — giving good coverage of phrasings that would naturally surface this skill.	3 / 3
Distinctiveness Conflict Risk	Scoped to VS Code documentation MetaDescription frontmatter with distinct triggers, occupying a clear niche unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: microsoft/vscode-docs
Path: .github/skills/frontmatter-description/SKILL.md
Commit: 66977a9

Reviewed: 10 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

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.