azure-communication-sms-java
Send SMS messages with Azure Communication Services SMS Java SDK. Use when implementing SMS notifications, alerts, OTP delivery, bulk messaging, or delivery reports.
85
82%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted skill description that clearly identifies the technology stack (Azure Communication Services SMS Java SDK), lists concrete use cases, and includes an explicit 'Use when' clause with natural trigger terms. It is concise, specific, and distinctive, making it easy for Claude to select appropriately from a large skill set.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: sending SMS messages, implementing notifications, alerts, OTP delivery, bulk messaging, and delivery reports. Also specifies the technology stack (Azure Communication Services SMS Java SDK). | 3 / 3 |
Completeness | Clearly answers both 'what' (send SMS messages with Azure Communication Services SMS Java SDK) and 'when' (explicit 'Use when' clause covering SMS notifications, alerts, OTP delivery, bulk messaging, or delivery reports). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'SMS', 'notifications', 'alerts', 'OTP delivery', 'bulk messaging', 'delivery reports', 'Azure Communication Services', 'Java SDK'. These cover common variations of how users would describe SMS-related tasks. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive due to the specific combination of Azure Communication Services, SMS, and Java SDK. Unlikely to conflict with other skills unless there are multiple Azure SMS skills; the technology stack and protocol specificity create a clear niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid API reference skill with excellent actionability—nearly all code examples are executable and cover the key use cases comprehensively. However, it's somewhat verbose with overlapping patterns shown in multiple sections, lacks a clear end-to-end workflow with validation steps, and includes unnecessary sections like 'Trigger Phrases' and 'When to Use' that waste tokens. The delivery report handler is notably pseudocode rather than real code.
Suggestions
Remove the 'Trigger Phrases' and 'When to Use' sections as they provide no actionable value to Claude.
Consolidate overlapping response handling code—the single send, multiple send, and response handling sections all demonstrate similar result-checking patterns that could be shown once.
Add a brief end-to-end workflow section at the top showing the sequence: create client → validate connection → send message → check result → handle delivery report, with explicit validation checkpoints.
Replace the delivery report pseudocode handler with an actual executable Event Grid webhook handler or remove it in favor of a reference link.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is mostly efficient with executable code examples, but includes some redundancy—multiple client creation patterns, response handling shown in several places with overlapping patterns, and the delivery report handler is essentially pseudocode with comments rather than real code. The 'Trigger Phrases' and 'When to Use' sections add no value for Claude. | 2 / 3 |
Actionability | The skill provides fully executable Java code for all major operations: client creation (multiple auth methods), single send, bulk send, async operations, error handling, and response processing. Code is copy-paste ready with concrete examples including phone number formats and option configuration. | 3 / 3 |
Workflow Clarity | The skill presents individual operations clearly but lacks a sequenced workflow tying them together (e.g., setup → send → verify → handle delivery reports). There are no explicit validation checkpoints—for instance, no guidance on verifying the client is properly authenticated before sending, or validating phone numbers before batch operations. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear section headers, but it's a monolithic document (~200 lines) that could benefit from splitting detailed sections (async operations, delivery reports, error handling) into separate reference files. The SmsSendResult properties table and environment variables are good inline content, but the overall length could be reduced with references. | 2 / 3 |
Total | 9 / 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
33fc69f
- 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.