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.
82
73%
Does it follow best practices?
Impact
100%
1.33xAverage score across 3 eval scenarios
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 an explicit 'Use when' clause with relevant trigger terms. Its main weakness is that it describes the domain and concepts rather than listing specific concrete actions the skill enables. Adding action verbs like 'create', 'refresh', 'parse' would strengthen the specificity.
Suggestions
Add concrete action verbs to describe what the skill does, e.g., 'Creates and manages CommunicationTokenCredential instances, parses user identifiers, handles token refresh callbacks.'
| 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 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
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable Java code examples for Azure Communication Services authentication and identifiers, which is its primary strength. However, it suffers from being a monolithic reference document that could benefit from splitting into focused sub-files, and includes some verbose patterns (instanceof chains, basic identifier usage) that Claude can infer. The workflow guidance is implicit rather than explicitly sequenced with validation steps.
Suggestions
Split the content into a concise SKILL.md overview with quick-start credential creation, and move detailed sections (identifiers, Entra ID, cloud environments) into separate referenced files like IDENTIFIERS.md and ENTRA_AUTH.md.
Remove the 'Type Checking Identifiers' and 'Identifier Parsing' sections or condense them significantly—Claude knows how to do instanceof checks and string prefix matching in Java.
Add an explicit workflow for token refresh error handling: what happens when the refresher callback fails, how to detect it, and how to recover.
Remove the 'Trigger Phrases' and 'When to Use' boilerplate sections which add no actionable value to the skill content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary sections like 'Trigger Phrases' and 'When to Use' boilerplate, and the Type Checking Identifiers section is verbose with patterns Claude already knows (instanceof checks, casting). The identifier parsing section is also somewhat redundant given Claude's Java knowledge. | 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 complete client builder patterns. All code is copy-paste ready with clear imports. | 3 / 3 |
Workflow Clarity | While individual code snippets are clear, there's no explicit workflow sequence for common multi-step operations like setting up authentication end-to-end. The best practices section lists guidelines but lacks validation checkpoints or error recovery steps for token refresh failures. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with all details inline. At ~200+ lines, sections like identifier parsing, type checking, cloud environments, and Entra ID authentication could be split into separate reference files. There are no references to external files for advanced topics. | 1 / 3 |
Total | 8 / 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
33fc69f
- 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.