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.

64

Quality

76%

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 ./skills/azure-identity-dotnet/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

65%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 comprehensive, highly actionable Azure.Identity reference with excellent copy-paste code, but it is verbose and monolithic — repeating credential/install content and inlining reference material that would benefit from separate files. The closing 'When to Use' section is generic filler.

Suggestions

Remove the redundant 'Credential Types Reference' table and 'Related SDKs' install column, or consolidate them with the earlier sections to eliminate duplication.

Delete or replace the generic filler 'When to Use' line ('This skill is applicable to execute the workflow or actions described in the overview.') with a concrete usage summary.

Split the large credential catalog and reference tables into a separate referenced file (e.g. references/credential-reference.md) and keep SKILL.md as a lean overview with one-level-deep links.

DimensionReasoningScore

Conciseness

The body is mostly efficient executable code, but it duplicates content (credential types appear both as code sections and again as a 'Credential Types Reference' table; install commands recur in 'Related SDKs') and ends with the filler line 'This skill is applicable to execute the workflow or actions described in the overview.'

3 / 5

Actionability

Provides fully executable, copy-paste-ready C# and bash examples that cover the common authentication scenarios (DefaultAzureCredential, managed identity, service principals, DI, error handling).

5 / 5

Workflow Clarity

Some sequences exist (the DefaultAzureCredential order table and numbered Best Practices), but this is reference material with no multi-step workflow that includes explicit validation checkpoints; no destructive/batch operation requires them here.

3 / 5

Progressive Disclosure

Section headers organize the content reasonably, but the file is a monolithic ~340-line reference with large catalog tables and full credential listings inlined; no bundle files exist and nothing is split out to separate referenced files.

3 / 5

Total

14

/

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, third-person description that clearly states what the skill does and when to use it, with concrete Azure credential trigger terms. Minor keyword-synonym gaps prevent a perfect specificity/trigger score.

DimensionReasoningScore

Specificity

Names the domain ('Authentication library for Azure SDK clients using Microsoft Entra ID') and several concrete items ('DefaultAzureCredential, managed identity, service principals, and developer credentials'), though coverage stops short of comprehensively enumerating all credential actions.

4 / 5

Completeness

Explicitly answers both 'what' ('Authentication library for Azure SDK clients using Microsoft Entra ID') and 'when' via a concrete 'Use for ...' clause listing specific trigger phrases.

5 / 5

Trigger Term Quality

Includes natural developer keywords a user would say ('managed identity', 'service principals', 'DefaultAzureCredential') with good coverage, though a few common synonyms (e.g. 'Entra ID', 'Azure AD', 'auth') are not present.

4 / 5

Distinctiveness Conflict Risk

Carves a clear niche (Azure Identity SDK for .NET) with distinct triggers, making conflict with unrelated skills unlikely.

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.

Validation15 / 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
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.