CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-identity-ts

Authenticate to Azure services with various credential types.

53

Quality

60%

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-ts/SKILL.md

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 body is a highly actionable, code-rich reference that lets examples speak for themselves, but it functions as a flat catalog rather than a guided workflow and inlines content that would benefit from progressive disclosure into separate reference files.

Suggestions

Add a short decision guide (e.g., a flow or table) for choosing among DefaultAzureCredential, managed identity, service principal, and interactive login based on environment.

Move the bulk type/API listing, sovereign clouds, and custom credential sections into separate reference files and link to them from SKILL.md to improve progressive disclosure.

Trim redundant sections (the "Key Types" import block and the vacuous "When to Use" line) to tighten token efficiency.

DimensionReasoningScore

Conciseness

Mostly code-forward and efficient with brief section intros, but includes minor trimmable redundancy such as the "Key Types" import listing and the vague filler line "This skill is applicable to execute the workflow or actions described in the overview."

4 / 5

Actionability

Provides fully executable, copy-paste-ready TypeScript for every common credential path (DefaultAzureCredential, managed identity variants, service principal, browser/device-code, custom chain, sovereign clouds, bearer token provider).

5 / 5

Workflow Clarity

Structured as a reference catalog of credential types with no sequenced workflow, no decision guidance for choosing among them, and no validation/verification checkpoints.

3 / 5

Progressive Disclosure

Well-organized with clear section headers, but roughly 300 lines are inlined monolithically with no external reference files for the API/type listing, sovereign clouds, or advanced patterns.

3 / 5

Total

15

/

20

Passed

Description

48%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 clearly states the skill's domain (Azure authentication) but is thin on concrete actions and entirely lacks a "Use when" trigger clause, which caps completeness. It is distinctive but would benefit from natural trigger phrases.

Suggestions

Add a "Use when…" clause naming concrete user phrases (e.g., authenticate to Azure, Azure login, managed identity, service principal credentials).

List specific concrete actions instead of the generic "Authenticate with various credential types" (e.g., acquire access tokens, configure DefaultAzureCredential, use managed identity).

Include natural synonyms and file/SDK cues (Azure AD, @azure/identity, tokens) to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the Azure-auth domain but offers only one generic action ("Authenticate") with a vague qualifier "various credential types" rather than concrete actions like acquire tokens or instantiate specific credentials.

2 / 5

Completeness

Has a clear "what" but no "Use when…" or equivalent trigger clause; per rubric guidelines a missing explicit trigger caps completeness at 3.

3 / 5

Trigger Term Quality

Contains relevant natural keywords ("Authenticate", "Azure", "credential types") but misses common synonyms a user would say such as "login", "Azure AD", "managed identity", or "service principal".

3 / 5

Distinctiveness Conflict Risk

Targets a clear niche (Azure authentication) with minimal conflict risk; only minor overlap with broader Azure or general identity skills.

4 / 5

Total

12

/

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.