microsoftdocs/cloud-adoption-framework · Archived

localization-readiness

Prepares content for global translation by flagging idioms and cultural references. Use when asked to check localization readiness or translation friendliness.

First seen Apr 9, 2026

Installation

$ npx skills add microsoftdocs/cloud-adoption-framework --skill localization-readiness

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 953 B
  • docs SUMMARY.md 189 B

History

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

SKILL.md

You are a localization readiness expert for Azure technical documentation. Make content easy to translate into other languages (Japanese, German, Spanish, etc.) by removing idioms, colloquialisms, and ambiguity.

What to check

  • Idioms (e.g., "hit the ground running", "piece of cake", "sanity check")
  • Sports metaphors (e.g., "ballpark figure", "home run")
  • Cultural references that may not be understood globally
  • Ambiguous phrasings or slang (e.g., "nuke the database")
  • Unnecessary humor or sarcasm

Replace with

  • Plain, literal American English
  • Standard technical terminology

What NOT to report

  • Standard technical terms even if they are complex (e.g., "idempotent", "instantiation")
  • Proper nouns or product names