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.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-communication-common-java/SKILL.md

Quality

Content

65%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 body is a well-organized, code-heavy reference that is largely actionable and concise, but it inlines a large amount of API detail that belongs in separate reference files and offers no multi-step workflow with validation checkpoints. Redundancy between sections and a misleading async example are the main weaknesses.

Suggestions

Split the identifier and credential API detail into a separate REFERENCE.md (or references/ files) and keep SKILL.md as a concise overview with one-level-deep pointers, improving progressive_disclosure.

Remove the duplicated proactive-refresh setup in "Common Usage Patterns" and the repeated MicrosoftTeamsUserIdentifier example in "Cloud Environments" to tighten conciseness.

Fix the "Async Token Refresh" example so it does not block on CompletableFuture.get() (or relabel it), and either use or drop the unused CommunicationIdentifierModel import to raise actionability.

Dimension	Reasoning	Score
Conciseness	The body is code-first and avoids explaining basic concepts Claude already knows, but contains redundancy (proactive refresh setup appears in both "Proactive Token Refresh" and "Common Usage Patterns"; MicrosoftTeamsUserIdentifier appears in both identifiers and cloud-environment sections) that could be trimmed, so it is not a 5.	4 / 5
Actionability	Provides concrete, mostly copy-paste-ready Java covering the common cases, with minor gaps: the "Async Token Refresh" example blocks via CompletableFuture.get() (misleadingly labeled async) and CommunicationIdentifierModel is imported but unused.	4 / 5
Workflow Clarity	Content is organized into logical sections (install → concepts → credential → identifiers → best practices), but as a reference catalog there is no multi-step workflow with explicit validation checkpoints or feedback loops, and "Best Practices" mentions handling refresh failures without demonstrating it.	3 / 5
Progressive Disclosure	Section headers give clear structure, but all ~300 lines of API reference are inlined in SKILL.md with no separate reference files and no signaled pointers to deeper material, which is the central gap the dimension targets.	3 / 5
	Total	14 / 20 Passed

Description

87%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 strong: it clearly states what the skill covers and gives concrete, distinctive trigger conditions in third person. Minor gaps in action specificity and synonym coverage keep specificity and trigger_term_quality at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Names the domain ("Azure Communication Services common utilities for Java") and several concrete items ("CommunicationTokenCredential, user identifiers, token refresh, or shared authentication"), but these are topics rather than a comprehensive list of actions, so it falls short of a 5.	4 / 5
Completeness	Explicitly states what it does ("Azure Communication Services common utilities for Java") and when to use it ("Use when working with CommunicationTokenCredential, user identifiers, token refresh, or shared authentication across ACS services"), matching the anchor that answers both what and when with concrete triggers.	5 / 5
Trigger Term Quality	Includes natural terms users would say ("CommunicationTokenCredential", "token refresh", "user identifiers", "ACS services", "shared authentication"), but misses some synonyms and specific class names, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (ACS common Java utilities) with distinctive triggers like CommunicationTokenCredential and ACS-specific authentication, giving minimal overlap with other skills.	5 / 5
	Total	18 / 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: sickn33/antigravity-awesome-skills
Path: skills/azure-communication-common-java/SKILL.md
Commit: 1f67c44

Reviewed: about 14 hours 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.