redirect-article

Deletes a markdown article and creates a redirect entry pointing to a different article. Use when consolidating articles, renaming or moving content, removing outdated documentation, or reorganizing the docs structure while preserving existing URLs.

Quality

73%

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/redirect-article/SKILL.md

Quality

Content

68%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.

The content is well-structured, actionable, and lean, with a real referenced script. Its main gap is the absence of an explicit validation/verification checkpoint for a destructive JSON-and-file-deletion workflow, which limits workflow clarity.

Suggestions

Add an explicit verification step after running the script (e.g. confirm the new entry appears in the redirection file and the JSON still parses) to create a validate-then-proceed feedback loop.

Make the internal-link update step concrete with an example search command (e.g. `grep -rn "old-article" --include=*.md --include=*.yml`) instead of only describing the search.

Consider moving the 17-row product-area reference table into a separate reference file and linking to it, keeping the SKILL.md body focused on the core procedure.

Dimension	Reasoning	Score
Conciseness	The body is efficient and does not explain concepts Claude already knows, though the repeated "ALWAYS use this script / DO NOT manually edit" emphasis and the large inline product-area table add minor redundant tokens.	4 / 5
Actionability	Provides an executable PowerShell example with all parameters and a parameter table, but the internal-link update step is given as a high-level search instruction rather than a concrete command.	4 / 5
Workflow Clarity	The delete / create-redirect / update-links sequence is clear, but this destructive operation has no explicit post-execution validation checkpoint (e.g. verify the entry was added and the JSON is valid), which caps workflow clarity at 3 per the destructive-operations guideline.	3 / 5
Progressive Disclosure	Well-organized sections with a one-level-deep, real bundle reference (./scripts/create-redirect-entry.ps1, verified present); the inline product-area lookup table is appropriate but borderline bulk that keeps it just short of fully optimal structure.	4 / 5
	Total	15 / 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.

The description is strong: it answers both what and when with concrete, natural trigger phrases and occupies a distinct niche. The main weakness is specificity, as it lists only two core actions without naming link updating or redirect-target selection.

Suggestions

Add a third concrete action to the what-clause (e.g. "and updates internal links to point to the new article") to lift specificity toward comprehensive coverage.

Include the word "redirect" or "redirects" in the trigger clause so users who say "set up a redirect" match naturally.

Optionally add the file extension / artifact term (e.g. ".openpublishing.redirection.json") to improve trigger-term coverage for users referencing the redirection files directly.

Dimension	Reasoning	Score
Specificity	Names the domain and two concrete actions ("Deletes a markdown article and creates a redirect entry pointing to a different article") but does not enumerate the broader set of operations such as link updating, so coverage is not comprehensive.	3 / 5
Completeness	Clearly states what the skill does (delete article + create redirect entry) and provides an explicit "Use when" clause with concrete trigger phrases, satisfying both what and when.	5 / 5
Trigger Term Quality	Natural trigger phrases are present ("consolidating articles, renaming or moving content, removing outdated documentation, or reorganizing the docs structure"), but a few common synonyms and the word "redirect" itself are absent from the trigger clause.	4 / 5
Distinctiveness Conflict Risk	The redirect-entry / URL-preservation niche is mostly distinct from general file skills, with only minor overlap risk against plain "delete file" skills.	4 / 5
	Total	16 / 20 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: dotnet/docs
Path: .github/skills/redirect-article/SKILL.md
Commit: 48719fe

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