📦

sent

Name: sent
Author: sentdm

Content revision r1 Safe ⚙️ External commands🌐 Network access

Route Sent Messaging Requests

Broad Sent requests can involve several channels, operations, and compliance workflows. This skill clarifies intent and routes each request to the appropriate specialist.

Supports: Claude Codex Code(CC)

📊 74 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 "sent" from https://skillstore.io/skills/sentdm-sent.md and its manifest at https://skillstore.io/api/skills/sentdm-sent/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/sentdm-sent.md Signed manifest GET /api/skills/sentdm-sent/manifest Signed lockfile GET /api/skills/sentdm-sent/lockfile

Test it

Using "sent". I want to use Sent for customer messaging.

Expected outcome:

Which channel do you plan to use: SMS, WhatsApp, RCS, or are you still deciding?

Using "sent". Our WhatsApp template was rejected by Meta.

Expected outcome:

This belongs in the WhatsApp template authoring workflow. Provide the rejection reason and current template text for review.

Using "sent". Check readiness, find my template, and send a test message.

Expected outcome:

First verify account readiness. Then locate the template, preview the message, and request confirmation before sending.

Security Audit

Safe

v1 • 9/2/2026 Open versioned report

All 26 command findings are Markdown inline-code references, not executable shell syntax. The two network findings are repeated links to public Sent documentation and do not initiate requests.

Files scanned

121

Lines analyzed

Review items

False positives ignored

Risk Factors

⚙️ External commands (26)

🌐 Network access (2)

SKILL.md:26 SKILL.md:85

No confirmed security findings were detected by the latest completed static and semantic audit. This does not prove the skill has no side effects.

Audited by: codex

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

Copy report link

https://skillstore.io/skills/sentdm-sent/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/sentdm-sent/security.svg)](https://skillstore.io/skills/sentdm-sent?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/sentdm-sent?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sentdm-sent/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/sentdm-sent.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

sentdm. (2026). sent security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sentdm-sent/audits/1

BibTeX citation

@techreport{sentdm-sentdm-sent-2026,
  author = {sentdm},
  title = {sent security audit report (audit version 1)},
  institution = {Skillstore},
  year = {2026},
  number = {1},
  url = {https://skillstore.io/skills/sentdm-sent/audits/1},
  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: "sent security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
  - name: "sentdm"
date-released: "2026-09-02"
url: "https://skillstore.io/skills/sentdm-sent/audits/1"
identifiers:
  - type: other
    value: "skillstore:sentdm-sent:audit:1"
    description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: Medium

Architecture

Maintainability

Content

Community

Spec Compliance

What You Can Build

Choose a Messaging Setup Path

Clarify channel, geography, and workflow stage before selecting an onboarding or integration skill.

Route a Delivery Problem

Separate account readiness, registration, template rejection, routing, and delivery-analysis issues.

Plan a Sent Integration

Select integration, webhook, Sender Profile, two-way messaging, or migration guidance based on the system scope.

Try These Prompts

Start With Sent

Help me start using Sent. Ask one question at a time and route me to the appropriate workflow.

Diagnose Messaging

My Sent messaging is not working. Identify the channel, symptom, and available evidence, then select the correct diagnostic skill.

Plan Multiple Workflows

I need account setup, templates, and a live send. Order the required Sent workflows and begin with the prerequisite.

Route a Platform Integration

We are building a multi-tenant messaging platform with webhooks and Sender Profiles. Clarify boundaries, then route each implementation stage.

Best Practices

Provide the channel, geography, workflow stage, and desired outcome when known.
Share relevant identifiers or error details only after confirming they contain no sensitive data.
Complete prerequisite checks before requesting live messaging operations.

Avoid

Do not use the router when one specialist workflow is already clear.
Do not force a Sent route for generic engineering questions.
Do not request live mutations before account readiness and user intent are confirmed.