azadvertizerlisted

Deterministic, offline-first lookups over Azure Policy, Policy Initiative, and RBAC Role metadata sourced from AzAdvertizer's CSV exports — including the cross-references that exist nowhere else in one place (which roles a policy uses, which initiatives include a policy, which policies a role is used by). Use whenever you need accurate current facts about an Azure built-in policy, initiative/policy-set, or RBAC role — definitions, effects, allowed effect values, categories, role actions/dataActions, or the policy↔role and policy↔initiative relationships — for writing or reviewing Azure IaC, governance, or landing-zone work. Fetches each CSV once into a provenance-stamped cache and answers queries offline; stdlib only, JSON envelope output. Pairs with terragrunt-skill, azure-architect, and fact-verifier (snapshots become tier-1 sources).
kevin-burns/claude-skills · ★ 8 · Data & Documents · score 81

Install: claude install-skill kevin-burns/claude-skills

# azadvertizer [AzAdvertizer](https://www.azadvertizer.net) (by Julian Hayward) tracks Azure governance capabilities — Policies, Initiatives (policy sets), and RBAC Roles — and publishes them as **downloadable CSV exports**. There is **no API**. This skill turns those CSVs into deterministic offline lookups: fetch once, validate, cache with provenance, then query without touching the network. The unique value is the **cross-references** AzAdvertizer computes that raw Azure sources don't give you in one place: `policyRolesUsed`, `policyUsedInPolicySet`, and (per role) `UsedInPolicy`. For canonical *definitions* where licensing/authority matters, prefer Azure's own sources (`az policy definition list`, `az role definition list`, the `Azure/azure-policy` repo) — use this skill for the enriched, cross-referenced view. ## How you'll usually use it In most cases this skill answers a concrete Azure-governance question that came up while writing or reviewing IaC (Terraform/Terragrunt/Bicep), designing a landing zone, or doing a least-privilege review. The common shapes: 1. **"What does this policy do — its effect, allowed effects, and what roles does it assign?"** → `get policy <id|name>` then `rel policy-roles <id>`. Typical before adding a `policyAssignment` (a `deployIfNotExists`/`modify` policy needs the right role, and this tells you which). 2. **"What's in this initiative / which built-in initiative includes this policy?"** → `get initiative <id>` or `rel polic