azure-communication-common-java

Azure Communication Services common utilities for Java. Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services.

1.33x

Quality

86%

Does it follow best practices?

Impact

100%

1.33x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

The canonical home for this skill is azure-communication-common-java in sickn33/agentic-awesome-skills

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.

A code-rich, highly actionable ACS Java reference with strong copy-paste examples and minimal padding. Its weaknesses are structural: it is a long monolithic file with no progressive disclosure to separate files, and it presents topics rather than a sequenced workflow with validation checkpoints.

Suggestions

Split the larger reference blocks (Entra ID authentication, identifier parsing/type-checking) into files under references/ and point to them from SKILL.md to improve progressive disclosure.

Add a short sequenced workflow for the common end-to-end task (create credential → wire into Chat/Calling client → dispose) with an explicit verification/checkpoint step so credential setup has a clear, validated process.

Trim the 'Common Usage Patterns' section, which duplicates the proactive-refresh construction already shown earlier, to tighten conciseness.

Dimension	Reasoning	Score
Conciseness	Mostly lean code with brief, useful comments and no lecturing on basic concepts, but the 'Best Practices' and 'Common Usage Patterns' sections restate credential-construction logic already shown, so minor trimming is possible rather than the every-token-earns-its-place bar at 5.	4 / 5
Actionability	Copy-paste-ready Java with imports, real method calls, and specific options covering static/proactive/async refresh, Entra ID, every identifier type, parsing, type-checking, and cleanup — matching the fully-executable anchor.	5 / 5
Workflow Clarity	Sections are logically ordered (install → credential variants → identifiers → parsing → cleanup) but this is a topical reference rather than a sequenced process, with no validation checkpoints; the destructive/batch cap does not apply since token-credential creation is neither, yet no explicit workflow sequence exists to lift it above 3.	3 / 5
Progressive Disclosure	Good section headers provide structure, but at ~300 lines all content is inlined in SKILL.md with no external references (no references/scripts/assets bundle exists), so material that could live in separate files (full identifier-parsing logic, Entra example) is not split out.	3 / 5
	Total	15 / 20 Passed

Description

100%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 concise, specific, and uses third-person voice with an explicit 'Use when...' clause naming concrete ACS types. It cleanly answers both what the skill does and when to invoke it.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete capabilities ('CommunicationTokenCredential, user identifiers, token refresh, or shared authentication'), matching the comprehensive-coverage anchor rather than the minor-gaps anchor at 4.	5 / 5
Completeness	Explicitly states both what ('Azure Communication Services common utilities for Java') and when ('Use when working with CommunicationTokenCredential...'), matching the anchor that requires both with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural terms a developer would actually say ('token refresh', 'user identifiers', 'CommunicationTokenCredential', 'ACS') with the real API type names; matches the comprehensive-coverage anchor.	5 / 5
Distinctiveness Conflict Risk	Scoped to Azure Communication Services common Java utilities with named class types, a clear niche with minimal overlap risk versus other skills.	5 / 5
	Total	20 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azure-communication-common-java/SKILL.md
Commit: debb2ec

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.