agentleFS
Sign inStart free
Microsoft AzureKnown publisherAzure/git-ape/.github/skills/azure-naming-research/SKILL.md

azure-naming-research

Skill274 starsChanged 28 days agoMITView on GitHub

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.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prefer Microsoft Docs MCP tools (microsoft_docs_search, microsoft_docs_fetch) when available.

    line 16
  2. Very specific:

    If not found, the resource is out-of-doc — set "out_of_doc": true in the JSON entry and omit official.slug and …

    line 25
  3. Distinctive:

    Never guess at constraints — mark as UNKNOWN if not verifiable.

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Azure Naming Research

Procedure

1. Look up CAF abbreviation

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:

  1. Terraform resource name without azurerm_ prefix (e.g., "container app")
  2. Resource provider namespace if known
  3. Common name (e.g., "Container Apps")

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.

2. Look up Azure naming rules

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.

3. Derive field values

See references/regex-patterns.md for the regex conversion tables.

  • scope mapping: "globally unique"→"global", "resource group"→"resourceGroup", "within parent"→"parent", "subscription"→"subscription"
  • dashes: true if hyphens allowed
  • lowercase: true if only lowercase letters allowed
  • validation_regex and regex: Use the pattern tables in the reference file. Both MUST use escaped double quotes: "\"pattern\""

Never guess at constraints — mark as UNKNOWN if not verifiable.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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.

Check your setup, free