Official agent skill

Docs Impact Architect

A skill your agent uses when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR.

OfficialMITAuto-check passedDevOps & Cloud

Install Docs Impact Architect

skills CLI

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

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

GitHub CLI

$ gh skill install microsoft/apm docs-impact-architect --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-architect .claude/skills/docs-impact-architect && 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-architect" agent skill from https://github.com/microsoft/apm/tree/main/.apm/skills/docs-impact-architect into .claude/skills/docs-impact-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-impact-architect", 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-architect

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-architect -a codex

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

GitHub CLI

$ gh skill install microsoft/apm docs-impact-architect --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-architect .agents/skills/docs-impact-architect && 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-architect" agent skill from https://github.com/microsoft/apm/tree/main/.apm/skills/docs-impact-architect into .agents/skills/docs-impact-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-impact-architect", 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-architect -a cursor

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

GitHub CLI

$ gh skill install microsoft/apm docs-impact-architect --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-architect .cursor/skills/docs-impact-architect && 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-architect" agent skill from https://github.com/microsoft/apm/tree/main/.apm/skills/docs-impact-architect into .cursor/skills/docs-impact-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-impact-architect", 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-architect

--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-architect -a gemini-cli

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

GitHub CLI

$ gh skill install microsoft/apm docs-impact-architect --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-architect .gemini/skills/docs-impact-architect && 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-architect" agent skill from https://github.com/microsoft/apm/tree/main/.apm/skills/docs-impact-architect into .gemini/skills/docs-impact-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-impact-architect", 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-architect

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-architect -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-architect .github/skills/docs-impact-architect && 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-architect" agent skill from https://github.com/microsoft/apm/tree/main/.apm/skills/docs-impact-architect into .github/skills/docs-impact-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-impact-architect", 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-architect -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-architect --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-architect .opencode/skills/docs-impact-architect && 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-architect" agent skill from https://github.com/microsoft/apm/tree/main/.apm/skills/docs-impact-architect into .opencode/skills/docs-impact-architect/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "docs-impact-architect", 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-architect
GitHub stars: 4k
Token cost: ~1.5k tokens
SKILL.md length: 591 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 when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR.

Works in 5 steps: read the corpus map, not the corpus → classify the structural shape → design the TOC delta → …
The docs-impact-classifier returns a structural verdict
SKILL.md covers When to invoke, Inputs, Step 1: read the corpus map,… and Step 2: classify the…, plus 5 more sections
Calls gh

What it does

Docs Impact Architect is an agent skill from microsoft/apm, published by the product's own GitHub organization. Use this skill when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR. Proposes TOC deltas (new pages, moves, merges) and emits new-page outline stubs that the doc-sync panel later fleshes out. Holds the 3-promise narrative (consume / produce / govern) and the persona ramps as hard constraints.

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

It sits in DevOps & Cloud, covering Monitoring and alerting. The repository describes itself as: Agent Package Manager. The licence is MIT.

When your agent uses it

The docs-impact-classifier returns a structural verdict
Signalling that the documentation TOC must change to accommodate the PR

Example prompts

“/docs-impact-architect”

Workflow steps

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

read the corpus map, not the corpus
classify the structural shape
design the TOC delta
validate against the 3-promise narrative
emit the architect report

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 Architect loads about 1.5k tokens when it runs. Until then it costs about 99 tokens; SKILL.md has 591 words of instructions outside code blocks.

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

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). 591 words, ~1,541 tokens.

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

name: docs-impact-architect
description: Use this skill when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR. Proposes TOC deltas (new pages, moves, merges) and emits new-page outline stubs that the doc-sync panel later fleshes out. Holds the 3-promise narrative (consume / produce / govern) and the persona ramps as hard constraints.

docs-impact-architect

Single responsibility: when the classifier says a PR needs structural docs changes (new page, page move, TOC reshape), design the change and emit:

A precise TOC delta (added pages, moved pages, retired pages)
New-page outline stubs (slug, title, persona, promise, H2 sections, key examples)
The persona-ramp impact (which ramp gains/loses a stop)

You are NOT the writer (doc-writer owns prose). You are the TOC architect. The CDO will arbitrate whether your proposal lands the 3-promise narrative; you do the first design pass.

When to invoke

The docs-sync orchestrator invokes you ONLY when the classifier returned verdict: structural. For no_change or in_place you don't run.

Inputs

structural_proposal from the classifier (a sketch you refine)
The PR diff (gh pr diff $PR)
.apm/docs-index.yml (full corpus map)
The PR description (for author-stated intent)

