스킬 sent-integration-starter

📦

sent-integration-starter

Name: sent-integration-starter
Author: sentdm

콘텐츠 리비전 r1 안전 🌐 네트워크 접근🔑 환경 변수⚙️ 외부 명령어

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.

지원: Claude Codex Code(CC)

🥈 80 실버

Maintain this Skill? Claim it 🥈 80 실버

내 에이전트로 설치

이 요청을 에이전트에 복사하세요. 공식 Skill 페이지와 매니페스트가 포함되어 있습니다.

에이전트 요청

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.

에이전트는 계속해서 계획을 표시하고 보안 정책에서 요구하는 확인을 요청해야 합니다.

에이전트가 읽기 쉬운 리소스

AI 에이전트, 크롤러, 스크립트가 전체 페이지 대신 정리된 컨텍스트만 필요할 때 이 링크를 사용하세요.

Markdown 상세 GET /skills/sentdm-sent-integration-starter.md 서명된 manifest GET /api/skills/sentdm-sent-integration-starter/manifest 서명된 lockfile GET /api/skills/sentdm-sent-integration-starter/lockfile

테스트해 보기

"sent-integration-starter" 사용 중입니다. Review a Python service that sends order confirmations and receives delivery events.

예상 결과:

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" 사용 중입니다. Classify an authentication failure and a rate-limit response.

예상 결과:

Treat authentication failures as terminal and alert an operator. Honor the rate-limit delay, then retry with bounded jittered backoff.

"sent-integration-starter" 사용 중입니다. Assess a multi-tenant worker that stores customer keys inside queued jobs.

예상 결과:

Remove credentials from job payloads. Store a tenant reference and resolve the currently authorized credential from a secret store when the worker runs.

보안 감사

안전

v1 • 2026. 9. 3. 버전별 보고서 열기

All 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.

스캔된 파일

745

분석된 줄 수

검토 항목

오탐 무시됨

위험 요인

🌐 네트워크 접근 (1)

references/errors-and-limits.md:30

🔑 환경 변수 (9)

references/sdk-and-frameworks.md:35 references/sdk-and-frameworks.md:47 references/sdk-and-frameworks.md:64 references/sdk-and-frameworks.md:70 references/sdk-and-frameworks.md:76 references/sdk-and-frameworks.md:82 references/sdk-and-frameworks.md:92 references/sdk-and-frameworks.md:96 SKILL.md:24

⚙️ 외부 명령어 (41)

가장 최근에 완료된 정적·의미론적 감사에서 확인된 보안 발견 사항이 감지되지 않았습니다. 이는 스킬에 부작용이 없음을 증명하지 않습니다.

감사자: codex

이 보고서 공유 및 인용

버전이 지정된 평가 보고서, 중립 배지, 임베드 카드 및 인용을 공유하세요. Skillstore는 근거를 보고하지만 이 Skill의 안전 여부를 판단하지 않습니다.

버전별 보고서 열기

보고서 링크 복사

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

Markdown 배지

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

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>

임베드 카드

<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>

학술 인용 (APA · BibTeX · CFF)

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/1

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"

Skillstore 점수

이 점수의 이유 증거 신뢰도: 중간

아키텍처

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

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.

이 프롬프트를 사용해 보세요

Choose an SDK

Recommend the Sent SDK and client setup for my language, framework, and server deployment model.

Review a Send Design

Review my planned Sent message flow for payload shape, idempotency, retries, rate limits, and delivery tracking.

Design a Verified Receiver

Define a Sent webhook receiver for my framework, including raw-body access, signature checks, replay protection, acknowledgment, deduplication, and background work.

Audit a Multi-Tenant Integration

Audit my Sent architecture for tenant credential isolation, profile scope, queue safety, message ownership, failure recovery, observability, and production launch risks.

모범 사례

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.

피하기

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.