azure-communication-chat-java
Build real-time chat applications with thread management, messaging, participants, and read receipts.
69
62%
Does it follow best practices?
Impact
Pending
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 chat application development. 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 benefit from more natural user-facing variations.
Suggestions
Add a 'Use when...' clause such as 'Use when the user asks to build a chat app, implement real-time messaging, add conversation threads, or integrate read receipts.'
Include additional natural trigger terms users might say, such as 'chat room', 'direct messages', 'DMs', 'conversations', 'WebSocket', or 'instant messaging'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions/features: 'thread management', 'messaging', 'participants', and 'read receipts'. These are concrete, identifiable capabilities within the chat application domain. | 3 / 3 |
Completeness | Clearly answers 'what' (build chat apps with thread management, messaging, participants, read receipts) 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 some natural keywords like 'chat applications', 'messaging', 'thread', and 'read receipts', but misses common variations users might say such as 'real-time messaging', 'chat app', 'conversations', 'DMs', 'direct messages', 'chat rooms', 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 is a thorough API reference for Azure Communication Chat in Java with excellent, executable code examples covering the full API surface. However, it reads more like SDK documentation than a skill—it lacks workflow sequencing with validation steps, and the sheer volume of inline content would benefit from progressive disclosure via separate reference files. Some sections (Trigger Phrases, When to Use, Limitations) are boilerplate that waste tokens.
Suggestions
Split the content into a concise SKILL.md overview (client setup, create thread, send message) with references to separate files for advanced topics (PAGINATION.md, ERROR_HANDLING.md, PARTICIPANTS.md).
Add an explicit end-to-end workflow with numbered steps and validation checkpoints, e.g., '1. Create client → 2. Create thread → 3. Verify thread ID is non-null → 4. Send message → 5. Confirm with getMessage()'.
Remove the 'Trigger Phrases', 'When to Use', and 'Limitations' boilerplate sections as they add no actionable value for Claude.
Trim the Key Concepts table and reduce println-heavy code examples to focus on the essential API calls rather than output formatting.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly comprehensive but includes some unnecessary verbosity—the Key Concepts table explains things Claude already knows, the 'Trigger Phrases' and 'When to Use' sections add little value, and some code examples include excessive println statements that pad the content without adding instructional value. | 2 / 3 |
Actionability | All code examples are fully executable Java with proper imports, concrete method calls, and realistic usage patterns. The examples cover the full API surface from client creation through messaging, participants, receipts, pagination, and error handling—all copy-paste ready. | 3 / 3 |
Workflow Clarity | The sections are logically ordered (client creation → thread creation → messaging → participants → receipts), but there's no explicit workflow sequence tying them together, no validation checkpoints, and no error recovery feedback loops for multi-step operations like creating a thread and adding participants. | 2 / 3 |
Progressive Disclosure | The content is a monolithic wall of text with all API operations inlined in a single file. For a skill this long (~250+ lines), advanced topics like pagination, error handling, and async client usage should be split into referenced files rather than all presented inline. | 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
76cbde3
- 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.