Step 1: read the corpus map, not the corpus

Load .apm/docs-index.yml entirely. Inspect chapters[], pages[], promises[]. This is your map. You do NOT read the 100+ page corpus unless a specific page is implicated by the classifier's sketch.

Step 2: classify the structural shape

Match the PR's surface change to one of these structural shapes:

Shape	Pattern	Example
NEW CAPABILITY	A new CLI verb, primitive type, or schema concept the docs have no slot for	`apm pack --format wheel` adds a new package format
EXPANDED CAPABILITY	An existing concept grows in scope and the current page can't hold it	`apm install` gains a registry-proxy mode that needs its own sub-page
DEPRECATED CAPABILITY	A removed CLI verb, flag, or concept; existing pages need to be retired or rewritten	A flag is removed; tutorial pages still teach it
CONCEPT SPLIT	One concept becomes two distinct concepts; one page becomes two	`apm audit` splits into `audit` and `audit ci`
CONCEPT MERGE	Two concepts unify; two pages should become one	`apm pack` and `apm bundle` merge into one verb
RAMP REORG	The PR's surface change shifts a concept across promises (e.g. an enterprise feature becomes consumer-default)	Policy enforcement moves from enterprise to consumer default behaviour

The structural shape drives the TOC delta shape.

Step 3: design the TOC delta

For each new page proposed, fill in:

yaml

new_page:
  slug: docs/src/content/docs/<persona>/<topic>.md
  title: "<short imperative title>"
  persona: consumer | producer | enterprise | cross
  promise: 1 | 2 | 3 | cross
  parent_chapter: <existing chapter slug>
  h2_sections:
    - "## Why <topic>"        # OPTIONAL -- skip unless concept is genuinely new
    - "## How to <use>"        # REQUIRED -- code first
    - "## Reference"           # OPTIONAL -- flag/option table
    - "## Troubleshooting"     # OPTIONAL -- only if known footguns
  bridges:
    incoming:                  # which existing pages should link TO this
      - {from: <slug>, link_text: <suggested>}
    outgoing:                  # which existing pages should this link FROM
      - {to: <slug>, link_text: <suggested>}
  ramp_impact: >-
    one-paragraph description of how this changes the <persona>
    ramp: which step it slots into, whether it adds a stop or
    replaces an existing one

For each moved/retired page:

yaml

moved_page:
  from: <slug>
  to: <slug>
  redirect_rationale: <one-sentence>

retired_page:
  slug: <slug>
  reason: <one-sentence>
  redirect_to: <slug>  # MUST exist; orphaning pages breaks SEO

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

Step 4: validate against the 3-promise narrative

Apply these hard rules. If any fails, redesign:

Every page belongs to exactly one promise. Cross-cutting pages (integrations, troubleshooting, reference) are explicitly marked promise: cross. If a new page straddles two promises, split it OR park it under cross.
Consumer pages don't pre-teach producer concepts. A consumer page may LINK to producer; it may not embed producer prose.
Producer pages don't pre-teach enterprise concepts. Same rule, one promise down.
No page is orphaned from the TOC. Every new page has a parent_chapter and at least one incoming bridge.
No retired page lacks a redirect_to. Search engines will index the old URL for months; the redirect is the SEO contract.

Step 5: emit the architect report

Return JSON:

json

{
  "structural_shape": "NEW CAPABILITY" | "EXPANDED CAPABILITY" | "DEPRECATED CAPABILITY" | "CONCEPT SPLIT" | "CONCEPT MERGE" | "RAMP REORG",
  "toc_delta": {
    "new_pages": [...],
    "moved_pages": [...],
    "retired_pages": [...],
    "chapter_changes": [...]
  },
  "promise_validation": {
    "all_pages_single_promise": true | false,
    "no_orphans": true | false,
    "no_unredirected_retires": true | false,
    "concerns": []
  },
  "downstream_in_place_pages": ["..."],
  "rationale": "<2-3 sentence summary of why this structural delta and not alternatives>"
}

downstream_in_place_pages[] is the handoff to the localizer -- after the architect approves the TOC, the localizer plans in-place edits to existing pages that REFERENCE the new structure.

Output contract

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

Anti-patterns

Inflating new-page counts to seem thorough. The minimal true delta wins.
Skipping the promise-validation step. The CDO will catch it; better to self-catch.
Designing a new chapter when an existing chapter has room. Always prefer extending over creating.
Forgetting redirect_to on retired pages. SEO debt is the silent corpus killer.

