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.
57
66%
Does it follow best practices?
Impact
—
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 common utilities for Java) and provides explicit trigger guidance via a 'Use when' clause with domain-specific keywords. Its main weakness is that it describes the domain and concepts rather than listing concrete actions the skill performs, which slightly reduces specificity.
Suggestions
Add concrete action verbs describing what the skill does, e.g., 'Creates and manages CommunicationTokenCredential instances, parses user identifiers, handles token refresh callbacks, and configures shared authentication across ACS services.'
| 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 CommunicationTokenCredential, user identifiers, token refresh, or shared authentication scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords 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/shared utilities in 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
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill functions as a comprehensive API reference document rather than a focused, concise skill. While the code examples are excellent and fully executable, the content is far too verbose—it includes many patterns Claude already knows (instanceof checks, try-with-resources), and dumps all reference material inline without any progressive disclosure structure. The boilerplate sections (Trigger Phrases, When to Use, Limitations) add no value.
Suggestions
Reduce content by 60%+: keep only the CommunicationTokenCredential creation patterns (static and proactive refresh) and a summary table of identifier types—remove the type checking, identifier parsing, async token refresh, and cloud environments sections as these are standard Java patterns or rarely needed details.
Remove boilerplate sections (Trigger Phrases, When to Use, Limitations) that waste tokens without adding actionable guidance.
If the full API reference is needed, split identifier details, cloud environments, and Entra ID authentication into separate referenced files to improve progressive disclosure.
Add a validation/error handling workflow for token refresh failures since this is listed as a best practice but never demonstrated with concrete code.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is excessively verbose at ~250 lines, acting as a comprehensive API reference rather than a concise skill. It explains concepts Claude already knows (type checking with instanceof, try-with-resources, environment variables), includes redundant sections (Trigger Phrases, boilerplate Limitations), and the identifier parsing/type checking sections are standard Java patterns that don't need explicit instruction. | 1 / 3 |
Actionability | The code examples are concrete, executable, and copy-paste ready. Every section includes real Java code with proper imports, specific class names, and realistic usage patterns including the ChatClient integration example. | 3 / 3 |
Workflow Clarity | The skill is primarily a reference/API guide rather than a multi-step workflow, but the best practices section lists important steps (proactive refresh, close credentials) without integrating them into a clear workflow sequence. There are no validation checkpoints or error recovery patterns for token refresh failures despite mentioning error handling as a best practice. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files and no bundle files. All content is inline including detailed API reference material (identifier types, cloud environments, token access patterns) that could be split into separate reference documents for better organization. | 1 / 3 |
Total | 7 / 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
76aea27
- 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.