스킬 cooper-agent-email-patterns

📦

cooper-agent-email-patterns

Name: cooper-agent-email-patterns
Author: cooper-email

v1 콘텐츠 리비전 r1 안전 ⚙️ 외부 명령어🌐 네트워크 접근

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.

지원: Claude Codex Code(CC)

🥉 77 브론즈

Maintain this Skill? Claim it 🥉 77 브론즈

내 에이전트로 설치

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

에이전트 요청

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.

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

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

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

Markdown 상세 GET /skills/cooper-email-cooper-agent-email-patterns.md 서명된 manifest GET /api/skills/cooper-email-cooper-agent-email-patterns/manifest 서명된 lockfile GET /api/skills/cooper-email-cooper-agent-email-patterns/lockfile

테스트해 보기

"cooper-agent-email-patterns" 사용 중입니다. Plan a persistent inbox for a support agent without a public webhook endpoint.

예상 결과:

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" 사용 중입니다. Plan email controls for an agent that sends financial notices.

예상 결과:

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.

보안 감사

안전

v1 • 2026. 10. 26. 버전별 보고서 열기

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.

스캔된 파일

분석된 줄 수

검토 항목

오탐 무시됨

위험 요인

⚙️ 외부 명령어 (32)

🌐 네트워크 접근 (1)

SKILL.md:7

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

감사자: codex

이 보고서 공유 및 인용

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

버전별 보고서 열기

보고서 링크 복사

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

Markdown 배지

[![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 배지

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

임베드 카드

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

학술 인용 (APA · BibTeX · CFF)

APA 인용

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

@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 점수

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

아키텍처

유지보수성

콘텐츠

커뮤니티

사양 준수

만들 수 있는 것

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.

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

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.

모범 사례

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.

피하기

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.

자주 묻는 질문

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.

개발자 세부 정보

작성자

cooper-email

라이선스

MIT

작성자 버전

Skillstore 리비전

버전 안내

작성자가 선언한 버전은 유효한 SemVer가 아닙니다.

리포지토리

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

참조

539af95a108e3fe7ef8081ed6fe1b45a397275d3

유지보수 최신성

2026. 10. 26.

사용량

0 다운로드 · 0 조회

파일 구조

📄 SKILL.md