Microsoft AzureKnown publisherAzure/agent-app-ingestion/.github/skills/documentation-consistency/SKILL.mddocumentation-consistency
Skill188 starsChanged 13 days agoMITView on GitHub
Keeps ingestion repository and published Agent Landing Zone documentation aligned with shipped formats, configuration, indexing, deployment, audit, and operator behavior.
11 other projects use a version of this.
Adopted by
Most recently taken up by
- Azure/agent-app-mcptheir own version, first seen Nov 8, 2026
- Azure/gpt-rag-mcptheir own version, first seen Nov 2, 2026
- Azure/gpt-rag-ingestionword for word, first seen Oct 30, 2026
- Azure/agent-app-orchestratortheir own version, first seen Oct 30, 2026
- Azure/gpt-rag-orchestratortheir own version, first seen Oct 30, 2026
- Azure/agent-app-uitheir own version, 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/gpt-rag-ingestion★ 188100% same
Edited · 0
None found.
Wrote their own version · 10
- Azure/agent-landing-zone★ 1.2ksame name
- Azure/GPT-RAG★ 1.2ksame name
- wallstop/unity-helpers★ 176same name
- Azure/agent-app-orchestrator★ 107same name
- Azure/gpt-rag-orchestrator★ 107same name
- Azure/agent-app-mcp★ 22same name
- Azure/gpt-rag-mcp★ 22same name
- Azure/bicep-ptn-aiml-landing-zone★ 19same name
- Azure/agent-app-ui★ 10same name
- Azure/gpt-rag-ui★ 10same 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 repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- architecture-decisionSkill
- engineering-principlesSkill
- ingestion-validationSkill
- releaseSkill
- service-releaseSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
4
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 9
Search this repository for the format, configuration key, index field, endpoint, job type, contract, and previous terminology.
- Distinctive: line 11
Keep component READMEs limited to concise descriptions and central pointers.
- Distinctive: line 12
Keep internal engineering instructions, ADRs, schemas, contracts, governance, workflows, policies, and changelogs local.
- Distinctive: line 21
Ensure examples match current defaults, App Configuration labels, supported deployment modes, and released component behavior.
“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
Ingestion documentation consistency
- Identify the user, operator, developer, or cross-component behavior that changed.
- Search this repository for the format, configuration key, index field, endpoint, job type, contract, and previous terminology.
- Keep component READMEs limited to concise descriptions and central pointers. Keep internal engineering instructions, ADRs, schemas, contracts, governance, workflows, policies, and changelogs local.
- Search
mainofAzure/AI-Landing-Zonesfor all affected application user, operator, and developer guides. Update every affected page in the coordinated change. Audit guidance belongs in Monitoring & audit, backed by executable local contracts, telemetry, and tests. - Register new published pages in that repository's
mkdocs.yml. - Ensure examples match current defaults, App Configuration labels, supported deployment modes, and released component behavior.
Publish application guides at https://azure.github.io/AI-Landing-Zones/agent-landing-zone/ rather than duplicating them locally. Report the central source commit or pull request and publication status in the implementation handoff.
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.