azure-communication-chat-java
Build real-time chat applications with Azure Communication Services Chat Java SDK. Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time cha...
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill azure-communication-chat-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 clearly identifies the technology stack (Azure Communication Services Chat Java SDK), lists specific capabilities (chat threads, messaging, participants, read receipts, typing notifications), and includes an explicit 'Use when...' clause with relevant trigger terms. The description is concise, uses third person voice, and provides enough specificity to distinguish it from other chat or messaging skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'chat threads, messaging, participants, read receipts, typing notifications, real-time chat'. These are concrete, actionable capabilities within the Azure Communication Services domain. | 3 / 3 |
Completeness | Clearly answers both what ('Build real-time chat applications with Azure Communication Services Chat Java SDK') and when ('Use when implementing chat threads, messaging, participants, read receipts, typing notifications, or real-time chat'). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'chat applications', 'chat threads', 'messaging', 'participants', 'read receipts', 'typing notifications', 'real-time chat', plus the specific technology 'Azure Communication Services Chat Java SDK'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with specific technology stack (Azure Communication Services, Java SDK) and clear domain (chat/messaging). Unlikely to conflict with generic chat or other cloud provider skills due to explicit Azure and Java references. | 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 API reference skill with excellent actionability and conciseness - all code is executable and the content respects Claude's intelligence. The main weaknesses are the lack of an explicit end-to-end workflow showing how operations connect, and the monolithic structure that could benefit from progressive disclosure to separate quick-start content from advanced reference material.
Suggestions
Add a 'Quick Start Workflow' section showing the complete sequence: create client → create thread → verify success → add participants → send message → handle response
Split advanced topics (pagination, error handling, message types reference) into a separate REFERENCE.md file, keeping SKILL.md focused on core operations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing direct 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 and cover the full API surface from client creation through error handling. | 3 / 3 |
Workflow Clarity | While individual operations are clear, there's no explicit workflow sequence for building a complete chat application. Missing validation checkpoints for operations like verifying thread creation succeeded before sending messages. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear section headers and tables, but it's a monolithic document (~250 lines) that could benefit from splitting advanced topics (pagination, error handling) into 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.