azure-rbac

Helps users find the right Azure RBAC role for an identity with least privilege access, then generate CLI commands and Bicep code to assign it. Also provides guidance on permissions required to grant roles. WHEN: bicep for role assignment, what role should I assign, least privilege role, RBAC role for, role to read blobs, role for managed identity, custom role definition, assign role to identity, what role do I need to grant access, permissions to assign roles.

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise and well-structured with clear tool orchestration, but lacks executable examples and any validation checkpoint for an access-changing operation. Actionability and workflow clarity are the limiting dimensions.

Suggestions

Add a short example of the expected output — e.g. a sample `az role assignment create` command and the resulting Bicep `roleAssignment` resource block — so guidance is copy-paste ready.

Insert a validation/verification step after assignment generation, such as checking for an existing assignment to avoid duplicates or confirming the assigned role's scope, since role assignment alters access.

Tighten repeated phrasing like "the desired permissions the user wants to assign to an identity" to reduce token overhead.

Dimension	Reasoning	Score
Conciseness	The body is lean and tool-focused, naming exact tools and their purpose without explaining concepts Claude already knows; nearly every token earns its place.	3 / 3
Actionability	It names specific tools (azure__documentation, azure__extension_cli_generate, azure__bicepschema, azure__get_azure_bestpractices) and a clear order, but provides no example CLI commands or Bicep snippets, leaving output concrete-but-incomplete.	2 / 3
Workflow Clarity	The find → custom-create → generate CLI → generate Bicep sequence with a conditional branch is clear, but role assignment is an access-changing operation with no validation or verification step, capping this dimension.	2 / 3
Progressive Disclosure	Under 50 lines with no external references needed; the single "Prerequisites for Granting Roles" section is well-organized, satisfying the simple-skill allowance.	3 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, uses third-person voice, and pairs concrete capabilities with a rich explicit WHEN trigger clause. It cleanly answers both what the skill does and when to use it with low conflict risk.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "find the right Azure RBAC role", "generate CLI commands and Bicep code to assign it", and "guidance on permissions required to grant roles" — rather than vague language.	3 / 3
Completeness	Clearly states what the skill does and provides an explicit "WHEN:" trigger clause equivalent to a 'Use when...' guide, satisfying both what and when.	3 / 3
Trigger Term Quality	The WHEN clause covers natural phrasings users would say, e.g. "what role should I assign", "least privilege role", "role for managed identity", "custom role definition", "permissions to assign roles".	3 / 3
Distinctiveness Conflict Risk	Scoped to Azure RBAC role assignment with role/identity-specific triggers, making it clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: microsoft/azure-skills
Commit: 2cd48ca

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.