content-redirect

Create and manage redirects in VS Code documentation when pages are moved, renamed, or deleted. Use when moving docs pages, renaming files, restructuring content, or when the user asks about redirects.

Quality

88%

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 lean, highly actionable skill body: concrete JSON format specification, a well-sequenced procedure with an explicit verification step, and clean section organization with no padding or misplaced content. The only gaps are slight redundancy with the frontmatter description and the absence of an explicit error-recovery loop after the verification checks.

Dimension	Reasoning	Score
Conciseness	The body is efficient — compact tables, a tight six-step procedure, and no explanations of concepts Claude already knows. It falls short of anchor 5 because the intro sentence and the "When to Use" section substantially restate the frontmatter description, and details like "Keep the array sorted or append at the end — either is acceptable" could be trimmed.	4 / 5
Actionability	Guidance is fully executable for an instruction-only skill: a concrete JSON entry example, a field-format table with rules, a worked path-transformation example (docs/copilot/overview.md → "/docs/copilot/overview"), and specific tool guidance (Grep across markdown and toc.json files). Per the scoring notes, absence of code is not penalized when guidance is this actionable.	5 / 5
Workflow Clarity	Six clearly numbered steps end with an explicit verification step (valid JSON, no duplicate from paths, target file exists), matching the anchor for a clear sequence with most checkpoints present. It misses anchor 5 because there is no error-recovery feedback loop describing what to do when a verification check fails.	4 / 5
Progressive Disclosure	No bundle files exist, and the body is a compact, well-sectioned, self-contained single-purpose procedure with no content that belongs in a separate file — matching the anchor 5 case for a small skill needing no external references. All sections are clearly headed and easy to navigate.	5 / 5
	Total	18 / 20 Passed

Description

87%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: third-person voice, concrete domain (VS Code docs redirects), an explicit "Use when..." clause with natural trigger phrases, and a clear niche that avoids conflicts with other skills. Minor room to add trigger synonyms and split the generic "manage" into more specific verbs.

Dimension	Reasoning	Score
Specificity	"Create and manage redirects in VS Code documentation when pages are moved, renamed, or deleted" names concrete actions in a specific domain with triggering events, matching the anchor for several specific actions with minor gaps. It falls short of 5 because only two verbs are given and "manage" is generic; it exceeds 3 because coverage goes beyond 1-2 bare actions.	4 / 5
Completeness	It explicitly answers both what ("Create and manage redirects in VS Code documentation when pages are moved, renamed, or deleted") and when ("Use when moving docs pages, renaming files, restructuring content, or when the user asks about redirects") with concrete trigger phrases, exactly matching the anchor 5 example structure.	5 / 5
Trigger Term Quality	"moving docs pages, renaming files, restructuring content, asks about redirects" are natural phrases a user would say, giving good keyword coverage. Missing common variations like "URL", "deleting pages", or file extensions keeps it below the comprehensive anchor 5.	4 / 5
Distinctiveness Conflict Risk	"VS Code documentation" plus "redirects" defines a clear niche with distinct triggers and minimal conflict risk with other skills. It is far more specific than the anchor 4 example and shows no overlap concerns.	5 / 5
	Total	18 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: microsoft/vscode-docs
Path: .github/skills/content-redirect/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.