Microsoft AzureKnown publisherAzure/gpt-rag-orchestrator/.github/skills/documentation-consistency/SKILL.mddocumentation-consistency
Skill107 starsChanged 13 days agoMITView on GitHub
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.
11 other projects use a version of this, 9 of them edited.
Adopted by
Most recently taken up by
- Azure/agent-app-mcpedited, first seen Nov 8, 2026
- Azure/gpt-rag-mcpedited, first seen Nov 2, 2026
- Azure/agent-app-ingestionedited, first seen Oct 30, 2026
- Azure/gpt-rag-ingestionedited, first seen Oct 30, 2026
- Azure/agent-app-orchestratorword for word, first seen Oct 30, 2026
- Azure/agent-app-uiedited, first seen Oct 30, 2026
Used with
Projects with it also use component-release.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Microsoft AzureSkillcomponent-release
Prepares a verifiable Agent Landing Zone UI release. Use for release branches, VERSION, changelog entries, tags, release notes, and compatibility evidence; never publish without explicit human approval.
Also in 4 projects that use this
Other versions11 projects use a version of this.
Word for word · 1
- Azure/agent-app-orchestrator★ 107100% same
Edited · 9
- Azure/agent-landing-zone★ 1.2k41% same
- Azure/GPT-RAG★ 1.2k41% same
- Azure/agent-app-ingestion★ 18812% same
- Azure/gpt-rag-ingestion★ 18812% same
- Azure/agent-app-mcp★ 2212% same
- Azure/gpt-rag-mcp★ 2212% same
- Azure/bicep-ptn-aiml-landing-zone★ 1911% same
- Azure/agent-app-ui★ 1019% same
- Azure/gpt-rag-ui★ 1019% same
Wrote their own version · 1
- wallstop/unity-helpers★ 176same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository6 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- architecture-decisionSkill
- engineering-principlesSkill
- orchestrator-releaseSkill
- releaseSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Keep engineering instructions, governance policies, ADRs, and executable contracts local.
- Distinctive: line 15
Search the documentation source for the feature, API, strategy, configuration key, parameter, component, and previous terminology.
- Distinctive: line 17
Update every affected page in the same coordinated change.
- Distinctive: line 19
Keep component READMEs concise and link to published topics.
- Distinctive: line 21
Ensure examples match current defaults, supported runtime strategies, configuration labels, authentication, deployment modes, and rollback.
- Distinctive: line 23
Update this repository's README links when central topics change.
“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Agent Landing Zone Orchestrator documentation consistency
Product, operator, and developer guides live only in
Azure/AI-Landing-Zones on main
and are published at https://azure.github.io/AI-Landing-Zones/agent-landing-zone/.
Keep engineering instructions, governance policies, ADRs, and executable
contracts local.
- 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:in the central repository'smkdocs.yml. - Keep component READMEs concise and link to published topics. Do not reintroduce local product, operator, or developer guides.
- Ensure examples match current defaults, supported runtime strategies, configuration labels, authentication, deployment modes, and rollback.
- Update this repository's README links when central topics change. Local startup and testing guidance belongs in local development and application testing.
- Report the central documentation commit 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.