azure-communication-callingserver-java
Azure Communication Services CallingServer (legacy) Java SDK. Note - This SDK is deprecated. Use azure-communication-callautomation instead for new projects. Only use this skill when maintaining le...
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill azure-communication-callingserver-java70
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
40%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 description is severely hampered by truncation and lacks any concrete capability descriptions. While it correctly identifies the deprecation status and points to the replacement SDK, it fails to explain what the skill actually does or provide complete trigger guidance for when to use it for legacy maintenance.
Suggestions
Complete the truncated description and add specific actions like 'manage legacy calling sessions', 'handle call events', or whatever concrete operations this SDK supports.
Add explicit trigger terms users might say when working with legacy code, such as 'CallingServer', 'legacy Azure calls', 'migrate from CallingServer', or specific class/method names.
Expand the 'Use when...' clause to fully specify scenarios like 'Use when maintaining legacy projects that use CallingServer SDK, or when migrating to callautomation SDK.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description is truncated and only mentions it's a 'Java SDK' without listing any concrete actions or capabilities. No specific operations like 'make calls', 'handle events', or 'manage sessions' are mentioned. | 1 / 3 |
Completeness | The 'when' is partially addressed with 'Only use this skill when maintaining le...' (truncated), and it clarifies deprecation status. However, the 'what' is extremely weak - no actual capabilities are described, only that it's a deprecated SDK. | 2 / 3 |
Trigger Term Quality | Contains some relevant keywords like 'Azure Communication Services', 'CallingServer', 'Java SDK', and 'azure-communication-callautomation', but the description is cut off and may be missing common user terms for when they'd need this legacy SDK. | 2 / 3 |
Distinctiveness Conflict Risk | The specific naming of 'CallingServer (legacy)' and distinction from 'azure-communication-callautomation' helps differentiate it, but the truncation and lack of specific use cases could cause confusion with the newer SDK or other Azure communication skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted deprecation/migration skill that efficiently communicates the essential information for maintaining legacy code. The side-by-side code comparisons and class mapping table are excellent. The main weakness is the lack of an explicit step-by-step migration workflow, which would help developers systematically update their codebases.
Suggestions
Add an explicit numbered migration workflow section (e.g., '1. Update dependency in pom.xml, 2. Find/replace imports, 3. Update client class names, 4. Update recording API calls, 5. Test')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, focusing only on migration-relevant information. No unnecessary explanations of what Azure Communication Services is or how SDKs work - it assumes Claude's competence and gets straight to the actionable differences. | 3 / 3 |
Actionability | Provides fully executable code examples for both old and new patterns, complete Maven dependency snippets, and a clear class name mapping table. All code is copy-paste ready with proper imports shown. | 3 / 3 |
Workflow Clarity | The migration path is implied through side-by-side comparisons rather than explicitly sequenced steps. For a migration skill, explicit steps like '1. Update pom.xml, 2. Replace imports, 3. Update class names, 4. Test' would improve clarity. | 2 / 3 |
Progressive Disclosure | Appropriately structured with clear sections and well-signaled references to the replacement skill (azure-communication-callautomation-java). Content is self-contained for legacy maintenance while directing new development elsewhere. | 3 / 3 |
Total | 11 / 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 | |
- 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.