docs-impact-localizer Skill
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 p Published by microsoft in apm.
Decision snapshot
Is this a fit?
Documentation, Includes SKILL.md, Reusable instructions
Compatibility not yet detected.
Permission behavior not yet detected.
Copy skill directory
2 months ago · MIT license
No specific cautions were detected. Review the source and requested permissions before installing.
What is docs-impact-localizer Skill?
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 p Published by microsoft in apm. This profile combines repository metadata with install, compatibility, and usage signals so developers can quickly decide whether it fits their agent workflow before opening the source repository.
Automated repository signals based on public metadata such as recency, license, installation evidence, and adoption. These are not a security audit or endorsement. See how SkillIndex evaluates profiles.
Key capabilities
- Includes SKILL.md support
- Reusable instructions support
- Documentation
- Documentation use cases
Declared skill metadata
- Source file: .apm/skills/docs-impact-localizer/SKILL.md
These fields retain source and confidence evidence from the indexed SKILL.md.
Compatibility and setup
- Install or run with Copy skill directory
When to use docs-impact-localizer Skill
- Use it for documentation.
Built with
Editorial notes
Source
- Creator: microsoft
- Repository: microsoft/apm
- Skill file: .apm/skills/docs-impact-localizer/SKILL.md
What it does
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 p
Skill instructions
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: inplace. For nochange you don't run. For structural the architect runs first; you may run after, scoped to existing pages that need amendment. Inputs - scopepages[] 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 scopepages[], 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 p
Verified compatibility and discovery
Frequently asked questions
What is docs-impact-localizer?
docs-impact-localizer is a open-source AI agent skill with Copy skill directory. Use this skill to translate a classifier's in-place verdict into a precise, page-by-page work plan for the docs-sync panel.
Who is docs-impact-localizer best for?
docs-impact-localizer is best for reusing agent instructions, scripts, and references, documentation workflows.
How do I install docs-impact-localizer?
Install or run docs-impact-localizer using Copy skill directory. Check docs-impact-localizer for the latest setup command.
Is docs-impact-localizer actively maintained?
docs-impact-localizer may need a closer maintenance check before production use.
Project health auto-fetched from the source repository.
Maintain this resource?
Review this source-backed profile, send a correction with evidence, or link to it from your documentation. Claims verify your relationship to the project; profile facts still require source evidence and editorial review.
