azure-communication-chat-java

Build real-time chat applications with thread management, messaging, participants, and read receipts.

Quality

60%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./skills/azure-communication-chat-java/SKILL.md

Quality

Content

65%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is highly actionable and reasonably concise, with strong executable Java examples, but it is a monolithic inline reference with no progressive disclosure and lacks validation checkpoints around its destructive operations.

Suggestions

Move the bulk API reference (e.g. full message/participant/receipt method details) into a separate REFERENCES.md and link to it one level deep, keeping SKILL.md as a concise overview.

Add a validation checkpoint before destructive calls — e.g. confirm the threadId/messageId and verify the participant exists before deleteChatThread/deleteMessage/removeParticipant, with a retry-on-failure note.

Trim the generic "When to Use" and "Limitations" boilerplate or fold them into a single concise usage note to recover tokens.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code blocks with minimal prose and does not explain concepts Claude already knows; a few inline comments and the boilerplate "When to Use"/"Limitations" sections could be trimmed, keeping it just short of fully lean.	4 / 5
Actionability	It provides concrete, copy-paste-ready Java for client creation, threads, messages, participants, receipts, typing, pagination, and error handling across the common cases, with only minor gaps (e.g. token refresh is named but not shown).	4 / 5
Workflow Clarity	The skill is organized as discrete API operations rather than a sequenced workflow, and destructive actions (deleteChatThread, deleteMessage, removeParticipant) are shown without any validate-before-proceeding checkpoint, so the rubric's destructive-operations cap holds it at 3.	3 / 5
Progressive Disclosure	Section headers give clear structure, but the entire API reference lives inline in a single ~310-line SKILL.md with no bundle files or one-level-deep references to split out the bulk reference material, matching the "good structure but content that should be separate is inline" anchor.	3 / 5
	Total	14 / 20 Passed

Description

55%Weight 40%Scale 1-5

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 states concrete capabilities but lacks a "Use when" trigger clause and omits the Azure/Java qualifiers that would distinguish it, so it lands at mid-range on completeness, triggers, and distinctiveness.

Suggestions

Add an explicit "Use when..." clause naming the natural triggers, e.g. "Use when building Java chat apps on Azure Communication Services, or when the user mentions ACS chat, chat threads, or read receipts in Java."

Include "Azure Communication Services" and "Java" in the description so it is distinguishable from generic chat skills.

Optionally add "typing notifications" to the capability list for fuller coverage of what the body teaches.

Dimension	Reasoning	Score
Specificity	Names the domain (real-time chat applications) and several concrete capability areas — "thread management, messaging, participants, and read receipts" — but omits other operations present in the body such as typing notifications and pagination, leaving minor coverage gaps.	4 / 5
Completeness	It clearly answers "what" the skill does, but provides no "Use when..." clause or equivalent trigger guidance; per the rubric a missing Use-when clause caps completeness at 3.	3 / 5
Trigger Term Quality	Phrases like "real-time chat", "messaging", and "read receipts" are reasonably natural, but the description never mentions "Azure Communication Services", "ACS", or "Java", the terms a user would most likely say when needing this specific skill.	3 / 5
Distinctiveness Conflict Risk	The chat/thread/participant framing is somewhat specific, but without naming Azure Communication Services or Java it could overlap with other general chat or messaging skills, so conflict risk remains moderate.	3 / 5
	Total	13 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/antigravity-awesome-skills
Path: skills/azure-communication-chat-java/SKILL.md
Commit: 1f67c44

Reviewed: about 15 hours ago

Table of Contents

Discovery Implementation Validation

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.