Skills azure-communication-sms-java
📦

azure-communication-sms-java

Content revision r2 Medium Risk ⚙️ External commands🌐 Network access

Build Azure SMS Workflows in Java

Java teams need reliable patterns for Azure SMS delivery and result handling. This skill provides focused examples for synchronous, asynchronous, and bulk messaging.

Supports: Claude Codex Code(CC)
📊 69 Adequate

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "azure-communication-sms-java" from https://skillstore.io/skills/sickn33-azure-communication-sms-java.md and its manifest at https://skillstore.io/api/skills/sickn33-azure-communication-sms-java/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Your Agent should still show its plan and request any confirmation required by the security policy.

Agent-readable resources

Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.

Markdown detail GET /skills/sickn33-azure-communication-sms-java.md Signed manifest GET /api/skills/sickn33-azure-communication-sms-java/manifest Signed lockfile GET /api/skills/sickn33-azure-communication-sms-java/lockfile

Test it

Using "azure-communication-sms-java". Create a single-recipient order confirmation flow.

Expected outcome:

A Java implementation outline using DefaultAzureCredential, E.164 placeholders, delivery reporting, and redacted success or failure logging.

Using "azure-communication-sms-java". Plan a bulk appointment reminder service.

Expected outcome:

  • Configure the asynchronous SMS client.
  • Batch approved E.164 recipients.
  • Apply a correlation tag.
  • Inspect every recipient result.
  • Retry rate limits with bounded backoff.

Using "azure-communication-sms-java". Explain delivery report processing.

Expected outcome:

A workflow connecting message identifiers to validated Event Grid events while recording delivery status and protecting recipient data.

Security Audit

Medium Risk
v5 • 7/23/2026 Open versioned report

All 37 static findings are false positives caused by Markdown formatting, Azure endpoint placeholders, and ordinary Java examples. Semantic review found PII logging guidance and an incomplete webhook validation example.

1
Files scanned
285
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (2)

Medium
SKILL.md:67SKILL.md:104-106SKILL.md:214
Recipient Data Exposed in Logs
The examples print recipient phone numbers and provider error details, which can expose personal data in production logs.
The cited statements directly concatenate result.getTo() into console output. Phone numbers are personal data and production logs often have broad retention and access.
Medium
SKILL.md:225-241
Delivery Webhook Validation Is Not Demonstrated
The delivery report example accepts a raw Event Grid payload without demonstrating subscription validation, endpoint authentication, or event schema checks.
The handler accepts eventJson and only contains a parsing placeholder. The surrounding guidance does not mention validating Event Grid requests before trusting delivery status.

Risk Factors

⚙️ External commands (27)
SKILL.md:15-21 SKILL.md:21-25 SKILL.md:25-53 SKILL.md:53-57 SKILL.md:57-74 SKILL.md:74-78 SKILL.md:78-109 SKILL.md:109-113 SKILL.md:113-121 SKILL.md:121-125 SKILL.md:125-150 SKILL.md:150-154 SKILL.md:154-182 SKILL.md:182-186 SKILL.md:186-221 SKILL.md:221-227 SKILL.md:227-242 SKILL.md:242-248 SKILL.md:248-249 SKILL.md:249-250 SKILL.md:250-251 SKILL.md:251-252 SKILL.md:252-253 SKILL.md:253-257 SKILL.md:257-261 SKILL.md:261-265 SKILL.md:265-268
🌐 Network access (4)
SKILL.md:32 SKILL.md:45 SKILL.md:258 SKILL.md:259
Audited by: codex View Audit History →
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/sickn33-azure-communication-sms-java/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sickn33-azure-communication-sms-java/security.svg)](https://skillstore.io/skills/sickn33-azure-communication-sms-java?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sickn33-azure-communication-sms-java?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sickn33-azure-communication-sms-java/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sickn33-azure-communication-sms-java.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA · BibTeX · CFF)

APA citation

sickn33. (2026). azure-communication-sms-java security audit report (audit version 5) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sickn33-azure-communication-sms-java/audits/5

BibTeX citation

@techreport{sickn33-sickn33-azure-communication-sms-java-2026, author = {sickn33}, title = {azure-communication-sms-java security audit report (audit version 5)}, institution = {Skillstore}, year = {2026}, number = {5}, url = {https://skillstore.io/skills/sickn33-azure-communication-sms-java/audits/5}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "azure-communication-sms-java security audit report (audit version 5)" version: "unspecified" type: report authors: - name: "sickn33" date-released: "2026-07-23" url: "https://skillstore.io/skills/sickn33-azure-communication-sms-java/audits/5" identifiers: - type: other value: "skillstore:sickn33-azure-communication-sms-java:audit:5" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
85
Maintainability
87
Content
69
Community
83
Spec Compliance

What You Can Build

Add Transactional Notifications

Create Java SMS notifications for orders, appointments, or service alerts with per-recipient result checks.

Implement OTP Delivery

Design an SMS send flow with delivery reporting, error handling, and Azure credentials.

Operate Bulk Messaging

Send approved messages to multiple recipients and correlate outcomes with campaign tags.

Try These Prompts

Create a Basic SMS Sender 
Show a minimal Java example that sends one Azure Communication Services SMS using DefaultAzureCredential and placeholders for the endpoint and phone numbers.
Add Result Handling 
Extend my Java SMS sender to check SmsSendResult, redact recipient data in logs, and handle request-level failures.
Build an Asynchronous Batch Flow 
Create an asynchronous Java flow for multiple recipients with delivery reports, tags, rate-limit handling, and bounded retries.
Design a Production SMS Integration 
Review my Azure SMS architecture for credential security, consent, idempotency, observability, Event Grid validation, retries, and per-recipient failure handling.

Best Practices

  • Prefer DefaultAzureCredential and keep connection strings outside source control.
  • Use E.164 numbers, verify consent, and check every recipient result.
  • Redact personal data, validate Event Grid requests, and use bounded retries for rate limits.

Avoid

  • Do not hardcode real access keys, connection strings, or production phone numbers.
  • Do not log complete recipient numbers, response headers, or unsanitized provider errors.
  • Do not send bulk messages without consent, opt-out handling, and regional compliance review.

Frequently Asked Questions

Which Azure Java package does this skill use?
It uses the azure-communication-sms package and demonstrates version 1.2.0 in the Maven dependency.
Which authentication methods are shown?
The examples show DefaultAzureCredential, a connection string, and AzureKeyCredential.
Can it send to multiple recipients?
Yes. It demonstrates recipient lists, per-recipient results, delivery reports, and tracking tags.
Does it support asynchronous sending?
Yes. It shows SmsAsyncClient with Reactor subscriptions for single and multiple recipients.
Does it fully implement delivery webhooks?
No. It outlines Event Grid delivery data but leaves payload parsing and request validation to the application.
What must I provide before using the examples?
Provide an Azure Communication Services resource, valid credentials, an SMS-enabled sender number, recipients, and required messaging consent.

Developer Details

Author

sickn33

License

MIT

Skillstore revision

r2

Version notice

The author did not declare a version.

Repository

https://github.com/sickn33/antigravity-awesome-skills/tree/main/skills/azure-communication-sms-java

Ref

f9e2c34b4f19c7f3e6b0a1e93227b5f77cc12526

Maintenance freshness

7/26/2026

Usage

7 downloads · 151 views

File structure

📄 SKILL.md