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

78%

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

Fix and improve this skill with Tessl

tessl review fix ./.github/skills/content-redirect/SKILL.md

Quality

Content

75%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 clear, actionable instruction skill with a well-sequenced procedure and explicit verification steps. The main gaps are a missing validate-fix-retry feedback loop in the Verify step and an unspecified Grep command for the link-update step.

Suggestions

Turn step 6 (Verify) into an explicit feedback loop: 'If any check fails, fix the issue and re-run verification before proceeding.'

Give a concrete Grep example in step 5 (e.g. the search pattern and target file globs) so the link-update step is copy-paste ready.

Trim the opening 'You are a redirect specialist... Your job is to...' framing to a single concise purpose line.

Dimension	Reasoning	Score
Conciseness	Mostly lean with useful tables and a concrete path-transformation example, but the opening 'You are a redirect specialist... Your job is to...' role framing is mild padding that could be trimmed; not a 5 because of that minor over-explanation.	4 / 5
Actionability	Provides a copy-paste-ready JSON entry, a field table, and concrete path rules with worked examples (including index.md handling); falls short of 5 because step 5's link update leaves the Grep command unspecified and step 3 offers a choice rather than a definitive instruction.	4 / 5
Workflow Clarity	A clearly sequenced 6-step procedure with an explicit Verify checklist (valid JSON, no duplicate from paths, target file exists) and a chain-check step, so the destructive/batch cap does not apply; held at 4 rather than 5 because there is no explicit validate-fix-retry feedback loop when verification fails.	4 / 5
Progressive Disclosure	Well-organized self-contained body with clear sections (When to Use, Redirect Files, Entry Format, Procedure, Verify) and no nested references; at 4 rather than 5 because it slightly exceeds the under-50-line simple-skill threshold and the procedure detail is all inlined rather than split.	4 / 5
	Total	16 / 20 Passed

Description

82%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 that clearly states both capability and trigger conditions in third person with concrete trigger phrases. The only soft spot is specificity, where 'manage' is generic and the action list is not exhaustive.

Dimension	Reasoning	Score
Specificity	Names the domain (VS Code docs redirects) and two concrete actions ('Create and manage redirects'), but 'manage' is generic and the action set is not comprehensive, matching the anchor for 1-2 concrete actions.	3 / 5
Completeness	Explicitly answers 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.	5 / 5
Trigger Term Quality	Good natural-term coverage with 'moved, renamed, or deleted', 'moving docs pages, renaming files, restructuring content', and 'asks about redirects'; falls short of 5 only because there are no synonym/extension variants to round out the niche.	4 / 5
Distinctiveness Conflict Risk	Clear niche (VS Code documentation redirects) with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 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: 193d3e4

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