metadata-updater

$npx mdskill add MicrosoftDocs/cloud-adoption-framework/metadata-updater

Updates YAML frontmatter metadata (ms.date, ms.service) after substantive content changes in Azure docs.

  • Helps maintain accurate metadata in Azure technical documentation after edits.
  • Integrates with YAML frontmatter blocks in documents, focusing on Azure service slugs.
  • Decides updates based on content changes and clear service renames, avoiding guesses.
  • Presents results by modifying only specified metadata fields, ignoring other content.

SKILL.md

.github/skills/metadata-updaterView on GitHub ↗
---
name: metadata-updater
description: Updates YAML frontmatter (ms.date, ms.service) after substantive content changes. Use when asked to update metadata or ms.date.
---

You are a metadata updater for Azure technical documentation. Update YAML frontmatter fields that should change when content has been substantively edited.

## Update rules

1. **ms.date** — Set to today's date in MM/DD/YYYY format. Only update if the document has other content changes applied.
2. **ms.service** — If the document's primary Azure service has been renamed or reorganized, update to the current service slug. Only change if clearly wrong (e.g., "azure-security-center" → "defender-for-cloud"). Don't guess.
3. **ms.subservice** — Same rule as ms.service.

## What NOT to change

- author, ms.author, ms.reviewer (people fields)
- ms.topic (article type classification)
- title, description, or any non-metadata content
- Any field you are unsure about

## What to ignore

All content outside the YAML frontmatter block (`---` to `---`). If the content does not contain a YAML frontmatter block, there is nothing to update.

More from MicrosoftDocs/cloud-adoption-framework

SkillDescription
acronym-checkEnsures abbreviations are expanded on first use per Microsoft style. Use when asked to check acronyms or abbreviations in documentation.
active-voiceRewrites passive voice to active/imperative and enforces second person. Use when asked to fix passive voice or improve writing directness.
api-consistencyEnsures Azure REST API and CLI consistency across a document. Use when asked to check API calls, CLI parameters, or REST consistency.
azure-validationValidates portal navigation paths, detects contradictions against Microsoft Learn documentation, and checks alignment with current Azure implementation standards. Use when asked to verify Azure portal instructions or validate content accuracy.
check-accessibilityChecks image accessibility compliance per Microsoft Learn standards. Use when asked to review images for alt text, lightbox paths, or complex image markup.
check-relevanceAssesses whether guidance is still relevant and framed for modern Azure approaches. Use when asked to check if content is still current or strategically relevant.
cloud-adoptionHow to adopt and integrate the Microsoft Azure cloud into your organization. Strategy, policies, organizational readiness, architecture, platform landing zone, governance, security, health, and operations.
code-expertIdentifies definite errors in code samples including syntax errors, missing imports, and deprecated APIs. Use when asked to review code samples for correctness.
code-freshnessReviews code samples for modern patterns, deprecated APIs, outdated dependencies, and alignment with current Microsoft best practices. Use when asked to update or modernize code samples.
code-verifierVerifies code samples against official Microsoft/Azure examples and syntax rules. Use when asked to verify code correctness or validate API usage.