sent-integration-starter
Build a Reliable Sent Integration
Messaging integrations can fail through duplicate sends, unsafe retries, weak webhook validation, or incorrect credential scope. This skill provides a staged Sent v3 implementation and launch review.
Instalar con mi Agente
Copia esta solicitud en tu Agente. Incluye la página canónica del Skill y el manifiesto.
Review the Skillstore skill "sent-integration-starter" from https://skillstore.io/skills/sentdm-sent-integration-starter.md and its manifest at https://skillstore.io/api/skills/sentdm-sent-integration-starter/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Tu Agente debe seguir mostrando su plan y solicitar cualquier confirmación exigida por la política de seguridad.
Recursos legibles por agentes
Usa estos enlaces cuando un agente de IA, crawler o script necesite contexto limpio en vez de leer la página completa.
Pruébalo
Usando "sent-integration-starter". Review a Python service that sends order confirmations and receives delivery events.
Resultado esperado:
- Use the asynchronous Python client with a server-managed environment credential.
- Derive one stable idempotency key from the order and notification type.
- Persist returned message identifiers before processing delivery events.
- Verify each webhook against the raw body and reject stale timestamps.
Usando "sent-integration-starter". Classify an authentication failure and a rate-limit response.
Resultado esperado:
Treat authentication failures as terminal and alert an operator. Honor the rate-limit delay, then retry with bounded jittered backoff.
Usando "sent-integration-starter". Assess a multi-tenant worker that stores customer keys inside queued jobs.
Resultado esperado:
Remove credentials from job payloads. Store a tenant reference and resolve the currently authorized credential from a secret store when the worker runs.
Auditoría de seguridad
SeguroAll 70 static alerts are false positives caused by documentation syntax, configuration examples, and fixed Python text. No prompt injection, secret exfiltration, shell execution, or unauthorized reconnaissance was found.
Factores de riesgo
🌐 Acceso a red (1)
🔑 Variables de entorno (9)
⚙️ Comandos externos (41)
Compartir y citar este informe
Comparte el informe de evaluación versionado, la insignia neutral, la tarjeta insertable y las citas. Skillstore presenta evidencias sin decidir si este Skill es seguro.
Copiar enlace del informe
https://skillstore.io/skills/sentdm-sent-integration-starter/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportInsignia Markdown
[](https://skillstore.io/skills/sentdm-sent-integration-starter?utm_source=security_passport_badge)Insignia HTML
<a href="https://skillstore.io/skills/sentdm-sent-integration-starter?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/sentdm-sent-integration-starter/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Tarjeta para insertar
<iframe src="https://skillstore.io/embed/skills/sentdm-sent-integration-starter.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citas académicas (APA · BibTeX · CFF)
Cita APA
sentdm. (2026). sent-integration-starter security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sentdm-sent-integration-starter/audits/1Cita BibTeX
@techreport{sentdm-sentdm-sent-integration-starter-2026,
author = {sentdm},
title = {sent-integration-starter security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/sentdm-sent-integration-starter/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-integration-starter security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "sentdm"
date-released: "2026-09-03"
url: "https://skillstore.io/skills/sentdm-sent-integration-starter/audits/1"
identifiers:
- type: other
value: "skillstore:sentdm-sent-integration-starter:audit:1"
description: "Skillstore immutable audit report identifier"
Puntuación de Skillstore
Por qué esta puntuación Confianza de la evidencia: MedioLo que puedes crear
Add Sent to a Service
Choose an SDK, configure credentials, design the client lifecycle, and prepare the first sandbox request.
Review Launch Readiness
Check idempotency, retries, rate limits, logging, webhook verification, and delivery tracking before production release.
Validate Multi-Tenant Isolation
Review credential scope, profile headers, client reuse, queue payloads, and tenant-to-message mappings.
Prueba estos prompts
Recommend the Sent SDK and client setup for my language, framework, and server deployment model.
Review my planned Sent message flow for payload shape, idempotency, retries, rate limits, and delivery tracking.
Define a Sent webhook receiver for my framework, including raw-body access, signature checks, replay protection, acknowledgment, deduplication, and background work.
Audit my Sent architecture for tenant credential isolation, profile scope, queue safety, message ownership, failure recovery, observability, and production launch risks.
Mejores prácticas
- Use a deterministic idempotency key for every mutating request and reuse it for retries.
- Keep credentials server-side, separate them by environment, and avoid logging secrets or message content.
- Verify webhook signatures against raw bytes, enforce timestamp limits, acknowledge quickly, and deduplicate events.
Evitar
- Do not use multiple explicit channels when you intend fallback because this broadcasts messages and increases charges.
- Do not retry authentication, validation, or missing-resource errors because repeated requests reproduce the failure.
- Do not treat an accepted response as proof of delivery because final status arrives through delivery events.
Preguntas frecuentes
Does this skill send messages?
Which languages are covered?
How should API keys be stored?
Why are idempotency keys required?
Does sandbox mode verify delivery?
What confirms final delivery?
Detalles del desarrollador
Autor
sentdmLicencia
MIT
Revisión de Skillstore
r1
Aviso de versión
El autor no declaró una versión.
Ref.
096c7daa4d0d974771dad12d81c3d0d4688617b9
Actualidad del mantenimiento
8/9/2026
Uso
1 descargas · 0 vistas
Estructura de archivos