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.
Mit meinem Agent installieren
Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.
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.Ihr Agent sollte weiterhin seinen Plan anzeigen und alle von der Sicherheitsrichtlinie verlangten Bestätigungen anfordern.
Agent-lesbare Ressourcen
Verwenden Sie diese Links, wenn ein KI-Agent, Crawler oder Skript sauberen Kontext benötigt, statt die vollständige Seite zu lesen.
Testen
„sent-integration-starter“ wird verwendet. Review a Python service that sends order confirmations and receives delivery events.
Erwartetes Ergebnis:
- 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.
„sent-integration-starter“ wird verwendet. Classify an authentication failure and a rate-limit response.
Erwartetes Ergebnis:
Treat authentication failures as terminal and alert an operator. Honor the rate-limit delay, then retry with bounded jittered backoff.
„sent-integration-starter“ wird verwendet. Assess a multi-tenant worker that stores customer keys inside queued jobs.
Erwartetes Ergebnis:
Remove credentials from job payloads. Store a tenant reference and resolve the currently authorized credential from a secret store when the worker runs.
Sicherheitsaudit
SicherAll 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.
Risikofaktoren
🌐 Netzwerkzugriff (1)
🔑 Umgebungsvariablen (9)
⚙️ Externe Befehle (41)
Diesen Bericht teilen & zitieren
Teile den versionierten Bewertungsbericht, das neutrale Badge, die Einbettungskarte und Zitate. Skillstore berichtet Nachweise, ohne zu entscheiden, ob dieser Skill sicher ist.
Berichtslink kopieren
https://skillstore.io/skills/sentdm-sent-integration-starter/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown-Badge
[](https://skillstore.io/skills/sentdm-sent-integration-starter?utm_source=security_passport_badge)HTML-Badge
<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>Einbettungskarte
<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>Wissenschaftliche Zitate (APA · BibTeX · CFF)
APA-Zitat
sentdm. (2026). sent-integration-starter security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/sentdm-sent-integration-starter/audits/1BibTeX-Zitat
@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"
Skillstore-Score
Warum dieser Score Evidenzvertrauen: MittelWas Sie erstellen können
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.
Diese Prompts ausprobieren
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.
Bewährte Praktiken
- 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.
Vermeiden
- 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.
Häufig gestellte Fragen
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?
Entwicklerdetails
Autor
sentdmLizenz
MIT
Skillstore-Revision
r1
Versionshinweis
Der Autor hat keine Version angegeben.
Ref.
096c7daa4d0d974771dad12d81c3d0d4688617b9
Aktualität der Wartung
8.9.2026
Nutzung
1 Downloads · 0 Aufrufe
Dateistruktur