Official agent skill

Docs Impact Localizer

A skill your agent uses to translate a classifier's in-place verdict into a precise, page-by-page work plan for the docs-sync panel.

OfficialMITAuto-check passed

Install Docs Impact Localizer

skills CLI

$ npx skills add microsoft/apm --skill docs-impact-localizer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install microsoft/apm docs-impact-localizer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/microsoft/apm.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.apm/skills/docs-impact-localizer .claude/skills/docs-impact-localizer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "docs-impact-localizer" agent skill from https://github.com/microsoft/apm/tree/main/.apm/skills/docs-impact-localizer into .claude/skills/docs-impact-localizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-impact-localizer", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/microsoft/apm/tree/main/.apm/skills/docs-impact-localizer

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add microsoft/apm --skill docs-impact-localizer -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install microsoft/apm docs-impact-localizer --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/apm.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.apm/skills/docs-impact-localizer .agents/skills/docs-impact-localizer && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "docs-impact-localizer" agent skill from https://github.com/microsoft/apm/tree/main/.apm/skills/docs-impact-localizer into .agents/skills/docs-impact-localizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-impact-localizer", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add microsoft/apm --skill docs-impact-localizer -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install microsoft/apm docs-impact-localizer --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/apm.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.apm/skills/docs-impact-localizer .cursor/skills/docs-impact-localizer && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "docs-impact-localizer" agent skill from https://github.com/microsoft/apm/tree/main/.apm/skills/docs-impact-localizer into .cursor/skills/docs-impact-localizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-impact-localizer", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/microsoft/apm.git --path .apm/skills/docs-impact-localizer

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add microsoft/apm --skill docs-impact-localizer -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install microsoft/apm docs-impact-localizer --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/apm.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.apm/skills/docs-impact-localizer .gemini/skills/docs-impact-localizer && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "docs-impact-localizer" agent skill from https://github.com/microsoft/apm/tree/main/.apm/skills/docs-impact-localizer into .gemini/skills/docs-impact-localizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-impact-localizer", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install microsoft/apm docs-impact-localizer

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add microsoft/apm --skill docs-impact-localizer -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/apm.git skills-src && mkdir -p .github/skills && cp -r skills-src/.apm/skills/docs-impact-localizer .github/skills/docs-impact-localizer && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "docs-impact-localizer" agent skill from https://github.com/microsoft/apm/tree/main/.apm/skills/docs-impact-localizer into .github/skills/docs-impact-localizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-impact-localizer", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add microsoft/apm --skill docs-impact-localizer -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install microsoft/apm docs-impact-localizer --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/microsoft/apm.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.apm/skills/docs-impact-localizer .opencode/skills/docs-impact-localizer && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "docs-impact-localizer" agent skill from https://github.com/microsoft/apm/tree/main/.apm/skills/docs-impact-localizer into .opencode/skills/docs-impact-localizer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-impact-localizer", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: docs-impact-localizer
GitHub stars: 4k
Token cost: ~1.1k tokens
SKILL.md length: 380 words
Files: 1
Skills in repo: 27
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses to translate a classifier's in-place verdict into a precise, page-by-page work plan for the docs-sync panel.

Works in 4 steps: load page contents → narrow scope inside each page → detect cross-page conflicts → …
Translate a classifiers in-place verdict into a precise
SKILL.md covers When to invoke, Inputs, Step 1: load page contents and Step 2: narrow scope inside…, plus 4 more sections
Calls gh

What it does

Docs Impact Localizer is an agent skill from microsoft/apm, published by the product's own GitHub organization. Use this skill to translate a classifier's in-place verdict into a precise, page-by-page work plan for the docs-sync panel. Activate after docs-impact-classifier returns verdict inplace; reads the candidate page list, fetches the actual page contents, narrows scope to specific sections within each page, and emits the per-page task brief the panel fans out against.

Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Agent Package Manager. The licence is MIT.

When your agent uses it

Translate a classifiers in-place verdict into a precise
Page-by-page work plan for the docs-sync panel

Example prompts

“/docs-impact-localizer”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

load page contents
narrow scope inside each page
detect cross-page conflicts
emit the per-page task brief

What it can do on your machine

Read from SKILL.md and the folder at commit 280b8a7. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
- gh
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use gh, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Docs Impact Localizer loads about 1.1k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 380 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~97
When it runs · the whole SKILL.md, loaded when a task matches: ~1.1k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from microsoft/apm at commit 280b8a7, republished under its MIT licence (© microsoft). 380 words, ~1,065 tokens.

