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.

60

Quality

71%

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

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.

The content is highly actionable with thorough executable examples, but it is a long monolithic reference that underuses progressive disclosure and lacks any real sequenced workflow with validation checkpoints. Tightening redundancy and moving reference material into separate files would lift the weaker dimensions.

Suggestions

Move the Credential Types Reference, Key Exceptions, and Managed Identity Support tables into a separate reference file and link to it from a concise overview, improving progressive disclosure and conciseness.

Remove time-sensitive version numbers from the main body or relocate them to a clearly labeled version/compatibility section so they do not penalize conciseness.

Replace the filler 'When to Use' sentence with concrete trigger guidance (e.g., 'Use when authenticating Azure SDK clients, configuring DefaultAzureCredential chains, or setting up managed identity in production').

DimensionReasoningScore

Conciseness

Mostly efficient code and tables, but the ~330-line body carries redundant reference tables, time-sensitive version numbers ('Stable v1.17.1, Preview v1.18.0-beta.2'), and a vague filler 'When to Use' sentence that could be trimmed.

3 / 5

Actionability

Comprehensive, copy-paste-ready C# examples cover the common cases (DefaultAzureCredential, managed identity, client secret/certificate, DI, retry, logging, error handling).

5 / 5

Workflow Clarity

The body is a reference catalog organized by topic rather than a sequenced workflow, so validation checkpoints and feedback loops are absent; numbered Best Practices are advisory, not a process.

3 / 5

Progressive Disclosure

Section headers are clear, but with no bundle files present the entire bulk (Credential Types Reference, exception tables, managed-identity support list) is inlined in one long SKILL.md rather than split into one-level-deep referenced files.

3 / 5

Total

14

/

20

Passed

Description

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

The description is specific, third-person, and distinct, clearly identifying what the skill covers and giving concrete 'Use for' trigger guidance. It is just short of a 5 on completeness and trigger quality because the when-clause is a capability enumeration rather than natural user phrasing.

DimensionReasoningScore

Specificity

Names the domain and lists several concrete capabilities (DefaultAzureCredential, managed identity, service principals, developer credentials), with only minor gaps in coverage.

4 / 5

Completeness

Has a clear 'what' (authentication library for Azure SDK clients) and a 'Use for...' when-clause listing concrete triggers, but the when-guidance reads as a capability list rather than explicit natural trigger phrases.

4 / 5

Trigger Term Quality

Good keyword coverage with natural terms a user would say (DefaultAzureCredential, managed identity, service principals, Entra ID), though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Azure Identity SDK for .NET) with distinct triggers and minimal overlap risk with unrelated skills.

5 / 5

Total

17

/

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.