CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

azure-identity-dotnet

Azure Identity SDK for .NET. Authentication library for Azure SDK clients using Microsoft Entra ID. Use for DefaultAzureCredential, managed identity, service principals, and developer credentials.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is azure-identity-dotnet in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

An actionable, well-sectioned single-file reference with executable code covering the common Azure Identity scenarios. Its weaknesses are redundancy (credential listings duplicated, version numbers inline, filler 'When to Use' line) and the absence of any progressive disclosure — a 330-line monolith where the reference tables could live in separate files.

Suggestions

Split the bulk reference material (Credential Types Reference table, Key Exceptions table, Managed Identity Support list) into a references/ file (e.g. references/credential-reference.md) and link to it from SKILL.md, keeping the body as a lean overview with quick-start code.

Remove the duplicate credential enumeration — either the 'Credential Types' code sections or the 'Credential Types Reference' table — and delete the filler 'When to Use' sentence or replace it with concrete guidance (e.g. 'Use DefaultAzureCredential in development, ManagedIdentityCredential or a service-principal credential in production').

Move version numbers ('Stable v1.17.1, Preview v1.18.0-beta.2') into a clearly labeled versions/release-notes section or drop them, so time-sensitive details don't stale the main content.

DimensionReasoningScore

Conciseness

Mostly efficient code-first reference with little concept explanation, but it includes redundant content: the credential landscape is listed twice (the 'Credential Types' sections and again in the 'Credential Types Reference' table), time-sensitive version numbers ('Stable v1.17.1, Preview v1.18.0-beta.2') appear outside any deprecated/versions section, and the closing 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview') is pure filler. Not a 4 because these are more than minor trimmable instances.

3 / 5

Actionability

Fully executable, copy-paste-ready guidance throughout: install commands ('dotnet add package Azure.identity'), complete C# snippets with using statements covering the common cases (DefaultAzureCredential usage, DI registration, managed identity variants, service principal with secret/certificate, custom chains, error handling with named exception types), plus concrete env-var blocks. The examples cover the scenarios a user is most likely to hit.

5 / 5

Workflow Clarity

As a reference skill there is no destructive or batch workflow requiring validation checkpoints, so the cap does not apply; the implicit decision flow (dev vs prod credential choice, DefaultAzureCredential chain order table, 'Use Deterministic Credentials in Production' best practice, try/catch error handling with the two key exceptions) is clearly laid out. Not a 5 because there is no explicit 'choose your credential' decision sequence and the 'When to Use' section is vague filler rather than a real checkpoint.

4 / 5

Progressive Disclosure

No bundle files exist (no references/, scripts/, or assets/), so everything — the full credential-type reference, exceptions table, managed-identity service list, and link tables — is inlined in a single ~330-line SKILL.md. Section headers are clear, but content that clearly belongs in separate reference files (the bulk credential reference tables, the exceptions reference) is inline with no one-level-deep external references at all, matching the anchor-3 pattern; the under-50-line exception does not apply at this size.

3 / 5

Total

15

/

20

Passed

Description

87%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 strong description: precise domain naming, third-person voice, and an explicit 'Use for' trigger clause with concrete credential terms. The only gaps are minor — no 'Azure AD' synonym and capability nouns rather than action verbs.

DimensionReasoningScore

Specificity

Names the domain precisely ('Authentication library for Azure SDK clients using Microsoft Entra ID') and lists several concrete capability areas ('DefaultAzureCredential, managed identity, service principals, and developer credentials'). Not a 5 because it names components/capabilities rather than concrete actions, and coverage is limited to credential types without touching configuration, error handling, or other SDK surface.

4 / 5

Completeness

Explicitly answers both questions: the 'what' is 'Authentication library for Azure SDK clients using Microsoft Entra ID' and the 'when' is the concrete trigger clause 'Use for DefaultAzureCredential, managed identity, service principals, and developer credentials.' This matches the anchor-5 pattern of a clear what plus an explicit use-when clause with concrete trigger phrases, so the 'cap at 3' rule for missing trigger guidance does not apply.

5 / 5

Trigger Term Quality

Good natural-keyword coverage: 'DefaultAzureCredential', 'managed identity', 'service principals', 'Azure Identity SDK for .NET', 'Microsoft Entra ID' — phrases users would actually say. Not a 5 because common synonyms like 'Azure AD' (the former name many users still use) and generic 'Azure authentication'/'auth' phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche: Azure Identity authentication specifically for .NET, with distinct triggers (DefaultAzureCredential, managed identity, Entra ID). Minimal conflict risk — only a hypothetical generic 'Azure SDK' skill would overlap, and the credential-specific triggers disambiguate well.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

administrakt0r/AI-Agents-Safe-Coding-Skills

Path

plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azure-identity-dotnet/SKILL.md

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.