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.

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-communication-callingserver-java/SKILL.md

Quality

Content

87%Scale 1-3

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 what changed, provides concrete old-vs-new mappings, and clearly directs users to the replacement SDK. Its main weakness is the lack of an explicit step-by-step migration workflow with validation checkpoints, which would help developers systematically migrate their codebase. The boilerplate 'When to Use' and 'Limitations' sections at the end add minimal value.

Suggestions

Add an explicit numbered migration workflow (e.g., 1. Update pom.xml dependency → 2. Replace imports → 3. Update class references → 4. Compile and verify) to improve workflow clarity.

Remove the generic 'When to Use' and 'Limitations' boilerplate sections, which add no skill-specific value and waste tokens.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It focuses on migration mapping (old vs new), provides concrete dependency coordinates and class name changes without explaining what Azure Communication Services is or how SDKs work. Every section earns its place for someone maintaining legacy code.	3 / 3
Actionability	Provides fully executable Maven dependency snippets, concrete class name mapping table, and copy-paste ready Java code for both old and new client creation patterns. The migration path is immediately actionable.	3 / 3
Workflow Clarity	The migration workflow is implicit rather than explicitly sequenced — the skill shows old vs new side-by-side but doesn't provide a step-by-step migration process (e.g., 1. Update pom.xml, 2. Replace imports, 3. Update class names, 4. Verify compilation). For a migration skill, an explicit checklist with validation would be stronger.	2 / 3
Progressive Disclosure	The skill is appropriately scoped as a concise overview with clear one-level-deep references to the `azure-communication-callautomation-java` skill for new development. Content is well-organized into logical sections (migration deps, class changes, legacy code, new direction) without being monolithic.	3 / 3
	Total	11 / 12 Passed

Description

22%Scale 1-3

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 as a deprecation notice rather than a proper skill description. It fails to explain what the skill actually does, lists no concrete actions or capabilities, and provides only a weak implicit trigger ('maintaining legacy code only'). While the specific SDK names provide some distinctiveness, the description is fundamentally inadequate for helping Claude select this skill appropriately.

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 with trigger terms, e.g., 'Use when the user references azure-communication-callingserver, the legacy calling server SDK, or needs to maintain pre-migration call automation code.'

Clarify the boundary between this skill and the replacement Call Automation skill so Claude can distinguish when to use each one.

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's no explanation of what the skill does. The 'when' is weakly implied ('for maintaining legacy code only') but lacks explicit trigger guidance. The description functions more as a deprecation notice than a skill description.	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 this specific 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 context provides some distinctiveness, but the lack of concrete capability descriptions means it could still overlap with the replacement skill or other Azure communication skills.	2 / 3
	Total	6 / 12 Passed

Validation

90%

Warnings & errors only

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: popey/claude-code-skills
Path: skills/azure-communication-callingserver-java/SKILL.md
Commit: a5a6601

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.