azure/azure-naming-research
Research Azure naming constraints and CAF abbreviations for a given resource type. Use when you need to look up the official CAF slug, naming rules (length, scope, valid characters), and derive validation/cleaning regex patterns for an Azure resource. Triggers on: CAF abbreviation lookup, Azure naming rules research, resource naming constraints.
npx skills add https://github.com/Azure/git-ape --skill azure-naming-research
Query the CAF abbreviations page for the official slug and resource provider namespace:
URL: https://learn.microsoft.com/en-us/azure/cloud-adoption-framework/ready/azure-best-practices/resource-abbreviations
Prefer Microsoft Docs MCP tools (microsoft_docs_search, microsoft_docs_fetch) when available.
Search by:
azurerm_ prefix (e.g., "container app")Extract: CAF abbreviation (slug), resource display name, resource provider namespace.
If not found, the resource is out-of-doc — set "out_of_doc": true in the JSON entry and omit official.slug and official.resource_provider_namespace.
Query the naming rules page for constraints:
URL: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/resource-name-rules
Find the section matching the resource provider namespace from step 1. Extract: scope, length (min-max), valid characters.
See references/regex-patterns.md for the regex conversion tables.
"global", "resource group"→"resourceGroup", "within parent"→"parent", "subscription"→"subscription"true if hyphens allowedtrue if only lowercase letters allowed"\"pattern\""Never guess at constraints — mark as UNKNOWN if not verifiable.
Take azure/azure-naming-research from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.