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.
81
77%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/azure-communication-common-java/SKILL.mdQuality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a solid skill description that clearly identifies its niche (Azure Communication Services Java utilities) and provides an explicit 'Use when' clause with relevant trigger terms. Its main weakness is that it describes the domain rather than listing concrete actions the skill enables, keeping specificity at a moderate level.
Suggestions
Add concrete actions such as 'Creates CommunicationTokenCredential instances, parses user/phone identifiers, handles token refresh callbacks' to improve specificity.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Azure Communication Services Java utilities) and mentions some specific concepts like CommunicationTokenCredential, user identifiers, and token refresh, but doesn't list concrete actions (e.g., 'create credentials', 'refresh tokens', 'parse identifiers'). | 2 / 3 |
Completeness | Clearly answers both 'what' (common utilities for Azure Communication Services in Java) and 'when' (explicit 'Use when' clause listing specific triggers like CommunicationTokenCredential, user identifiers, token refresh, and shared authentication). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords that a developer would use: 'CommunicationTokenCredential', 'user identifiers', 'token refresh', 'shared authentication', 'ACS services'. These are the exact terms a user working in this domain would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Azure Communication Services common utilities for Java. The specific trigger terms like 'CommunicationTokenCredential' and 'ACS services' make it very unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides solid, actionable Java code examples for Azure Communication Services authentication and identifiers, making it immediately useful. However, it's overly long for a SKILL.md, including patterns Claude already knows (instanceof checks, string parsing) and boilerplate sections that waste tokens. The content would benefit from splitting reference material into separate files and trimming sections that don't add unique knowledge.
Suggestions
Move the Identifier Parsing, Type Checking, and Cloud Environments sections into a separate REFERENCE.md file, keeping only the Key Concepts table and core credential examples in SKILL.md.
Remove the 'Trigger Phrases', 'When to Use', and 'Limitations' boilerplate sections as they add no actionable value.
Cut the Async Token Refresh section—it's just wrapping a CompletableFuture.get() which Claude already knows how to do.
Add error handling examples for token refresh failures since the best practices section calls this out but provides no concrete guidance.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary sections like 'Trigger Phrases', 'When to Use', and 'Limitations' boilerplate that add no value. The Type Checking Identifiers section and Identifier Parsing section are patterns Claude already knows (instanceof checks, string prefix matching). The content could be tightened significantly. | 2 / 3 |
Actionability | The skill provides fully executable Java code examples throughout, including Maven dependency, credential creation with static and refreshing tokens, identifier construction, and a complete client creation pattern. Code is copy-paste ready with clear imports. | 3 / 3 |
Workflow Clarity | The skill is primarily a reference/API guide rather than a multi-step workflow, so workflow clarity is less critical. However, the best practices section mentions error handling and token refresh failures without showing how to handle them. The credential lifecycle (create → use → close) is shown but not as an explicit validated workflow. | 2 / 3 |
Progressive Disclosure | The content is a long monolithic document (~200+ lines) with no references to external files. The Key Concepts table provides a good overview, but sections like Cloud Environments, Identifier Parsing, and Type Checking could be split into a reference file. Everything is inline with no navigation to supplementary materials. | 2 / 3 |
Total | 9 / 12 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.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- sickn33/antigravity-awesome-skills
- Commit
76cbde3
- 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.