agentsclimarketplace

Azure governance policy guardrails

Skill Raishin/vanguard-frontier-agentic/skills/azure/azure-governance-policy-guardrails

Use this skill for Azure Policy guardrails, initiatives, assignment scope, management-group inheritance, exclusions, remediation risk, tag governance, allowed regions or SKUs, and staged governance rollout reviews.From its SKILL.md

Install
npx -y skills add Raishin/vanguard-frontier-agentic --skill azure-governance-policy-guardrails

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.6 KB, 446 tokens by cl100k_base, as published. Nobody here has run it

Azure Governance Policy Guardrails

Purpose

Design or review Azure governance guardrails with Azure Policy in a way that is enforceable, scope-aware, and safe to roll out.

When to use

Use this skill when the user asks for:

  • Azure Policy design or review,
  • initiatives versus single policy choices,
  • management-group or subscription assignment placement,
  • exclusions, exemptions, or inheritance concerns,
  • tag governance,
  • allowed locations, resource types, or SKU restrictions,
  • brownfield governance hardening,
  • compliance enforcement rollout safety.

Do not use this as a substitute for full regulatory interpretation, SOC operations, or writing full organization-specific policy JSON unless the user asks for that next.

Lean operating rules

  • Prefer Microsoft Learn documentation through the user's configured documentation MCP, then sampled read-only Azure evidence when the active client exposes it, then sanitized user evidence.
  • Separate confirmed facts from inference. If state was not queried or shown, say so.
  • Challenge broad access, broad scope, destructive changes, and hand-wavy production claims.
  • Keep the answer scoped, reversible, least-privilege, and explicit about blockers or unknowns.

References

Load these only when needed:

  • Operations guide — use for service-specific pitfalls, design rules, verification targets, and pushback criteria.
  • MCP and evidence path — use when choosing documentation-based evidence, sampled read-only Azure evidence, or sanitized user evidence.
  • Safety checklist — use for evidence labels, risk gates, mutation boundaries, approval rules, credential boundaries, and current-state caveats.
  • Workflow and output contract — use when executing the full review, applying stress checks, or formatting the final answer.
  • Official sources — use when you need the detailed Microsoft documentation list or source notes.

Response minimum

Return, at minimum:

  • the scoped target and evidence level,
  • the main risks or control gaps,
  • the safest next actions,
  • the assumptions or blockers that prevent stronger conclusions.

What ships with it: 6 files

14.1 KB alongside SKILL.md

Keep looking

Skills are one crate of 613,531. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.