azure-communication-chat-java
Build real-time chat applications with thread management, messaging, participants, and read receipts.
55
62%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/azure-communication-chat-java/SKILL.mdQuality
Discovery
67%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 reasonably specific about what the skill does, listing concrete features of a chat application. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. The trigger terms are decent but could include more natural user language variations.
Suggestions
Add a 'Use when...' clause such as 'Use when the user wants to build a chat feature, messaging system, real-time conversations, or asks about threads, DMs, or read receipts.'
Include additional natural trigger terms users might say, such as 'instant messaging', 'chat feature', 'conversation threads', 'WebSocket chat', or 'DMs'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'thread management, messaging, participants, and read receipts' clearly describes the capabilities of the skill. | 3 / 3 |
Completeness | Clearly answers 'what does this do' (build real-time chat applications with specific features), but lacks an explicit 'Use when...' clause or equivalent trigger guidance, which caps this at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes relevant terms like 'chat applications', 'thread management', 'messaging', 'read receipts', but misses common user variations like 'chat app', 'real-time messaging', 'conversation threads', 'DMs', 'instant messaging', or 'WebSocket'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of 'real-time chat applications' with specific features like 'thread management', 'participants', and 'read receipts' creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides comprehensive, actionable Java code examples for Azure Communication Chat covering all major operations. However, it suffers from being a monolithic reference document with no progressive disclosure or workflow structure—it reads more like API documentation than a task-oriented skill. It could be significantly improved by splitting into a concise overview with references to detailed files, and by adding explicit workflow sequences with validation steps.
Suggestions
Split the content into a concise SKILL.md overview (client setup + basic send/receive) with references to separate files like PARTICIPANTS.md, RECEIPTS.md, and API_REFERENCE.md for detailed operations.
Add an explicit end-to-end workflow with validation checkpoints, e.g.: 1. Create client → verify connection, 2. Create thread → confirm threadId returned, 3. Send message → verify sendResult, 4. Handle errors at each step.
Remove the 'Trigger Phrases', 'When to Use', and 'Limitations' boilerplate sections as they waste tokens without adding actionable guidance.
Trim the Key Concepts table and verbose print statements in examples—Claude already understands these patterns and can infer them.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with executable code examples, but includes some unnecessary sections like 'Trigger Phrases', 'When to Use', and 'Limitations' boilerplate that add no value. The Key Concepts table explains things Claude already knows. The overall length (~200+ lines) could be tightened—e.g., the print statements in examples are verbose padding. | 2 / 3 |
Actionability | All code examples are concrete, executable Java with proper imports, specific class names, and method calls. The examples cover the full lifecycle (create thread, send/get/update/delete messages, manage participants, read receipts, error handling) and are copy-paste ready. | 3 / 3 |
Workflow Clarity | The sections are logically ordered (client creation → thread creation → messaging → participants → receipts), but there's no explicit multi-step workflow with validation checkpoints. For a chat application involving token management and thread lifecycle, there are no feedback loops or verification steps (e.g., confirming thread creation succeeded before sending messages). | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with no references to external files and no layered structure. All API details are inline in a single file with no separation between quick-start essentials and advanced/reference material. Given the length and breadth of topics, this would benefit significantly from splitting into overview + reference files. | 1 / 3 |
Total | 8 / 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
9e5d4dd
- 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.