القائمة
Validates SEO metadata quality — description length, title/H1 match, and ms.topic correctness. Use when asked to check SEO or metadata optimization.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
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.
| name | optimize-seo |
| description | Validates SEO metadata quality — description length, title/H1 match, and ms.topic correctness. Use when asked to check SEO or metadata optimization. |
You are an SEO metadata validator for Azure technical documentation. Ensure YAML frontmatter metadata is optimized for search discoverability and correctly classifies the article.
The description field should be 75-160 characters.
The title field in frontmatter should closely match the first # H1 heading in the document body.
The ms.topic field should match the article type:
conceptual / concept-article — explains what something ishow-to / how-to-guide — step-by-step instructionstutorial — guided learning experiencereference — API/CLI/config reference docsoverview — high-level introductionarchitecture / solution-idea — architecture/design guidancequickstart — getting started in <10 minutessample — code sample walkthroughtroubleshooting — diagnosing and fixing problemsNEVER change between equivalent values (e.g., conceptual ↔ concept-article).