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

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

86%Weight 40%Scale 1-5

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

A well-structured, highly actionable single-purpose skill: an unambiguous procedure with explicit validation checkpoints, concrete rules with exact thresholds, and illustrative examples. The only notable inefficiency is partial duplication between the Rules table and the validation checklist.

Dimension	Reasoning	Score
Conciseness	The body is efficient — rules as a compact table, an 11-item operational checklist, and short example lists — but the Rules table and Procedure step 2 restate several checks (length, voice, tone, colons, reusable variables), which is more than trivial duplication but stops short of padding or over-explanation.	4 / 5
Actionability	Guidance is fully executable for an instruction-only skill: 11 numbered checks with exact thresholds ("Maximum 160 characters"), exact phrases to flag ("you can", "users can", "this page explains"), a concrete reporting table format, explicit do/don't fix rules, and labeled good/bad examples with reasons.	5 / 5
Workflow Clarity	The 4-step procedure (identify files → extract and validate → report → apply fixes) is clearly sequenced with explicit checkpoints ("Verify the fix passes all rules and reflects the confirmed page framing before applying"; confirm framing with the writer when ambiguous), but there is no spelled-out fix-and-revalidate retry loop, so it falls short of the top anchor.	4 / 5
Progressive Disclosure	The skill is self-contained with no bundle files and no inlined content that belongs in separate files; sections are clearly organized (When to Use, Rules, Procedure, Examples) and both external links (content-framing guidance, data/variables) are one level deep and clearly signaled.	5 / 5
	Total	18 / 20 Passed

Description

78%Weight 40%Scale 1-5

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 description with an explicit what and when and good natural trigger coverage. Its main weakness is a thin set of core capability verbs and a broad catch-all trigger clause that slightly increases overlap risk with general content-editing skills.

Suggestions

Expand the what-clause with one or two more distinct concrete actions (e.g., "produces a findings table with rewritten suggestions") to move specificity beyond the current two core verbs.

Tighten the catch-all trigger "Apply this when making content changes to markdown articles" to reference MetaDescription/frontmatter specifically, reducing overlap with general docs-editing skills.

Add one or two natural synonym triggers such as "search snippet" or "meta description" to round out keyword coverage.

Dimension	Reasoning	Score
Specificity	The what-clause names the domain and two concrete actions ("Check and optimize MetaDescription frontmatter fields in VS Code documentation"), but the remaining verbs are trigger variations of the same narrow task rather than a list of several distinct capabilities.	3 / 5
Completeness	It clearly answers both questions: the what ("Check and optimize MetaDescription frontmatter fields in VS Code documentation") and an explicit, doubly-stated when ("Use when auditing, adding, or improving page descriptions for SEO and discoverability. Apply this when making content changes to markdown articles.").	5 / 5
Trigger Term Quality	Natural terms users would say are well covered ("auditing", "page descriptions", "SEO", "discoverability", "frontmatter", "markdown articles"), but common variations like "search snippet" or ".md" are missing, so it falls short of comprehensive synonym coverage.	4 / 5
Distinctiveness Conflict Risk	The MetaDescription/VS Code-docs niche is clear and distinct, but the broad clause "Apply this when making content changes to markdown articles" overlaps with any general docs-editing skill, creating minor conflict risk rather than minimal.	4 / 5
	Total	16 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 2 suspicious	Warning

	Total	15 / 16 Passed

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

Reviewed: 9 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.