azure-communication-callingserver-java
⚠️ DEPRECATED: This SDK has been renamed to Call Automation. For new projects, use azure-communication-callautomation instead. This skill is for maintaining legacy code only.
63
55%
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-callingserver-java/SKILL.mdQuality
Discovery
22%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 functions primarily as a deprecation notice rather than a skill description. It fails to communicate what the skill does, lists no concrete actions or capabilities, and lacks an explicit 'Use when...' clause. While it provides some useful context about the SDK rename, it would be very difficult for Claude to determine when to select this skill from a list of available options.
Suggestions
Add concrete actions describing what this skill does, e.g., 'Manages call routing, media operations, and call recording using the legacy Azure Communication Calling Server SDK.'
Add an explicit 'Use when...' clause, e.g., 'Use when maintaining legacy code that references azure-communication-callingserver or the old Calling Server SDK, not for new projects.'
Include natural trigger terms users might say, such as 'calling server', 'callingserver SDK', 'legacy call automation', 'azure communication calling'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description does not describe any concrete actions or capabilities. It only states the skill is deprecated and references a renamed SDK, without explaining what the skill actually does. | 1 / 3 |
Completeness | The 'what' is almost entirely missing—there is no explanation of what the skill does. The 'when' is weakly implied ('maintaining legacy code only') but there is no explicit 'Use when...' clause with proper trigger guidance. | 1 / 3 |
Trigger Term Quality | It includes some relevant keywords like 'Call Automation', 'azure-communication-callautomation', and 'legacy code', which could help match user queries about the old SDK. However, it lacks natural terms describing what the skill actually handles. | 2 / 3 |
Distinctiveness Conflict Risk | The mention of the specific SDK name 'azure-communication-callautomation' and the deprecation notice provide some distinctiveness, but without describing actual capabilities, it could overlap with or be confused for the newer Call Automation skill. | 2 / 3 |
Total | 6 / 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-structured deprecation/migration skill that efficiently communicates the old-to-new mapping with concrete, executable examples. Its main weakness is the lack of a sequenced migration workflow with validation steps, which would help Claude guide users through the actual migration process rather than just showing the before/after. The boilerplate 'When to Use' and 'Limitations' sections at the end add minimal value.
Suggestions
Add a numbered migration workflow with validation steps (e.g., 1. Update pom.xml dependency, 2. Find/replace imports, 3. Compile and fix errors, 4. Run tests to verify behavior).
Remove or condense the generic 'When to Use' and 'Limitations' boilerplate sections, which don't add skill-specific value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and focused on what matters: migration mappings, old vs new code, and clear deprecation warnings. No unnecessary explanations of what Azure Communication Services is or how SDKs work in general. | 3 / 3 |
Actionability | Provides fully executable code examples for both old and new client creation, concrete Maven dependency XML, and a clear class name mapping table. The migration path is copy-paste ready. | 3 / 3 |
Workflow Clarity | The migration path is presented as side-by-side comparisons rather than a sequenced workflow with validation steps. There's no explicit checklist for migration (e.g., find all usages, replace dependencies, update imports, verify compilation, test). For a migration task, explicit validation checkpoints would be valuable. | 2 / 3 |
Progressive Disclosure | The skill serves as a concise overview of the deprecated SDK with clear pointers to the replacement skill (`azure-communication-callautomation-java`) for new development. References are one level deep and well-signaled. Content is appropriately scoped to legacy maintenance and migration. | 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 | |
- 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.