azure-communication-chat-java

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

Quality

67%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azure-communication-chat-java/SKILL.md

Quality

Content

72%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 with comprehensive executable Java examples, but it is a monolithic reference with no progressive disclosure and lacks validation checkpoints around destructive operations.

Suggestions

Add validation/confirmation checkpoints (e.g. verify thread exists, confirm before delete) and a validate->fix->retry loop for destructive operations like deleteChatThread and removeParticipant.

Split the bulk reference (message types, full error handling, pagination details) into referenced files under references/ and link to them from a concise overview.

Remove the filler 'When to Use' line and trim redundancy between the Get Messages and Pagination sections to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean executable code with minimal padding and assumes Java competence, but the filler 'When to Use' line and minor redundancy between the Get Messages and Pagination sections keep it just short of the fully lean anchor 5.	4 / 5
Actionability	It provides fully executable, copy-paste-ready Java examples across the common cases (client creation, threads, messages, participants, receipts, typing, pagination, error handling), matching the 'fully executable; covers common cases' anchor.	5 / 5
Workflow Clarity	Sections are logically sequenced (install -> client -> thread -> operations), but destructive operations like deleteChatThread, deleteMessage, and removeParticipant have no validation feedback loops, so per the scoring notes workflow clarity is capped at 3.	3 / 5
Progressive Disclosure	The ~300-line body is a monolithic inline reference with no bundle files and no one-level-deep links to detail materials, fitting the 'some structure but content that should be separate is inline' anchor despite clear section headers.	3 / 5
	Total	15 / 20 Passed

Description

62%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 is specific and keyword-rich about chat capabilities but lacks an explicit 'when to use' trigger clause and does not name the Azure provider, weakening completeness and distinctiveness.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when building chat or real-time messaging in Java with Azure Communication Services.'

Mention Azure Communication Services in the description to reduce overlap risk with generic chat skills.

Include common synonyms like 'instant messaging' or 'live chat' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	The phrase 'thread management, messaging, participants, and read receipts' lists several concrete capabilities, matching the 'lists several specific actions; minor gaps' anchor rather than the 1-2 actions of a 3 or the fully comprehensive coverage of a 5.	4 / 5
Completeness	The description gives a clear 'what' but contains no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural terms like 'real-time chat applications', 'messaging', and 'read receipts' give good keyword coverage, though synonyms such as 'instant messaging' or 'live chat' are missing, fitting the 'good coverage, a few natural terms missing' anchor.	4 / 5
Distinctiveness Conflict Risk	The chat domain and capability list are somewhat specific, but the description omits the Azure provider name, so it could overlap with other chat/messaging skills, fitting the 'somewhat specific but could still overlap' anchor.	3 / 5
	Total	14 / 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/azure-communication-chat-java/SKILL.md
Commit: 57c135b

Reviewed: 6 days 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.