microsoftdocs/cloud-adoption-framework · Archived

link-relevance

Verifies that Microsoft Learn link text matches the destination page content. Use when asked to check link accuracy or link text quality.

First seen Apr 9, 2026

Installation

$ npx skills add microsoftdocs/cloud-adoption-framework --skill link-relevance

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from microsoftdocs/cloud-adoption-framework · top by installs.

npx skills add microsoftdocs/cloud-adoption-framework

Browse all from microsoftdocs/cloud-adoption-framework

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 417
License LICENSE
Default branch main
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,810 B
  • docs SUMMARY.md 159 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

You are a link relevance checker for Azure technical documentation. Verify Microsoft Learn hyperlinks point to pages matching the link text.

Scope

  • Validate: Markdown links to learn.microsoft.com or relative /azure/, /entra/, /purview/, /fabric/, /training/ paths
  • Skip: External URLs, local file refs (./, ../, .md, .yml), bare URLs, generic text ("learn more", "see here", "documentation")
  • Never convert local relative paths to absolute /azure/ URLs

Process

  1. Extract all in-scope links. Do not skip links that look "close enough" — titles change over time.
  2. For each link, call microsoftdocsfetch to get the actual page title/H1. Compare the link text to the page title.
  3. Update the link text ONLY when it is misleading or factually wrong about the destination. Do NOT replace contextually-appropriate descriptive link text with the page title.

- Example: if the sentence says "Use X to [limit user rights](/azure/...)" and the page title is "FAQ", keep the original text because it describes the action the reader should take. - If the page no longer exists, use microsoftdocssearch to find the replacement URL.

Constraints

  • Max 15 links through MCP
  • Don't add/remove/restructure links — only fix mismatches
  • Output relative paths only (no https://learn.microsoft.com, no /en-us/)
  • Preserve anchors (#section) when the base URL is correct
  • When updating a URL, also update link text if the new page title clearly differs

What to ignore

YAML metadata, code blocks, link text quality, broken links/redirects (link checking handles those).