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 Java utilities) 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 performs (e.g., 'create token credentials', 'parse user identifiers'). Overall it is well-targeted and distinctive.
Suggestions
Replace the general 'common utilities' phrasing with specific actions like 'Creates CommunicationTokenCredential instances, parses user 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', 'resolve user 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
42%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, which is its primary strength. However, it is significantly over-long for a SKILL.md, reading more like comprehensive API documentation than a concise skill guide. It would benefit from aggressive trimming of patterns Claude already knows (instanceof checks, try-with-resources) and splitting reference material into separate files.
Suggestions
Reduce the content by at least 50%: remove the Type Checking Identifiers section, Identifier Parsing section, and Cloud Environments section (all standard patterns Claude can derive from the Key Concepts table), and trim the Dispose Credential section to a single line mentioning try-with-resources.
Split detailed identifier reference and Entra ID authentication into separate bundle files (e.g., IDENTIFIERS.md, ENTRA_AUTH.md) and reference them from the main skill.
Remove the 'Trigger Phrases', boilerplate 'When to Use', and 'Limitations' sections from the body content as they add no actionable value.
Add a brief error-handling workflow for token refresh failures, since it's listed as a best practice but never demonstrated.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is excessively verbose for its purpose. It explains basic patterns 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 full method examples. The 'Best Practices' section states obvious things like 'never log tokens.' Much of this is API reference documentation that bloats the context window. | 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. The common usage pattern at the end shows a complete, practical integration example. | 3 / 3 |
Workflow Clarity | The skill is primarily a reference/API guide rather than a multi-step workflow, but the credential lifecycle (create → use → dispose) is implicitly shown across scattered sections rather than as a clear sequence. There's no validation or error handling workflow for token refresh failures despite mentioning it in best practices. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files and no bundle files to support it. All API reference material, identifier details, cloud environments, and usage patterns are inlined in a single long document (~200+ lines) that would benefit greatly from being split into separate reference files. | 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
9e5d4dd
- 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.