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 strong in specificity and distinctiveness, clearly naming concrete features of a chat application domain. Its main weakness is the absence of an explicit 'Use when...' clause, which would help Claude know exactly when to select this skill. Adding natural trigger term variations would also improve discoverability.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks to build a chat app, implement messaging features, or add real-time communication to an application.'
Include additional natural trigger terms users might say, such as 'instant messaging', 'conversations', 'DMs', 'direct messages', 'chat rooms', or 'WebSocket'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions/features: 'thread management', 'messaging', 'participants', and 'read receipts'. These are concrete, well-defined capabilities within the chat application domain. | 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 dimension at 2 per the rubric. | 2 / 3 |
Trigger Term Quality | Includes some natural keywords like 'chat', 'messaging', 'real-time', 'thread', and 'read receipts', but misses common variations users might say such as 'instant messaging', 'conversations', 'chat rooms', 'DMs', 'direct messages', 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 such as general web development or messaging queue 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 comprehensive API reference for Azure Communication Chat in Java with strong actionability—all code examples are concrete and executable. However, it reads more like exhaustive documentation than a focused skill: it's overly long, lacks workflow sequencing with validation checkpoints, and dumps everything into a single monolithic file without progressive disclosure. The boilerplate sections (Trigger Phrases, When to Use, Limitations) 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, error handling, participant management, read receipts).
Add an explicit workflow sequence with validation steps, e.g., verify thread creation succeeded before proceeding to send messages, and check token validity before operations.
Remove the 'Trigger Phrases', 'When to Use', and 'Limitations' boilerplate sections as they consume tokens without adding actionable guidance.
Trim verbose print statements from examples and remove the Key Concepts table—Claude already understands these class-purpose mappings from the code examples themselves.
| 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, examples, and reference tables are inlined in a single file. Advanced topics like pagination, error handling, and async clients could be split into separate references. | 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
76aea27
- 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.