Cloud Cost Optimization
wshobson/agents
Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.
Keeps Agent Landing Zone Orchestrator user and operator documentation aligned with shipped behavior.
Install Documentation Consistency
$ npx skills add Azure/agent-app-orchestrator --skill documentation-consistency -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Azure/agent-app-orchestrator documentation-consistency --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Azure/agent-app-orchestrator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.github/skills/documentation-consistency .claude/skills/documentation-consistency && rm -rf skills-srcUse ~/.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/
Install the "documentation-consistency" agent skill from https://github.com/Azure/agent-app-orchestrator/tree/main/.github/skills/documentation-consistency into .claude/skills/documentation-consistency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-consistency", 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 install https://github.com/Azure/agent-app-orchestrator/tree/main/.github/skills/documentation-consistencyType 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.
$ npx skills add Azure/agent-app-orchestrator --skill documentation-consistency -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Azure/agent-app-orchestrator documentation-consistency --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/agent-app-orchestrator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.github/skills/documentation-consistency .agents/skills/documentation-consistency && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "documentation-consistency" agent skill from https://github.com/Azure/agent-app-orchestrator/tree/main/.github/skills/documentation-consistency into .agents/skills/documentation-consistency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-consistency", 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.
$ npx skills add Azure/agent-app-orchestrator --skill documentation-consistency -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Azure/agent-app-orchestrator documentation-consistency --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/agent-app-orchestrator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.github/skills/documentation-consistency .cursor/skills/documentation-consistency && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "documentation-consistency" agent skill from https://github.com/Azure/agent-app-orchestrator/tree/main/.github/skills/documentation-consistency into .cursor/skills/documentation-consistency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-consistency", 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 https://github.com/Azure/agent-app-orchestrator.git --path .github/skills/documentation-consistency--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Azure/agent-app-orchestrator --skill documentation-consistency -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Azure/agent-app-orchestrator documentation-consistency --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/agent-app-orchestrator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.github/skills/documentation-consistency .gemini/skills/documentation-consistency && rm -rf skills-srcUse ~/.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/
Install the "documentation-consistency" agent skill from https://github.com/Azure/agent-app-orchestrator/tree/main/.github/skills/documentation-consistency into .gemini/skills/documentation-consistency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-consistency", 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.
$ gh skill install Azure/agent-app-orchestrator documentation-consistencyInstalls 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).
$ npx skills add Azure/agent-app-orchestrator --skill documentation-consistency -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Azure/agent-app-orchestrator.git skills-src && mkdir -p .github/skills && cp -r skills-src/.github/skills/documentation-consistency .github/skills/documentation-consistency && rm -rf skills-srcUse ~/.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/
Install the "documentation-consistency" agent skill from https://github.com/Azure/agent-app-orchestrator/tree/main/.github/skills/documentation-consistency into .github/skills/documentation-consistency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-consistency", 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.
$ npx skills add Azure/agent-app-orchestrator --skill documentation-consistency -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Azure/agent-app-orchestrator documentation-consistency --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Azure/agent-app-orchestrator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.github/skills/documentation-consistency .opencode/skills/documentation-consistency && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "documentation-consistency" agent skill from https://github.com/Azure/agent-app-orchestrator/tree/main/.github/skills/documentation-consistency into .opencode/skills/documentation-consistency/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "documentation-consistency", 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
documentation-consistency- GitHub stars
- 103
- Token cost
- ~351 tokens
- SKILL.md length
- 146 words
- Files
- 1
- Skills in repo
- 5
- Repo updated
- First seen
- Licence
- MIT
At a glance
Keeps Agent Landing Zone Orchestrator user and operator documentation aligned with shipped behavior.
- Works in 8 steps: Identify the user or operator behavior… → Search the documentation source for the… → Update every affected page in the same… → …
- Runtime strategies
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
- Configuration keys
What it does
Documentation Consistency is an agent skill from Azure/agent-app-orchestrator, published by the product's own GitHub organization. Keeps Agent Landing Zone Orchestrator user and operator documentation aligned with shipped behavior. Use for runtime strategies, APIs, configuration keys, deployment, defaults, operations, or breaking changes.
Its SKILL.md is about 350 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 Cloud architecture. It works with Microsoft Azure. The repository describes itself as: Agent orchestration service for the Agent Landing Zone, built on Microsoft Foundry Agent Service and Microsoft Agent Framework. Runs agentic RAG workflows across specialized… The licence is MIT.
When your agent uses it
- Runtime strategies
- Configuration keys
- Breaking changes
Example prompts
- “Use the documentation-consistency skill to keep Agent Landing Zone Orchestrator user and operator documentation aligned with shipped behavior”
- “/documentation-consistency”
Workflow steps
8 steps, taken from the first numbered list in SKILL.md.
- Identify the user or operator behavior that changed.
- Search the documentation source for the feature, API, strategy,
- Update every affected page in the same coordinated change.
- Register new pages under nav: in mkdocs.yml.
- Keep this service README focused; link to the published site instead of
- Ensure examples match current defaults, supported runtime strategies,
- Update this repository's README when service-local setup or contracts are
- Report the documentation branch or pull request in the implementation
What it can do on your machine
Read from SKILL.md and the folder at commit 0e67231. 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
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
azure.github.io
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
Documentation Consistency loads about 351 tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 146 words of instructions outside code blocks.
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 Azure/agent-app-orchestrator at commit 0e67231, republished under its MIT licence (© Azure). 146 words, ~351 tokens.
Download SKILL.mdSave it as
.claude/skills/documentation-consistency/SKILL.md (or your agent's skills folder).- name
- documentation-consistency
- description
- Keeps Agent Landing Zone Orchestrator user and operator documentation aligned with shipped behavior. Use for runtime strategies, APIs, configuration keys, deployment, defaults, operations, or breaking changes.
Agent Landing Zone Orchestrator documentation consistency
User-facing documentation lives on the docs branch of Azure/agent-landing-zone and
is published at https://azure.github.io/AI-Landing-Zones/agent-landing-zone/.
- Identify the user or operator behavior that changed.
- Search the documentation source for the feature, API, strategy, configuration key, parameter, component, and previous terminology.
- Update every affected page in the same coordinated change.
- Register new pages under
nav:inmkdocs.yml. - Keep this service README focused; link to the published site instead of creating a second long-lived source of product truth.
- Ensure examples match current defaults, supported runtime strategies, configuration labels, authentication, deployment modes, and rollback.
- Update this repository's README when service-local setup or contracts are intentionally documented here.
- Report the documentation branch or pull request in the implementation handoff.
A user-visible change is incomplete until documentation is updated or a search demonstrates that no published page is affected.
© Azure, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .github/skills/documentation-consistency of Azure/agent-app-orchestrator.
Open the folder on GitHubat commit 0e67231
Compare with similar skills
Documentation Consistency 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Documentation Consistency this skillAzure/agent-app-orchestrator | 103 | — | ~351 | Automated safety check: Pass | MIT | |
| Cloud Cost Optimizationwshobson/agents | 40k | 14 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Thesvgglincker/thesvg | 2.8k | — | ~1.5k | Automated safety check: Pass | MIT | |
| Azure Architecture Autopilotgithub/awesome-copilot | 40k | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Dangling DNS Finderanirudhbiyani/findmytakeover | 180 | — | ~1.8k | Automated safety check: Pass | GPL-3.0 | |
| Azure Bicep Skilltimothywarner-org/claude-code | 224 | — | ~2.9k | Automated safety check: Pass | MIT |
Similar skills
Thesvg
glincker/thesvg
Fetch brand SVG logos and cloud architecture icons (AWS, Azure, GCP) from theSVG.
- Official
Azure Architecture Autopilot
github/awesome-copilot
Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.
Dangling DNS Finder
anirudhbiyani/findmytakeover
Detect dangling DNS records and subdomain-takeover risks across a multi-cloud environment by running the bundled findmytakeover tool.
Azure Bicep Skill
timothywarner-org/claude-code
A skill your agent uses when authoring, reviewing, or refactoring Azure Bicep code.
Hybrid Cloud Networking
wshobson/agents
Configure secure, high-performance connectivity between on-premises infrastructure and cloud platforms using VPN and dedicated connections.
More from Azure/agent-app-orchestrator
- Official
Release
Azure/agent-app-orchestrator
Prepare and reconcile Agent Landing Zone Orchestrator releases, including authoritative version discovery, semantic version selection, release branches, VERSION and CHANGELOG updates, release notes…
- Official
Architecture Decision
Azure/agent-app-orchestrator
Conducts and records a verifiable Agent Landing Zone Orchestrator architectural decision.
- Official
Engineering Principles
Azure/agent-app-orchestrator
Agent Landing Zone Orchestrator architecture and implementation principles.
- Official
Orchestrator Release
Azure/agent-app-orchestrator
Prepares and validates Agent Landing Zone Orchestrator releases.
Related
Works with
Categories
Questions about Documentation Consistency
What does Documentation Consistency do?
Keeps Agent Landing Zone Orchestrator user and operator documentation aligned with shipped behavior. Documentation Consistency is an agent skill from Azure/agent-app-orchestrator, published by the product's own GitHub organization. Keeps Agent Landing Zone Orchestrator user and operator documentation aligned with shipped behavior.
When should I use Documentation Consistency?
Documentation Consistency fits situations like: runtime strategies; configuration keys; breaking changes.
How do I install Documentation Consistency in Claude Code?
Run `npx skills add Azure/agent-app-orchestrator --skill documentation-consistency -a claude-code`. Or copy the skill folder (.github/skills/documentation-consistency in Azure/agent-app-orchestrator) into .claude/skills/documentation-consistency in your project. Claude Code loads it when a task matches its description.
How do I install Documentation Consistency in Codex?
Run `npx skills add Azure/agent-app-orchestrator --skill documentation-consistency -a codex`. Or copy the skill folder (.github/skills/documentation-consistency in Azure/agent-app-orchestrator) into .agents/skills/documentation-consistency in your project. Codex loads it when a task matches its description.
Can I use Documentation Consistency 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 Azure/agent-app-orchestrator --skill documentation-consistency -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/documentation-consistency, .gemini/skills/documentation-consistency, .github/skills/documentation-consistency and .opencode/skills/documentation-consistency in your project.
What does Documentation Consistency need to run?
SKILL.md names no scripts, command-line tools or credentials: Documentation Consistency is instructions for the agent only.
Does Documentation Consistency access the network?
SKILL.md names 1 domain. As links in the text: azure.github.io. This is read from the text; nothing was executed.
Is Documentation Consistency 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 Documentation Consistency use?
Documentation Consistency 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 Documentation Consistency use?
About 351 tokens (SKILL.md is roughly 1.4k 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 Documentation Consistency?
Skills that share tags, products or a category with Documentation Consistency: Cloud Cost Optimization (wshobson/agents, 40k stars), Thesvg (glincker/thesvg, 2.8k stars), Azure Architecture Autopilot (github/awesome-copilot, 40k stars) and Dangling DNS Finder (anirudhbiyani/findmytakeover, 180 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Documentation Consistency?
Azure (a GitHub organization, an official publisher) maintains it in Azure/agent-app-orchestrator, which has 103 GitHub stars. The repository holds 5 skills in this directory. The repository was last updated on October 8, 2026.
Source: Azure/agent-app-orchestrator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.