CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-identity-ts

Authenticate to Azure services with various credential types.

45

Quality

48%

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

Quality

Content

59%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 skill is a comprehensive but overly long reference catalog of Azure Identity credential types in TypeScript. Its strength is the breadth of concrete, executable code examples covering nearly every credential scenario. Its weaknesses are the monolithic structure that should leverage progressive disclosure, some unnecessary content (filler 'When to Use' section, obvious best practices), and the lack of a troubleshooting/debugging workflow for authentication failures.

Suggestions

Split the credential catalog into a separate REFERENCE.md file, keeping only DefaultAzureCredential and the most common 1-2 patterns in SKILL.md with links to the full reference.

Remove the 'When to Use' filler section and trim 'Best Practices' to only non-obvious guidance (e.g., remove 'Never hardcode credentials' and 'Handle token refresh').

Add a brief troubleshooting workflow: if auth fails → enable debug logging → check credential chain order → verify environment variables.

Remove the 'Key Types' section which is just a list of imports Claude can infer from the examples above it.

DimensionReasoningScore

Conciseness

The skill is largely a reference catalog of credential types. While each individual snippet is lean, the sheer breadth (12+ credential types, key types listing, custom implementation) makes it verbose for a skill file. The 'Best Practices' section includes items Claude already knows (e.g., 'Never hardcode credentials', 'Handle token refresh - Azure SDK handles this automatically'). The 'When to Use' section is a meaningless filler sentence.

3 / 5

Actionability

Nearly all examples are concrete, executable TypeScript snippets with proper imports and constructor arguments. Minor gaps: placeholder values like '<tenant-id>' are used throughout without a concrete end-to-end example showing how to wire a credential into a real service call beyond the single BlobServiceClient example.

4 / 5

Workflow Clarity

This is primarily a reference/catalog skill rather than a multi-step workflow, so the bar is lower. The DefaultAzureCredential section clearly shows the credential chain order, and the overall organization flows logically from recommended approach to specific types to debugging. However, there's no troubleshooting workflow (e.g., 'if authentication fails, check X, then Y') which would be valuable for a credential skill.

4 / 5

Progressive Disclosure

The content is a monolithic ~200-line file with no references to external files. The extensive API catalog (all credential types, key types, custom implementation, debugging) would benefit from being split into separate reference files, with the SKILL.md serving as a concise overview pointing to detailed sections. No bundle files exist to support this.

2 / 5

Total

13

/

20

Passed

Description

36%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 identifies a clear domain (Azure authentication) but is too terse and vague to be effective for skill selection. It lacks specific credential types, concrete actions beyond 'authenticate', and has no 'Use when...' clause to guide Claude on when to select this skill.

Suggestions

Add a 'Use when...' clause with trigger terms like 'Azure login', 'service principal', 'managed identity', 'Azure AD token', 'DefaultAzureCredential'.

List specific credential types and actions, e.g., 'Authenticate using service principals, managed identities, client secrets, or certificate-based credentials. Configures Azure SDK credential chains.'

Include common synonyms and related terms users might use, such as 'sign in', 'Azure access', 'OAuth', 'RBAC', or 'Azure CLI auth'.

DimensionReasoningScore

Specificity

Names the domain (Azure authentication) and hints at an action ('Authenticate') but 'various credential types' is vague—no specific credential types or concrete actions are listed.

2 / 5

Completeness

Has a vague 'what' (authenticate to Azure with various credentials) but no 'when' clause at all. The lack of explicit trigger guidance caps this score low per the rubric.

2 / 5

Trigger Term Quality

Includes 'Azure', 'authenticate', and 'credential' which are relevant keywords, but misses natural terms users might say like 'login', 'sign in', 'service principal', 'managed identity', 'Azure AD', 'token', 'OAuth', or 'DefaultAzureCredential'.

3 / 5

Distinctiveness Conflict Risk

Somewhat specific to Azure authentication, which narrows the domain, but could overlap with other Azure-related skills or general authentication/credential management skills. Without specifying credential types, the boundaries are unclear.

3 / 5

Total

10

/

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.