Files

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

Open the folder on GitHubat commit 280b8a7

Compare with similar skills

Docs Impact Architect 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 Architect compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Docs Impact Architect this skillmicrosoft/apm	4k	—	~1.5k	Automated safety check: Pass	MIT	yesterday
Mz Release SignoffMaterializeInc/materialize	6.4k	—	~7.2k	Automated safety check: Pass	Custom licence	today
Axiom Alerting Managementopenclaw/clawhub	9.5k	—	~2.1k	Automated safety check: Pass	MIT	today
KubeEye Cluster Inspectionkubesphere/kubesphere	17k	—	~3.6k	Automated safety check: Pass	Custom licence	2 mo ago
Axiom Dashboard Builderopenclaw/clawhub	9.5k	—	~4.9k	Automated safety check: Pass	MIT	today
Happy Infra Metrics and Grafanaslopus/happy	24k	—	~2k	Automated safety check: Notes	MIT	today

Similar skills

Mz Release Signoff
MaterializeInc/materialize
Verify a release candidate on the Grafana dashboards and sign off in release.
6.4k GitHub stars~7.2k tokensUpdated today
DevOps & CloudAuto-check passed
Axiom Alerting Management
openclaw/clawhub
Creates and manages Axiom monitors and notifiers end to end through the v2 API, with scripts for each CRUD operation and a recommended create-validate-tune workflow.
9.5k GitHub stars~2.1k tokensUpdated today
DevOps & CloudAuto-check passed
KubeEye Cluster Inspection
kubesphere/kubesphere
Deploys KubeEye on KubeSphere and writes InspectRule and InspectPlan resources to inspect cluster health, then retrieves the inspection reports.
17k GitHub stars~3.6k tokensUpdated 2 mo ago
DevOps & CloudAuto-check passed
Axiom Dashboard Builder
openclaw/clawhub
Designs and deploys Axiom dashboards through the API, choosing chart types and writing APL or metrics queries, with templates and migration notes for Splunk and Grafana.
9.5k GitHub stars~4.9k tokensUpdated today
DevOps & CloudAuto-check passed
Happy Infra Metrics and Grafana
slopus/happy
Queries live Prometheus metrics and manages Grafana dashboards as code for Happy's infrastructure, using the grafanactl CLI and the Grafana datasource proxy API.
24k GitHub stars~2k tokensUpdated today
DevOps & CloudAuto-check: notes
Axiom Cost Control
openclaw/clawhub
Finds unused data in Axiom by analyzing query patterns, then deploys a cost dashboard and ingest monitors to keep spend under the contract limit.
9.5k GitHub stars~1.7k tokensUpdated today
DevOps & CloudAuto-check passed

Questions about Docs Impact Architect

What does Docs Impact Architect do?

A skill your agent uses when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR. Docs Impact Architect is an agent skill from microsoft/apm, published by the product's own GitHub organization. Use this skill when the docs-impact-classifier returns a structural verdict, signalling that the documentation TOC must change to accommodate the PR.

When should I use Docs Impact Architect?

Docs Impact Architect fits situations like: the docs-impact-classifier returns a structural verdict; signalling that the documentation TOC must change to accommodate the PR.

How do I install Docs Impact Architect in Claude Code?

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

How do I install Docs Impact Architect in Codex?

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

Can I use Docs Impact Architect 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-architect -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-architect, .gemini/skills/docs-impact-architect, .github/skills/docs-impact-architect and .opencode/skills/docs-impact-architect in your project.

What does Docs Impact Architect need to run?

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

Does Docs Impact Architect 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 Architect 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 Architect use?

Docs Impact Architect 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 Architect use?

About 1.5k tokens (SKILL.md is roughly 6.2k 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 Architect?

Skills that share tags, products or a category with Docs Impact Architect: Mz Release Signoff (MaterializeInc/materialize, 6.4k stars), Axiom Alerting Management (openclaw/clawhub, 9.5k stars), KubeEye Cluster Inspection (kubesphere/kubesphere, 17k stars) and Axiom Dashboard Builder (openclaw/clawhub, 9.5k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Docs Impact Architect?

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 Architect

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-architect

When to invoke

Inputs

Step 1: read the corpus map, not the corpus

Step 2: classify the structural shape

Step 3: design the TOC delta

Step 4: validate against the 3-promise narrative

Step 5: emit the architect report

Output contract

Anti-patterns

Files

Compare with similar skills

Similar skills

More from microsoft/apm

Related

Questions about Docs Impact Architect