azure-communication-callautomation-java
Build call automation workflows with Azure Communication Services Call Automation Java SDK. Use when implementing IVR systems, call routing, call recording, DTMF recognition, text-to-speech, or AI-...
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill azure-communication-callautomation-java91
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
100%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 well-crafted skill description that follows best practices. It specifies the exact technology stack (Azure Communication Services Call Automation Java SDK), lists concrete capabilities (IVR, call routing, recording, DTMF, TTS), and includes an explicit 'Use when' clause with natural trigger terms. The only minor issue is the truncation indicated by '...' which may hide additional context.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'IVR systems, call routing, call recording, DTMF recognition, text-to-speech, AI-...' - these are concrete, actionable capabilities even though truncated. | 3 / 3 |
Completeness | Clearly answers both what ('Build call automation workflows with Azure Communication Services Call Automation Java SDK') and when ('Use when implementing IVR systems, call routing, call recording, DTMF recognition, text-to-speech'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'call automation', 'IVR systems', 'call routing', 'call recording', 'DTMF', 'text-to-speech', 'Azure Communication Services' - good coverage of domain-specific terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche: Azure Communication Services + Java SDK + call automation. The combination of platform (Azure), SDK type (Java), and domain (call automation) creates a distinct trigger profile unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong SDK reference skill with excellent actionability and conciseness - all code examples are executable and the content respects Claude's intelligence. The main weakness is the lack of explicit workflow guidance for building complete IVR systems or call flows, and missing validation/error recovery patterns for multi-step operations.
Suggestions
Add a 'Building an IVR Flow' section showing the complete sequence: answer call → play prompt → recognize input → route based on result → handle errors, with explicit validation checkpoints
Include a workflow diagram or numbered sequence for the event-driven architecture showing how webhook events connect to subsequent actions
Consider splitting detailed event handling and recording workflows into separate reference files with clear navigation from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing executable code examples without explaining basic concepts Claude already knows. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | All code examples are complete, executable Java snippets with proper imports shown. The examples are copy-paste ready with clear parameter placeholders and cover the full range of SDK operations. | 3 / 3 |
Workflow Clarity | Individual operations are clear, but the skill lacks explicit workflow sequencing for multi-step processes like IVR flows. No validation checkpoints or feedback loops for error recovery in complex call scenarios. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers and a useful key concepts table, but it's a monolithic document. Complex topics like event handling or recording workflows could benefit from separate reference files. | 2 / 3 |
Total | 10 / 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.