CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-identity-java

Authenticate Java applications with Azure services using Microsoft Entra ID (Azure AD).

52

Quality

57%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

67%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 comprehensive, highly actionable reference for Azure Identity in Java with excellent executable code examples covering all credential types. Its main weaknesses are excessive length without progressive disclosure (everything inlined in one file) and some redundancy in environment variable listings and selection guidance. The 'Trigger Phrases' and 'When to Use' sections are boilerplate that waste tokens.

Suggestions

Split credential-specific details into separate referenced files (e.g., MANAGED_IDENTITY.md, SERVICE_PRINCIPAL.md) and keep SKILL.md as a concise overview with the selection matrix and DefaultAzureCredential example only.

Remove the 'Trigger Phrases' and 'When to Use' sections which provide no actionable value in the body content.

Consolidate the duplicate environment variable listings (they appear under 'Environment Credential' and again under 'Environment Variables' section).

DimensionReasoningScore

Conciseness

The skill is quite long (~300 lines) and includes some redundancy (e.g., environment variables listed twice, the 'Trigger Phrases' and 'When to Use' sections add no value for Claude). The credential table and selection matrix overlap. However, the code examples themselves are lean and well-structured.

3 / 5

Actionability

Every credential type has fully executable, copy-paste ready Java code with proper imports. The examples cover common configurations (system-assigned vs user-assigned MI, PEM vs PFX certificates, explicit vs env-var-based config). Error handling includes specific exception types.

5 / 5

Workflow Clarity

This is primarily a reference skill rather than a multi-step workflow, so the single-task exception applies. The DefaultAzureCredential chain order is clearly documented, the credential selection matrix provides clear decision guidance, and error handling shows recovery patterns. Minor gap: no explicit 'verify authentication works' step after setup.

4 / 5

Progressive Disclosure

All content is inlined in a single monolithic file with no references to supporting files. At ~300 lines covering 10+ credential types, this would benefit significantly from splitting into separate files (e.g., a quick-start overview with references to detailed credential guides). No bundle files exist to support progressive disclosure.

2 / 5

Total

14

/

20

Passed

Description

47%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 niche (Java Azure authentication) with good keyword coverage for discoverability, but it lacks concrete actions beyond the single verb 'authenticate' and entirely omits a 'Use when...' clause. Adding specific capabilities and explicit trigger guidance would significantly improve skill selection accuracy.

Suggestions

Add a 'Use when...' clause with trigger phrases like 'Use when the user needs to set up Azure authentication in Java, configure service principals, managed identities, or use the azure-identity SDK.'

Expand the capabilities list with concrete actions such as 'configure DefaultAzureCredential, set up managed identity authentication, handle token acquisition, integrate with Azure Key Vault or Azure Storage credentials.'

Include common synonyms and related terms like 'OAuth', 'service principal', 'client credentials', 'MSAL', 'azure-identity' to improve trigger term coverage.

DimensionReasoningScore

Specificity

Names the domain (Java + Azure authentication) but the action is generic — 'authenticate' is a single vague verb with no elaboration on concrete steps like configuring credentials, setting up managed identities, or handling token refresh.

2 / 5

Completeness

Provides a vague 'what' (authenticate Java apps with Azure) but has no 'when' clause or trigger guidance. The absence of a 'Use when...' clause caps this at 3, and the weak 'what' brings it to 2.

2 / 5

Trigger Term Quality

Includes several strong natural keywords: 'Java', 'Azure', 'authenticate', 'Microsoft Entra ID', 'Azure AD'. Missing some common variations like 'OAuth', 'token', 'managed identity', 'service principal', 'credentials', or 'azure-identity SDK'.

4 / 5

Distinctiveness Conflict Risk

The combination of Java + Azure + authentication is fairly specific and unlikely to conflict with most other skills. However, it could overlap with broader Azure SDK skills or general authentication skills, creating minor conflict risk.

4 / 5

Total

12

/

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.