Tessl • The management layer for AI agent skills

SkillPublic

azure

Azure identity (Workload Identity, OIDC, Entra ID), resource tagging, AKS platform patterns, RBAC scoping, and production-readiness review — with Terraform generation.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/azure/SKILL.md

Quality

Content

78%Weight 40%Scale 1-5

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

A highly actionable, well-structured multi-mode skill with excellent executable examples and validation loops in several workflows. Its weaknesses are repeated content across sections, missing verification steps in the identity and rbac modes, and references to bundle files that do not actually exist.

Suggestions

Ship the referenced bundle files (references/azure.md, examples/azure/) or remove the repeated 'Read references/azure.md before responding' instructions — they currently point to nonexistent paths.

Move per-mode detail (e.g. the full AKS Terraform baseline and identity federation snippets) into the reference file so SKILL.md serves as a lean overview with one-level-deep references.

Add validation steps to the identity and rbac modes, e.g. verifying a federated credential with a test GitHub Actions login and confirming a role assignment's effective scope with 'az role assignment list'.

Dimension	Reasoning	Score
Conciseness	The body is dense and executable with no padding explaining concepts Claude already knows, but the merge(local.common_tags, {...}) pattern repeats across the tagging and aks sections and MC_ tagging guidance appears in three places (tagging mode, review warnings, common mistakes), so minor trimming is possible.	4 / 5
Actionability	Fully executable, copy-paste-ready guidance throughout: complete az CLI commands, Terraform HCL, Kubernetes YAML, a custom-role JSON definition, and a commit-pinned GitHub Action, with parameterized placeholders covering the common cases for each mode.	5 / 5
Workflow Clarity	Sequences are clear and some modes have real feedback loops (tagging: audit → enforce → remediate → validate with 'az policy state summarize'; aks: 'kubectl get nodes' checkpoint; review: CRITICAL/WARNING checklist), but the identity and rbac modes lack validation steps such as testing a federated credential or verifying an assignment after creation.	4 / 5
Progressive Disclosure	Internal structure is good with clearly signaled references ('Read references/azure.md before responding'), but those references are dangling — no references/ or examples/ directory ships with the skill — and each mode inlines substantial detail that the reference split was evidently meant to hold, leaving organization and navigation incomplete.	3 / 5
	Total	16 / 20 Passed

Description

66%Weight 40%Scale 1-5

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

A domain-rich, fairly specific description that names its niche clearly and includes strong natural trigger terms. Its main weakness is the complete absence of any 'when to use this' guidance, which caps completeness, and a few missing common synonyms like 'managed identity' and 'Azure AD'.

Suggestions

Add an explicit trigger clause, e.g. 'Use when working with Azure identity, AKS clusters, resource tagging policy, RBAC assignments, or reviewing an Azure environment for production readiness.'

Include missing natural trigger terms users commonly say: 'managed identity', 'Azure AD', 'service principal', and 'role assignment'.

Trim or reword 'with Terraform generation' (e.g. 'generates Terraform for the above') to reduce overlap with a dedicated Terraform skill while keeping the capability visible.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas — 'Workload Identity, OIDC, Entra ID', 'resource tagging', 'RBAC scoping', 'production-readiness review' — but they are domain nouns rather than enumerated actions, and 'AKS platform patterns' is generic, so coverage falls short of the comprehensive anchor 5.	4 / 5
Completeness	The 'what' is clear and multi-faceted, but there is no 'Use when...' clause or equivalent explicit trigger guidance anywhere in the description, which caps completeness at 3 per the rubric guidelines.	3 / 5
Trigger Term Quality	Good natural keywords users would say ('Azure', 'AKS', 'RBAC', 'Entra ID', 'OIDC', 'tagging'), but common variations like 'managed identity', 'Azure AD', 'service principal', and 'role assignment' are missing, which keeps it below the comprehensive synonym coverage of anchor 5.	4 / 5
Distinctiveness Conflict Risk	The Azure platform niche is unmistakable and unlikely to trigger the wrong skill, but the trailing 'with Terraform generation' creates minor overlap with a dedicated Terraform skill (the body itself hands off to /platform-skills:terraform), matching anchor 4 rather than 5.	4 / 5
	Total	15 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 5 missing	Warning

	Total	14 / 16 Passed

Repository: nitinjain999/platform-skills
Path: skills/azure/SKILL.md
Revision: c2e75b7

Reviewed: 16 hours ago

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.

azure

Table of Contents

Is this your skill?