CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

61

Quality

72%

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

Fix and improve this skill with Tessl

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

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%Scale 1-5

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

This is a solid API reference skill with excellent actionability—every credential type has executable C# code examples covering real-world scenarios. However, it's overly long for a single SKILL.md file, containing reference material (credential tables, supported services list, related SDKs) that could be split into separate files. Some content is redundant or explains things Claude already knows (thread safety, what managed identity services are supported), and the version numbers will become stale.

Suggestions

Split the credential types reference table, supported Azure services list, and detailed per-credential examples into a separate REFERENCE.md file, keeping SKILL.md as a concise overview with DefaultAzureCredential usage and the most common patterns.

Remove or condense content Claude already knows: the thread safety note, the 'When to Use' boilerplate, and the Related SDKs table (which duplicates the Installation section).

Move the version numbers to a clearly marked section or remove them entirely to avoid staleness.

Add a brief troubleshooting workflow: enable logging → identify which credential failed → check environment variables/configuration → retry, to improve workflow clarity for debugging scenarios.

DimensionReasoningScore

Conciseness

The skill is fairly comprehensive but includes some content Claude would already know (thread safety note, list of supported Azure services, the 'When to Use' section, and the Related SDKs table which largely repeats the Installation section). The credential types reference table and the detailed credential examples are useful but the overall document could be tightened significantly. The version numbers are time-sensitive and will become stale.

3 / 5

Actionability

The skill provides fully executable, copy-paste ready C# code examples for every credential type, DI integration, error handling, logging, retry configuration, and environment-based configuration. All common scenarios are covered with concrete, runnable code.

5 / 5

Workflow Clarity

The skill is primarily a reference/API skill rather than a multi-step workflow, so the bar is lower. The best practices section provides clear guidance on credential selection (dev vs prod), and the DefaultAzureCredential chain order table is very helpful. However, there's no explicit workflow for troubleshooting authentication failures (e.g., 'if DefaultAzureCredential fails, enable logging, check which credential in the chain failed, then...').

4 / 5

Progressive Disclosure

The content is a long monolithic document (~250 lines) with no bundle files to offload detail into. The credential types reference table, the full list of supported Azure services, and the detailed examples for every credential type could be split into separate reference files. The reference links section at the end is helpful but the document itself would benefit from being an overview that points to separate files for credential details and examples.

3 / 5

Total

15

/

20

Passed

Description

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

This is a solid description that clearly identifies its niche (Azure Identity SDK for .NET) and includes relevant technical trigger terms. Its main weakness is the lack of concrete action verbs describing what the skill helps accomplish, and the 'when' guidance could be more scenario-oriented rather than just listing feature names.

Suggestions

Add concrete action verbs describing what the skill does, e.g., 'Configure authentication, troubleshoot credential chains, set up managed identity for Azure SDK clients.'

Include common synonyms and variations users might use, such as 'Azure AD', 'Azure.Identity', 'token authentication', or 'NuGet package'.

DimensionReasoningScore

Specificity

Names the domain (Azure Identity SDK for .NET) and mentions specific concepts like DefaultAzureCredential, managed identity, service principals, and developer credentials, but these are more like feature names than concrete actions. No verbs describing what the skill actually does (e.g., 'configure authentication', 'troubleshoot credential chains').

3 / 5

Completeness

The 'what' is present (authentication library for Azure SDK clients) and there is a 'Use for...' clause that serves as a 'when' trigger. However, the 'when' is phrased as 'Use for' specific concepts rather than describing user scenarios or explicit trigger phrases like 'Use when the user needs to authenticate Azure SDK clients'.

4 / 5

Trigger Term Quality

Includes strong trigger terms like 'DefaultAzureCredential', 'managed identity', 'service principals', 'developer credentials', 'Azure SDK', 'Microsoft Entra ID', and 'authentication'. Missing some natural variations like 'Azure AD', 'token', 'credential provider', 'Azure.Identity NuGet', or '.NET authentication'.

4 / 5

Distinctiveness Conflict Risk

Highly distinctive with a clear niche: Azure Identity SDK specifically for .NET. The specific terms like 'DefaultAzureCredential', 'managed identity', and 'Microsoft Entra ID' make it very unlikely to conflict with other skills.

5 / 5

Total

16

/

20

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.