Download SKILL.mdSave it as .claude/skills/docs-impact-localizer/SKILL.md (or your agent's skills folder).

name: docs-impact-localizer
description: Use this skill to translate a classifier's in-place verdict into a precise, page-by-page work plan for the docs-sync panel. Activate after docs-impact-classifier returns verdict in_place; reads the candidate page list, fetches the actual page contents, narrows scope to specific sections within each page, and emits the per-page task brief the panel fans out against.

docs-impact-localizer

Single responsibility: given a list of candidate pages from the classifier, produce a per-page task brief the docs-sync panel can fan out against.

You are NOT the verdict-maker (classifier owns that). You are NOT the writer (doc-writer owns that). You are the work planner.

When to invoke

The docs-sync orchestrator invokes you ONLY when the classifier returned verdict: in_place. For no_change you don't run. For structural the architect runs first; you may run after, scoped to existing pages that need amendment.

Inputs

scope_pages[] from the classifier
The PR diff (gh pr diff $PR)
.apm/docs-index.yml (per-page metadata)
Optional: the structural architect's TOC delta (if you run after the architect on a structural verdict)

Step 1: load page contents

For each path in scope_pages[], read the file. Pages are typically 3-10 KB; total budget for this step is bounded by the candidate count (the classifier should have kept it to <= 6).

Step 2: narrow scope inside each page

For each page, identify the SPECIFIC section(s) that need to change:

Read the page's H2/H3 structure
For each diff symbol from the classifier output, find the section most directly documenting it
Capture line ranges: lines 120-145 not the whole page

The output is a sections_to_edit[] per page, where each entry is:

yaml

page: docs/src/content/docs/consumer/install.md
sections_to_edit:
  - section: "## From Git"
    line_range: [120, 145]
    diff_symbol: "--no-cache flag"
    edit_kind: add | modify | remove
    rationale: "the new --no-cache flag is documented nowhere; section already lists other flags so this is the natural home"

Show full SKILL.md (172 more words)Show less

Step 3: detect cross-page conflicts

If two pages document the same symbol and the diff changes the symbol's behaviour, BOTH pages need an edit AND they must stay consistent. Flag this in the brief so the CDO synthesizer knows to cross-check coherence between the two redrafts:

yaml

cross_page_constraint:
  pages: [path1, path2]
  shared_symbol: "apm install --target"
  consistency_required: "both pages must reflect the same default value"

Step 4: emit the per-page task brief

Return JSON with this shape (one entry per page in scope_pages[]):

json

{
  "tasks": [
    {
      "page": "docs/src/content/docs/consumer/install.md",
      "persona_owner": "consumer",
      "promise": 1,
      "sections_to_edit": [
        {
          "section": "## From Git",
          "line_range": [120, 145],
          "diff_symbol": "--no-cache flag",
          "edit_kind": "add",
          "rationale": "..."
        }
      ],
      "verify_claims": [
        {"claim": "the flag is named --no-cache", "verify_with": "apm install --help"},
        {"claim": "the flag is documented in click.option decorator", "verify_with": "grep -n no-cache src/apm_cli/commands/install.py"}
      ]
    }
  ],
  "cross_page_constraints": [
    {"pages": [...], "shared_symbol": "...", "consistency_required": "..."}
  ],
  "estimated_panel_calls": 8
}

The verify_claims[] per page is consumed by the python-architect panelist -- it tells the verifier WHICH claims need a S7 tool-call check (run apm install --help, grep the source) rather than prose-trusting.

Output contract

Return a SINGLE JSON document matching the schema in Step 4 as the final message of your task. No prose around the JSON.

Anti-patterns

Selecting whole pages when one section suffices (inflates context per panelist).
Skipping verify_claims[] -- that's the S7 tool-bridge hook; the verifier needs it.
Inventing pages not in scope_pages[] -- that's the classifier's job, not yours. If you think the classifier missed a page, return an extra field localizer_concern instead of expanding scope unilaterally.

Files

Just SKILL.md in .apm/skills/docs-impact-localizer of microsoft/apm.

Open the folder on GitHubat commit 280b8a7

Compare with similar skills

Docs Impact Localizer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Docs Impact Localizer compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Docs Impact Localizer this skillmicrosoft/apm	4k	—	~1.1k	Automated safety check: Pass	MIT	today
Translating LocalesTriliumNext/Trilium	38k	—	~3k	Automated safety check: Pass	AGPL-3.0	today
Write Locale Translationsvideojs/video.js	40k	—	~723	Automated safety check: Pass	Custom licence	today
Translation Diff TranslateDevolutions/UniGetUI	26k	—	~934	Automated safety check: Pass	MIT	today
Plane UI Translationmakeplane/plane	60k	—	~16k	Automated safety check: Pass	AGPL-3.0	yesterday
Translatetagspaces/tagspaces	5.3k	—	~2.2k	Automated safety check: Pass	AGPL-3.0	today

Similar skills

Translating Locales
TriliumNext/Trilium
A skill your agent uses when filling in or improving a lagging UI translation locale in Trilium (e.g.
38k GitHub stars~3k tokensUpdated today
Writing & ContentAuto-check passed
Write Locale Translations
videojs/video.js
Translate or audit the values in a Video.js locale pack. An agent skill from videojs/video.js.
40k GitHub stars~723 tokensUpdated today
Writing & ContentAuto-check passed
Translation Diff Translate
Devolutions/UniGetUI
Translates a sparse UniGetUI JSON language patch, writes completed entries into the working copy, preserves placeholders and terminology, and prepares the patch for merge-back.
26k GitHub stars~934 tokensUpdated today
Writing & ContentAuto-check passed
Plane UI Translation
makeplane/plane
Sets the rules for translating and updating Plane's UI strings across locales: do-not-translate terms, plural forms, placeholders and AI translation review.
60k GitHub stars~16k tokensUpdated yesterday
Writing & ContentAuto-check passed
Translate
tagspaces/tagspaces
Translate new or untranslated i18n strings from the English locale files (core.json + peri.json) into all other locales, maintaining consistency with each language's existing translations.
5.3k GitHub stars~2.2k tokensUpdated today
Writing & ContentAuto-check passed
Translation
doxygen/doxygen
Keeps all Doxygen and Doxywizard translations up to date across three mechanisms: translator C++ classes (src/translatorxx.h), Qt .ts locale files for the Doxywizard GUI (addon/doxywizard/i18n/)…
6.6k GitHub stars~5.2k tokensUpdated 6 days ago
Writing & ContentAuto-check passed

Questions about Docs Impact Localizer

What does Docs Impact Localizer do?

A skill your agent uses to translate a classifier's in-place verdict into a precise, page-by-page work plan for the docs-sync panel. Docs Impact Localizer is an agent skill from microsoft/apm, published by the product's own GitHub organization. Use this skill to translate a classifier's in-place verdict into a precise, page-by-page work plan for the docs-sync panel.

When should I use Docs Impact Localizer?

Docs Impact Localizer fits situations like: translate a classifiers in-place verdict into a precise; page-by-page work plan for the docs-sync panel.

How do I install Docs Impact Localizer in Claude Code?

Run `npx skills add microsoft/apm --skill docs-impact-localizer -a claude-code`. Or copy the skill folder (.apm/skills/docs-impact-localizer in microsoft/apm) into .claude/skills/docs-impact-localizer in your project. Claude Code loads it when a task matches its description.

How do I install Docs Impact Localizer in Codex?

Run `npx skills add microsoft/apm --skill docs-impact-localizer -a codex`. Or copy the skill folder (.apm/skills/docs-impact-localizer in microsoft/apm) into .agents/skills/docs-impact-localizer in your project. Codex loads it when a task matches its description.

Can I use Docs Impact Localizer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add microsoft/apm --skill docs-impact-localizer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/docs-impact-localizer, .gemini/skills/docs-impact-localizer, .github/skills/docs-impact-localizer and .opencode/skills/docs-impact-localizer in your project.

What does Docs Impact Localizer need to run?

Going by SKILL.md and its folder, Docs Impact Localizer needs the command-line tools its instructions call (gh).

Does Docs Impact Localizer access the network?

SKILL.md contains no URLs. Its commands use gh, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Docs Impact Localizer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Docs Impact Localizer use?

Docs Impact Localizer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Docs Impact Localizer use?

About 1.1k tokens (SKILL.md is roughly 4.3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Docs Impact Localizer?

Skills that share tags, products or a category with Docs Impact Localizer: Translating Locales (TriliumNext/Trilium, 38k stars), Write Locale Translations (videojs/video.js, 40k stars), Translation Diff Translate (Devolutions/UniGetUI, 26k stars) and Plane UI Translation (makeplane/plane, 60k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Docs Impact Localizer?

microsoft (a GitHub organization, an official publisher) maintains it in microsoft/apm, which has 3,968 GitHub stars. The repository holds 27 skills in this directory. The repository was last updated on October 6, 2026.

Source: microsoft/apm on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Docs Impact Localizer

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

docs-impact-localizer

When to invoke

Inputs

Step 1: load page contents

Step 2: narrow scope inside each page

Step 3: detect cross-page conflicts

Step 4: emit the per-page task brief

Output contract

Anti-patterns

Files

Compare with similar skills

Similar skills

More from microsoft/apm

Questions about Docs Impact Localizer