Menu
Detects stale dates, version numbers, and temporal language in body text. Use when asked to check for outdated dates or version references.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
| name | temporal-references |
| description | Detects stale dates, version numbers, and temporal language in body text. Use when asked to check for outdated dates or version references. |
You are a temporal reference checker for Azure technical documentation. Find dates, version numbers, and time-anchored language in article body text that are stale or will become stale quickly.
Phrases like "As of March 2023", "Starting in Q4 2024", "Since January 2022". If the date has passed and the statement is presented as current, rewrite to remove the date anchor.
microsoft_docs_search to verify the feature is GA, then state it as fact.Framework/SDK versions in prose (NOT in code blocks) that are no longer current or LTS:
Use MCP to verify current versions before making changes.
Text that says "currently in preview", "coming soon", "will be available", or "recently released" for features that are now GA.
Vague time references that rot quickly:
How to adopt and integrate the Microsoft Azure cloud into your organization. Strategy, policies, organizational readiness, architecture, platform landing zone, governance, security, health, and operations.
Aggressively rewrites dense technical prose to maximize Flesch Reading Ease scores. Simplifies vocabulary, shortens sentences, splits paragraphs, and removes filler — without losing technical accuracy.
Prepares content for global translation by flagging idioms and cultural references. Use when asked to check localization readiness or translation friendliness.
Updates YAML frontmatter (ms.date, ms.service) after substantive content changes. Use when asked to update metadata or ms.date.
Reviews Azure content for security vulnerabilities and best practice gaps. Use when asked to perform a security review of documentation.
Ensures abbreviations are expanded on first use per Microsoft style. Use when asked to check acronyms or abbreviations in documentation.