CtrlK
BlogDocsLog inGet started
Tessl Logo

azure-identity-java

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

58

Quality

67%

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

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

A thorough, executable Azure Identity reference with strong actionability and a clear selection workflow, weakened by duplicated sections, a misleading token-caching snippet, and a monolithic single-file structure with no progressive disclosure.

Suggestions

Deduplicate the environment-variable and logging sections into a single canonical block to tighten conciseness.

Fix the token-caching example so it actually enables caching rather than only calling enableAccountIdentifierLogging.

Split per-credential deep dives into references/ files (e.g. CREDENTIALS.md) and keep SKILL.md as an overview pointing to them.

DimensionReasoningScore

Conciseness

Mostly efficient reference material, but it duplicates the environment-variable and logging sections and repeats per-credential import boilerplate, so several sections could be consolidated or trimmed.

3 / 5

Actionability

Packed with copy-paste-ready Java builder snippets for every credential type and real exception classes, but the token-caching example is misleading (it calls enableAccountIdentifierLogging rather than a caching API).

4 / 5

Workflow Clarity

As a single-purpose reference skill the action is unambiguous: the Credential Selection Matrix maps each environment to a credential and Best Practices plus the error-handling try/catch sequence the decision.

5 / 5

Progressive Disclosure

Content is organized into clear sections, but everything is inlined into one ~360-line file with no external references, and the per-credential deep dives could reasonably be split into separate reference files.

3 / 5

Total

15

/

20

Passed

Description

65%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 distinct but incomplete: it states what the skill does without any explicit trigger guidance for when Claude should invoke it.

Suggestions

Add a "Use when..." clause naming concrete triggers, e.g. "Use when authenticating Java apps against Azure services, configuring managed identity, or setting up service principals."

Broaden trigger coverage with natural synonyms such as "managed identity", "service principal", and "az login".

Mention 1-2 more concrete actions (e.g. token caching, chained credentials) to lift specificity toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain (Java + Azure/Entra ID) and one concrete action ("Authenticate"), but does not enumerate the multiple credential mechanisms the body covers, so it is not comprehensive.

3 / 5

Completeness

The "what" is clearly stated ("Authenticate Java applications with Azure services using Microsoft Entra ID") but there is no "Use when..." trigger clause, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ("Azure", "Java", "Microsoft Entra ID", "Azure AD"), though common sub-terms like managed identity or service principal are absent.

4 / 5

Distinctiveness Conflict Risk

The Java + Azure Entra ID framing carves a clear niche unlikely to trigger for non-Java or non-Azure skills, with minimal conflict risk.

5 / 5

Total

15

/

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.