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.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill azure-communication-sms-java87
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%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 solid skill description with excellent trigger terms and completeness. The explicit 'Use when...' clause with specific scenarios (OTP, bulk messaging, delivery reports) makes selection criteria clear. The main weakness is that specificity could be improved by listing more concrete actions the skill can perform beyond just 'send'.
Suggestions
Expand the capabilities list with more specific actions like 'send single or bulk SMS, track delivery status, handle send failures, format international numbers'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Azure Communication Services SMS Java SDK) and the primary action (Send SMS messages), but doesn't list multiple concrete actions beyond 'send'. The use cases mentioned (notifications, alerts, OTP, bulk messaging, delivery reports) hint at capabilities but aren't described as specific actions the skill performs. | 2 / 3 |
Completeness | Clearly answers both what ('Send SMS messages with Azure Communication Services SMS Java SDK') and when ('Use when implementing SMS notifications, alerts, OTP delivery, bulk messaging, or delivery reports'). Has explicit 'Use when...' clause with specific trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'SMS', 'notifications', 'alerts', 'OTP delivery', 'bulk messaging', 'delivery reports', plus the specific technology 'Azure Communication Services'. Good coverage of common variations and use cases. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with clear niche: specifically Azure Communication Services + SMS + Java SDK. Unlikely to conflict with other messaging skills (e.g., Twilio, email, push notifications) due to explicit technology stack and protocol specification. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a strong, actionable skill with excellent code examples covering the full Azure Communication SMS Java SDK surface area. The content is concise and assumes Claude's competence. Minor improvements could include explicit workflow sequences for common scenarios and better progressive disclosure through linked reference files for advanced topics.
Suggestions
Add an explicit workflow sequence for common use cases (e.g., OTP delivery with retry logic on rate limiting)
Include a feedback loop example showing retry with exponential backoff for 429 responses, not just detection
Consider splitting delivery reports and async operations into separate reference files with clear links from the main skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing executable code examples without explaining basic concepts Claude already knows. Every section serves a clear purpose with no padding or unnecessary explanations. | 3 / 3 |
Actionability | All code examples are fully executable and copy-paste ready with proper imports. The skill covers multiple authentication methods, sync/async patterns, error handling, and bulk operations with complete, working code. | 3 / 3 |
Workflow Clarity | While individual operations are clear, there's no explicit workflow sequence for common use cases like OTP delivery or bulk messaging. The error handling section shows checking results but lacks a complete validate-retry feedback loop for rate limiting scenarios. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but it's a monolithic file that could benefit from splitting detailed topics (async operations, delivery reports) into separate reference files. The delivery reports section mentions Event Grid but doesn't link to further documentation. | 2 / 3 |
Total | 10 / 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 | |
- 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.