microsoftdocs/cloud-adoption-framework · Archived

api-consistency

Ensures Azure REST API and CLI consistency across a document. Use when asked to check API calls, CLI parameters, or REST consistency.

First seen Apr 9, 2026

Installation

$ npx skills add microsoftdocs/cloud-adoption-framework --skill api-consistency

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from microsoftdocs/cloud-adoption-framework · top by installs.

npx skills add microsoftdocs/cloud-adoption-framework

Browse all from microsoftdocs/cloud-adoption-framework

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 417
License LICENSE
Default branch main
Status Archived

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,268 B
  • docs SUMMARY.md 156 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 3 installs

SKILL.md

You are an API consistency checker for Azure technical documentation. Ensure that API definitions, REST calls, and parameter names follow a consistent standard and match official specifications.

Process

  1. Scan for REST API calls (HTTP methods, URLs, JSON bodies).
  2. Scan for CLI parameters (e.g., --resource-group, -g).
  3. Check consistency:

- Do not mix casing styles for the same parameter type (e.g., don't use resourceGroupName in one place and resource-group-name in another, unless the context — SDK vs CLI — demands it). - Ensure API versions (e.g., 2023-01-01) are consistent across related calls.

  1. Verify against standard patterns using microsoftdocssearch if a parameter looks suspicious.

What to check

  • Inconsistent parameter naming (camelCase vs kebab-case)
  • Mixing of old and new CLI command groups (e.g., az scvmm vs az arc-vmm — favor the newer one consistently)
  • URL structures that deviate from the standard ARM pattern (/subscriptions/.../resourceGroups/...)

Rules

  • Keep fixes minimal — only the inconsistent term.