Comprehensive Azure compliance and security auditing capabilities including best practices assessment, Key Vault expiration monitoring, and resource configuration validation. WHEN: compliance scan, security audit, BEFORE running azqr (compliance cli tool), Azure best practices, Key Vault expiration check, compliance assessment, resource review, configuration validation, expired certificates, expiring secrets, orphaned resources, policy compliance, security posture evaluation.
83
78%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.github/skills/azure-compliance/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 defines its Azure compliance and security auditing domain with specific capabilities and an explicit, comprehensive WHEN clause containing numerous natural trigger terms. The description is well-structured, uses third person voice appropriately, and provides enough specificity to distinguish it from other skills. Minor improvement could include slightly more structured formatting, but overall it performs well across all dimensions.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'best practices assessment', 'Key Vault expiration monitoring', 'resource configuration validation', plus mentions expired certificates, expiring secrets, orphaned resources, and policy compliance. | 3 / 3 |
Completeness | Clearly answers both 'what' (Azure compliance/security auditing with best practices assessment, Key Vault monitoring, resource validation) and 'when' (explicit WHEN clause with numerous trigger scenarios like compliance scan, security audit, before running azqr, etc.). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'compliance scan', 'security audit', 'Azure best practices', 'Key Vault expiration check', 'expired certificates', 'expiring secrets', 'orphaned resources', 'policy compliance', 'security posture evaluation'. These are terms Azure practitioners would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Azure-specific terminology, Key Vault references, azqr tool mention, and compliance/security focus. Unlikely to conflict with general coding or non-Azure skills. The niche is clearly Azure compliance and security auditing. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is well-organized with strong progressive disclosure and clear reference navigation, but falls short on actionability by lacking concrete tool invocation examples and expected outputs. The workflow is present but needs validation checkpoints, and there's some redundancy between the 'When to Use' and 'Skill Activation Triggers' sections that could be consolidated.
Suggestions
Add a concrete example showing an actual MCP tool invocation (e.g., calling mcp_azure_mcp_extension_azqr with specific parameters) and its expected output format.
Add validation checkpoints to the assessment workflow, e.g., 'Verify azqr completed successfully by checking output artifacts exist' and 'Confirm Key Vault access before attempting item enumeration'.
Merge 'When to Use This Skill' and 'Skill Activation Triggers' into a single section to reduce redundancy and save tokens.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill includes some unnecessary sections like 'Skill Activation Triggers' which largely duplicates 'When to Use This Skill', and the 'Best Practices' section contains generic advice Claude already knows. The tables are well-structured but there's redundancy between sections. | 2 / 3 |
Actionability | The skill lists MCP tools and provides a workflow, but lacks concrete executable examples. The assessment workflow is high-level (e.g., 'Run azqr and capture output artifacts') without showing actual tool invocations or expected outputs. Key details are deferred to reference files. | 2 / 3 |
Workflow Clarity | The 5-step assessment workflow provides a sequence but lacks validation checkpoints and feedback loops. There's no explicit verification step after running azqr or after remediation. The error handling table is helpful but disconnected from the workflow steps. | 2 / 3 |
Progressive Disclosure | Excellent use of progressive disclosure with clear one-level-deep references organized by topic. The 'Reference Index' table with 'When to Load' guidance and the explicit instruction 'Load these on demand — do NOT read all at once' are well-designed. SDK references are also well-organized by language. | 3 / 3 |
Total | 9 / 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.
ec7b8ff
Table of Contents
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.