Fähigkeiten cooper-agent-email-patterns
📦

cooper-agent-email-patterns

v1 Inhaltsrevision r1 Sicher ⚙️ Externe Befehle🌐 Netzwerkzugriff

Design Controlled Email Workflows for AI Agents

Agent email workflows need isolated identities, reliable replies, and clear sending permissions. This skill guides Cooper Email architecture with owner approval, delivery controls, and explicit trust boundaries.

Unterstützt: Claude Codex Code(CC)
Maintain this Skill? Claim it 🥉 77 Bronze

Mit meinem Agent installieren

Kopieren Sie diese Anfrage in Ihren Agent. Sie enthält die maßgebliche Skill-Seite und das Manifest.

Agent-Anfrage
Review the Skillstore skill "cooper-agent-email-patterns" from https://skillstore.io/skills/cooper-email-cooper-agent-email-patterns.md and its manifest at https://skillstore.io/api/skills/cooper-email-cooper-agent-email-patterns/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.

Markdown-Detailseite GET /skills/cooper-email-cooper-agent-email-patterns.md Signiertes manifest GET /api/skills/cooper-email-cooper-agent-email-patterns/manifest Signiertes lockfile GET /api/skills/cooper-email-cooper-agent-email-patterns/lockfile

Testen

„cooper-agent-email-patterns“ wird verwendet. Plan a persistent inbox for a support agent without a public webhook endpoint.

Erwartetes Ergebnis:

  • Create a dedicated inbox with a stable client identifier and an inbox-scoped key.
  • Use long-polling with a job deadline and read extracted message text.
  • Reply using the parent message identifier, then mark handled mail read.
  • Keep job state outside email and treat all incoming content as untrusted.

„cooper-agent-email-patterns“ wird verwendet. Plan email controls for an agent that sends financial notices.

Erwartetes Ergebnis:

  • Establish a verified owner and enable approval mode before sending.
  • Require reapproval whenever recipients, subject, body, or attachments change.
  • Restrict recipients with an allow list and use idempotency for every send.
  • Respect suppressions and review bounce and complaint metrics.

Sicherheitsaudit

Sicher
v1 • 26.10.2026 Versionsbericht öffnen

All 34 static findings are false positives involving Markdown code spans, homepage metadata, or an inbox-scope lookup. The document provides architecture guidance and explicitly addresses untrusted email, owner authentication, webhook verification, and key protection. No evidence found of malicious execution, credential exfiltration, or prompt injection attempts.

1
Gescannte Dateien
97
Analysierte Zeilen
0
Prüfelemente
0
Falschmeldungen ignoriert

Risikofaktoren

⚙️ Externe Befehle (32)
SKILL.md:18 SKILL.md:22 SKILL.md:24 SKILL.md:25 SKILL.md:27 SKILL.md:34 SKILL.md:35 SKILL.md:36 SKILL.md:37 SKILL.md:38 SKILL.md:40 SKILL.md:45 SKILL.md:49 SKILL.md:50 SKILL.md:54 SKILL.md:56 SKILL.md:57 SKILL.md:61 SKILL.md:62 SKILL.md:63 SKILL.md:67 SKILL.md:68 SKILL.md:69 SKILL.md:70 SKILL.md:74 SKILL.md:77 SKILL.md:78 SKILL.md:79 SKILL.md:81 SKILL.md:89 SKILL.md:90 SKILL.md:92
🌐 Netzwerkzugriff (1)
SKILL.md:7
Das letzte abgeschlossene statische und semantische Audit erkannte keine bestätigten Sicherheitsbefunde. Dies beweist nicht, dass der Skill keine Nebenwirkungen hat.
Geprüft von: codex
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.

Versionsbericht öffnen
Sicherheitsbewertung

Berichtslink kopieren

https://skillstore.io/skills/cooper-email-cooper-agent-email-patterns/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown-Badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/cooper-email-cooper-agent-email-patterns/security.svg)](https://skillstore.io/skills/cooper-email-cooper-agent-email-patterns?utm_source=security_passport_badge)

HTML-Badge

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

Einbettungskarte

<iframe src="https://skillstore.io/embed/skills/cooper-email-cooper-agent-email-patterns.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

