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.
64
75%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Advisory
Suggest reviewing before use
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/plugins/azure-skills/skills/azure-rbac/SKILL.mdQuality
Discovery
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.
This is a strong skill description that clearly articulates what the skill does (Azure RBAC role selection, CLI/Bicep code generation, permissions guidance) and when to use it (with an explicit WHEN clause containing diverse, natural trigger phrases). The description is specific to a well-defined domain, making it highly distinguishable from other skills. The trigger terms cover a wide range of realistic user queries.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description lists multiple specific concrete actions: finding the right Azure RBAC role, generating CLI commands, generating Bicep code for role assignment, and providing guidance on permissions required to grant roles. | 3 / 3 |
Completeness | Clearly answers both 'what' (find RBAC roles with least privilege, generate CLI commands and Bicep code, provide permissions guidance) and 'when' (explicit WHEN clause with multiple trigger phrases covering various user scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: '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', 'permissions to assign roles'. These are realistic, varied phrasings users would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Azure RBAC role assignment specifically. The combination of Azure, RBAC, Bicep, managed identity, and least privilege creates a very specific domain that is unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides a reasonable high-level workflow for finding and assigning Azure RBAC roles using specific tools, and includes useful prerequisite information. However, it lacks concrete examples (sample CLI output, Bicep snippets, example role lookups), explicit step sequencing with validation checkpoints, and could be better structured to separate the workflow from reference material.
Suggestions
Add a numbered workflow with explicit steps and a validation checkpoint (e.g., 'Confirm the identified role grants only the minimum required permissions before proceeding to assignment').
Include at least one concrete example showing a sample role lookup, the resulting CLI command, and the corresponding Bicep snippet so Claude has a clear pattern to follow.
Add a conditional decision tree or explicit branching for when no built-in role matches vs. when one does, rather than embedding it in prose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient but includes some unnecessary explanation (e.g., 'The most common roles with this permission are' is slightly verbose). The prerequisites section is useful but could be tighter. Overall reasonably lean. | 2 / 3 |
Actionability | References specific tools (azure__documentation, azure__extension_cli_generate, azure__bicepschema, azure__get_azure_bestpractices) which gives Claude concrete actions, but provides no example inputs/outputs, no sample CLI commands, no sample Bicep snippets, and no concrete code. The guidance is tool-directed but not copy-paste ready. | 2 / 3 |
Workflow Clarity | There is an implicit multi-step sequence (find role → generate CLI → generate Bicep), but steps are not explicitly numbered or sequenced, and there are no validation checkpoints (e.g., confirming the role matches before proceeding to assignment). The conditional for custom roles is mentioned but not structured as a clear decision point. | 2 / 3 |
Progressive Disclosure | The content is short enough that a single file is acceptable, but the prerequisites section is inlined rather than clearly separated, and there are no references to external files. The structure could benefit from clearer section headers (e.g., a 'Workflow' section distinct from 'Prerequisites'). For a skill with no bundle files, the organization is adequate but not well-signaled. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- microsoft/azure-skills
- Commit
d02fd24
- Reviewed
Table of Contents
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.