CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-identity-java

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

52

Quality

58%

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

63%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 a strong, code-dense reference for Azure Identity in Java with good decision support and error handling, but it suffers from duplicated sections, a misleading token-caching example, and no progressive disclosure into separate files. These keep the highest dimensions at 4 rather than 5.

Suggestions

Remove the duplicated Environment Variables section (lines 320-339 largely repeat 153-176) and the vacuous 'When to Use' line to tighten conciseness toward a 4-5.

Fix the Token Caching example to actually demonstrate token caching (e.g., enablePersistentCache / token cache persistence) rather than repeating enableAccountIdentifierLogging, which is already shown under Logging.

Move the per-credential deep-dive code blocks into reference files (e.g., references/credentials.md) and have SKILL.md link to them one level deep, improving progressive disclosure from 3 to 4-5.

DimensionReasoningScore

Conciseness

The body is largely code examples with little prose, but it duplicates the Environment Variables section, repeats the enableAccountIdentifierLogging snippet across Token Caching and Logging, and includes a vacuous 'When to Use' line, fitting the 'mostly efficient but could be tightened' anchor.

3 / 5

Actionability

It provides extensive copy-paste-ready Java with imports across every credential type, plus a credential selection matrix, landing in the 'mostly executable guidance with minor gaps' band; the Token Caching block misleadingly shows logging rather than caching keeps it from a 5.

4 / 5

Workflow Clarity

Though a reference catalog rather than a sequential workflow, it is well-organized by credential type, includes a Credential Selection Matrix for decisions, and an Error Handling section with a feedback loop, fitting 'clear sequence with most checkpoints present' minus a true multi-step process.

4 / 5

Progressive Disclosure

No bundle files exist and all reference material is inlined in a ~360-line SKILL.md with no external navigation, matching the 'some structure but content that should be separate is inline' anchor despite good section headers.

3 / 5

Total

14

/

20

Passed

Description

53%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 clear and specific about its Azure Identity (Java) niche but stops short of listing multiple concrete actions and omits any explicit 'Use when' trigger guidance. It reads as competent but incomplete, capping the strongest dimensions at the midpoint.

Suggestions

Add 2-3 more concrete actions (e.g., 'acquire access tokens', 'configure managed identity', 'chain credentials') to lift specificity from 3 toward 5.

Append an explicit 'Use when...' clause naming natural trigger phrases (e.g., 'Use when authenticating Java apps to Azure, configuring managed identity, or handling Azure login in Java').

Include natural synonyms users actually say ('Azure login Java', 'Azure credentials Java') alongside the technical terms to broaden trigger coverage.

DimensionReasoningScore

Specificity

The description names the domain (Java, Azure, Entra ID/Azure AD) and one concrete action ('Authenticate'), matching the anchor for naming a domain plus 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

It gives a clear 'what' (authenticate Java apps with Azure via Entra ID) but has no 'Use when...' clause or explicit trigger guidance, which per the judging guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

It includes relevant terms ('Azure services', 'Microsoft Entra ID', 'Azure AD', 'Java', 'Authenticate') but leans technical and omits natural user phrasing like 'Azure login' or 'Azure credentials', fitting the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The combination of Java plus Azure Identity plus Entra ID carves a fairly distinct niche with only minor overlap risk against closely related Azure SDK skills, landing above the midpoint.

4 / 5

Total

13

/

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.