cooper-idempotent-sends
Prevent Duplicate Cooper Email Sends
Timeouts and retried jobs can send duplicate emails or create duplicate resources. This skill guides Cooper Email key selection and recovery checks for repeatable operations.
Installer avec mon Agent
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
Review the Skillstore skill "cooper-idempotent-sends" from https://skillstore.io/skills/cooper-email-cooper-idempotent-sends.md and its manifest at https://skillstore.io/api/skills/cooper-email-cooper-idempotent-sends/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Ressources lisibles par les agents
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Tester
Utilisation de « cooper-idempotent-sends ». Which key should a Cooper Email task reply use?
RĂ©sultat attendu:
- Use idempotency_key with cooper_reply_task.
- Derive the key from the task and intended reply, then reuse it for retries of that operation.
- Without the key, two calls can send two emails.
Utilisation de « cooper-idempotent-sends ». A Cooper Email send timed out. Should I retry with a new key?
RĂ©sultat attendu:
- Do not generate a new key merely because the first call timed out.
- Retry the same request with its original key, or check outbound messages using cooper_list_messages.
- If the request is still in progress, wait before retrying with the same key.
Utilisation de « cooper-idempotent-sends ». Cooper Email returned an idempotency key conflict.
RĂ©sultat attendu:
- The key was previously used with a different request.
- Determine what was sent before taking further action.
- Do not change the key simply to force another send.
Audit de sécurité
SûrAll 18 static findings are false positives: Markdown code spans, a homepage URL, and ordinary retry guidance. No evidence found of command execution, reconnaissance, credential theft, or prompt injection. This documentation guides Cooper Email writes but includes no executable implementation.
Facteurs de risque
âïž Commandes externes (16)
đ AccĂšs rĂ©seau (1)
Partager et citer ce rapport
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
Copier le lien du rapport
https://skillstore.io/skills/cooper-email-cooper-idempotent-sends/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportBadge Markdown
[](https://skillstore.io/skills/cooper-email-cooper-idempotent-sends?utm_source=security_passport_badge)Badge HTML
<a href="https://skillstore.io/skills/cooper-email-cooper-idempotent-sends?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cooper-email-cooper-idempotent-sends/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Carte intégrable
<iframe src="https://skillstore.io/embed/skills/cooper-email-cooper-idempotent-sends.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Citations académiques (APA · BibTeX · CFF)
Citation APA
cooper-email. (2026). cooper-idempotent-sends security audit report (audit version 1) [Author version 1]. Skillstore. https://skillstore.io/skills/cooper-email-cooper-idempotent-sends/audits/1Citation BibTeX
@techreport{cooper-email-cooper-email-cooper-idempotent-sends-2026,
author = {cooper-email},
title = {cooper-idempotent-sends security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/cooper-email-cooper-idempotent-sends/audits/1},
note = {Author version 1}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "cooper-idempotent-sends security audit report (audit version 1)"
version: "1"
type: report
authors:
- name: "cooper-email"
date-released: "2026-10-26"
url: "https://skillstore.io/skills/cooper-email-cooper-idempotent-sends/audits/1"
identifiers:
- type: other
value: "skillstore:cooper-email-cooper-idempotent-sends:audit:1"
description: "Skillstore immutable audit report identifier"
Score Skillstore
Pourquoi ce score Niveau de confiance des preuves: MoyenCe que vous pouvez créer
Recover a timed-out send
Review the original key and outbound messages before retrying a Cooper Email send whose result is unknown.
Design retryable email jobs
Choose stable job-derived identifiers for recurring reports and preserve the same identifier across retries.
Review agent resource creation
Check that inbox, draft, webhook, and domain creation workflows use the documented client_id parameter.
Essayez ces prompts
Explain which key to pass when replying to a message with Cooper Email. Do not send anything.
Propose a stable Cooper Email key for [report job] and [recipient]. Explain how retries should reuse it. Do not send anything.
A Cooper Email send timed out with key [key]. Plan recovery using the same key or outbound message checks. Do not send anything yet.
Review [workflow] for Cooper Email key persistence, parameter precedence, conflicts, in-progress responses, and replay-window limits. Propose corrections without executing writes.
Bonnes pratiques
- Associate each intended operation with a stable job-derived key and retain it across retries and agent restarts.
- Use the documented parameter for each action and account for client_id precedence when both identifiers are supplied.
- Investigate conflicts and unknown outcomes before sending again; respect the documented idempotency_key replay window.
Ăviter
- Generate a fresh timestamp-based key every time a job retries.
- Change the key after a conflict to force another send without checking the original result.
- Assume a timeout proves delivery failed or that duplicate protection lasts indefinitely.
Foire aux questions
Does this skill send email by itself?
Which key should a new message use?
How long does idempotency_key replay protection last?
What should I do after a timeout?
How do the two documented 409 errors differ?
Can these instructions be applied unchanged to another email API?
Détails du développeur
Auteur
cooper-emailLicence
MIT
Version de lâauteur
v1
RĂ©vision Skillstore
r1
Avis de version
La version dĂ©clarĂ©e par lâauteur nâest pas un SemVer valide.
RĂ©f
539af95a108e3fe7ef8081ed6fe1b45a397275d3
RĂ©cence de maintenance
26/10/2026
Utilisation
0 téléchargements · 0 vues
Structure de fichiers
đ SKILL.md