cooper-email. (2026). cooper-agent-email-patterns security audit report (audit version 1) [Author version 1]. Skillstore. https://skillstore.io/skills/cooper-email-cooper-agent-email-patterns/audits/1

BibTeX-Zitat

@techreport{cooper-email-cooper-email-cooper-agent-email-patterns-2026, author = {cooper-email}, title = {cooper-agent-email-patterns security audit report (audit version 1)}, institution = {Skillstore}, year = {2026}, number = {1}, url = {https://skillstore.io/skills/cooper-email-cooper-agent-email-patterns/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-agent-email-patterns 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-agent-email-patterns/audits/1" identifiers: - type: other value: "skillstore:cooper-email-cooper-agent-email-patterns:audit:1" description: "Skillstore immutable audit report identifier"

Skillstore-Score

Warum dieser Score Evidenzvertrauen: Mittel
55
Architektur
85
Wartbarkeit
87
Inhalt
65
Gemeinschaft
83
Spezifikationskonformität

Was Sie erstellen können

Plan a dedicated agent inbox

Choose persistent or temporary inboxes and define reply handling without granting access to a personal mailbox.

Define approval for sensitive messages

Design verified-owner approval and recipient restrictions for financial, legal, or first-contact email workflows.

Review email integration boundaries

Assess webhook authentication, owner task verification, credential scope, and treatment of untrusted email content.

Diese Prompts ausprobieren

Choose an inbox model 
My agent performs [task]. Compare a persistent inbox with temporary inboxes per run. Recommend an identity, expiration, and key-scope strategy.
Design a reply loop 
Design a Cooper Email reply loop for [workflow] without a public endpoint. Include deadlines, extracted text, threading, read-state updates, and external job state.
Add owner approval 
Plan owner-approved email for [sensitive workflow]. Include verified ownership, draft reapproval after edits, recipient allow lists, owner updates, and duplicate-send prevention.
Review an event-driven architecture 
Review this Cooper Email architecture: [design]. Assess webhook signatures, timestamp freshness, owner verification, injection boundaries, secret storage, suppressions, and retries. Propose changes without sending mail.

Bewährte Praktiken

  • Use separate inboxes for independent agents and prefer narrowly scoped keys.
  • Enable owner approval for sensitive sends and verify owner tasks before treating replies as instructions.
  • Combine bounded waits and idempotent sends with signature verification for webhook-based workflows.

Vermeiden

  • Granting an agent broad access to a personal mailbox when a dedicated inbox is sufficient.
  • Treating email subjects, bodies, attachments, or links as trusted instructions.
  • Retrying sends without idempotency or ignoring recipient suppressions.

Häufig gestellte Fragen

Does this skill send or receive email by itself?
No. It provides architecture guidance. Actual operations require Cooper Email tools, credentials, and the relevant action workflows.
When should an agent use a temporary inbox?
Use temporary inboxes for isolated jobs, sign-ups, or trials. Set expiration deliberately; deletion follows the service cleanup schedule.
Do incoming replies require a public webhook endpoint?
No. The skill describes long-polling and event listing as alternatives. Webhook deployments require signature verification and rejection of stale timestamps.
How does owner approval affect edited drafts?
Approval mode holds outgoing mail for the verified owner. Changing recipients, subject, body, or attachments requires approval again.
Can an agent trust the sender address as proof of ownership?
No. The guidance requires an authenticated owner task with the verified_owner flag. Screening labels alone are not a guarantee.
How should API keys be stored?
Use a secret store or environment variable. Never place keys in chat, logs, commits, or email, and prefer inbox-scoped keys.

Entwicklerdetails

Lizenz

MIT

Autorenversion

v1

Skillstore-Revision

r1

Versionshinweis

Die vom Autor angegebene Version ist kein gültiges SemVer.

Repository

https://github.com/cooper-email/cooper-email/tree/e017faae12644b593317e55d97612eb24dfa24af/skills/cooper-agent-email-patterns

Ref.

539af95a108e3fe7ef8081ed6fe1b45a397275d3

Aktualität der Wartung

26.10.2026

Nutzung

0 Downloads · 0 Aufrufe

Dateistruktur

📄 SKILL.md