CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

50

Quality

55%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

Quality

Content

61%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body delivers concrete, executable migration guidance with a useful class-mapping table and code samples, but it reads as a reference sheet rather than a sequenced migration workflow and carries some repeated deprecation wording plus generic boilerplate sections.

Suggestions

Convert the migration into a numbered workflow with a validation checkpoint (e.g., after swapping dependencies and class names, compile and confirm no com.azure.communication.callingserver imports remain).

Collapse the repeated deprecation warnings into a single prominent banner and remove the generic 'When to Use'/'Limitations' boilerplate that adds no migration-specific value.

Either inline a minimal Call Automation recording example or link to the specific section of the callautomation skill rather than a bare 'see the skill' pointer.

DimensionReasoningScore

Conciseness

The body is mostly efficient with copy-paste Maven and Java snippets, but the deprecation warning is repeated across the header and 'For New Development' section, and the generic 'When to Use'/'Limitations' boilerplate could be trimmed.

3 / 5

Actionability

It provides executable Maven dependency blocks, import statements, and Java client/recording code plus a concrete class-name mapping table; the only gap is the recording 'NEW WAY' pointing to another skill instead of showing code.

4 / 5

Workflow Clarity

Migration is presented as parallel OLD/NEW comparisons and a class-change table rather than a sequenced workflow, and there are no validation checkpoints to confirm a migration is complete and correct.

3 / 5

Progressive Disclosure

Content is organized into clear, well-labeled sections (Migration, Class Name Changes, Legacy Client Creation, Legacy Recording, For New Development) with a signaled pointer to the callautomation skill; no bundle files exist, so structure alone is assessed.

4 / 5

Total

14

/

20

Passed

Description

48%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is an effective deprecation notice that clearly redirects users, but it functions more as a warning than a capability description, lacking concrete actions and an explicit 'Use when' trigger clause.

Suggestions

Add an explicit 'Use when...' clause with natural trigger phrases (e.g., 'Use when maintaining code that imports com.azure.communication.callingserver or migrating it to Call Automation').

Name concrete actions the skill supports (e.g., 'Migrates CallingServer clients, recording calls, and class references to the Call Automation SDK') to raise specificity.

Include common synonyms/extensions users might say ('callingserver', 'deprecated calling SDK', 'Call Automation migration') alongside the existing keywords.

DimensionReasoningScore

Specificity

The description names the domain ('Call Automation', 'legacy code') but offers no concrete actions the skill performs — it is a deprecation pointer rather than a capability list, matching 'names the domain but actions are minimal or generic'.

2 / 5

Completeness

It conveys a 'what' (maintaining legacy CallingServer code) and a weak 'when' (legacy only), but contains no explicit 'Use when...' clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

It surfaces relevant keywords users would say ('DEPRECATED', 'legacy', 'Call Automation') but lacks common variations or synonyms and has no explicit trigger phrase, fitting 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

It targets a narrow, deprecated SDK and explicitly redirects new work elsewhere, leaving only minor overlap risk with the closely related callautomation skill.

4 / 5

Total

12

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
sickn33/antigravity-awesome-skills
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.