mcpbeat

Documentation Consistency

azure/documentation-consistency

Keeps ingestion repository and published GPT-RAG documentation aligned with shipped formats, configuration, indexing, deployment, audit, and operator behavior.

266 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
186
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository 
npx skills add https://github.com/Azure/GPT-RAG --skill documentation-consistency

The instruction itself

1 sections, as written by the author

Ingestion documentation consistency

  • Identify the user, operator, or cross-component behavior that changed.
  • Search this repository for the format, configuration key, index field,

endpoint, job type, contract, and previous terminology.

  • Update ingestion-specific service or audit guidance in README.md.
  • Search the docs branch of Azure/GPT-RAG for cross-component user and

operator guidance and update every affected page in the coordinated change.

  • Register new published pages in that branch's mkdocs.yml.
  • Ensure examples match current defaults, App Configuration labels,

supported deployment modes, and released component behavior.

Keep the service README concise and link to

https://azure.github.io/GPT-RAG/ for broad product guidance. Report the

documentation branch or pull request in the implementation handoff.

How to use it

Copy the folder

Take azure/documentation-consistency from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.