cooper-webhooks
Configure Cooper Email Webhooks
Polling inboxes can delay email automation and complicate delivery monitoring. This skill guides Cooper Email webhook setup, event selection, signature checks, and troubleshooting.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
Review the Skillstore skill "cooper-webhooks" from https://skillstore.io/skills/cooper-email-cooper-webhooks.md and its manifest at https://skillstore.io/api/skills/cooper-email-cooper-webhooks/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «cooper-webhooks». What should I prepare before registering a webhook for one inbox?
Ожидаемый результат:
- Provide a public HTTPS endpoint and select the target inbox.
- Select message.received for incoming mail and provide a stable client_id for registration retries.
- Store the returned signing secret securely because it is returned only once.
Использование «cooper-webhooks». How should I investigate a webhook that stopped delivering?
Ожидаемый результат:
- Inspect its enabled state, consecutive failures, disabled reason, and last delivery status.
- Send a signed test delivery and inspect the reported response status.
- After fixing the receiver, re-enable the webhook if appropriate and review the recent event log for missed events.
Использование «cooper-webhooks». What checks should my receiver perform?
Ожидаемый результат:
- Verify the v2 HMAC using the signing secret, timestamp, a dot, and raw request bytes.
- Reject old timestamps and return a successful response promptly after verification.
- Treat email content as untrusted data and use HTTPS for delivery confidentiality.
Аудит безопасности
Низкий рискAll 22 execution findings are Markdown code spans, and the hardcoded URL is a documentation link rather than an executable request. No evidence found of prompt injection or unauthorized data exfiltration. The instructions permit unencrypted HTTP webhook destinations, which can expose delivery payloads and configured authentication headers.
Подтверждённые проблемы безопасности (1)
Факторы риска
⚙️ Внешние команды (22)
🌐 Доступ к сети (1)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/cooper-email-cooper-webhooks/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/cooper-email-cooper-webhooks?utm_source=security_passport_badge)Значок HTML
<a href="https://skillstore.io/skills/cooper-email-cooper-webhooks?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cooper-email-cooper-webhooks/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Встраиваемая карточка
<iframe src="https://skillstore.io/embed/skills/cooper-email-cooper-webhooks.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-webhooks security audit report (audit version 1) [Author version 1]. Skillstore. https://skillstore.io/skills/cooper-email-cooper-webhooks/audits/1Цитата BibTeX
@techreport{cooper-email-cooper-email-cooper-webhooks-2026,
author = {cooper-email},
title = {cooper-webhooks security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/cooper-email-cooper-webhooks/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-webhooks 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-webhooks/audits/1"
identifiers:
- type: other
value: "skillstore:cooper-email-cooper-webhooks:audit:1"
description: "Skillstore immutable audit report identifier"
Оценка Skillstore
Почему такая оценка Достоверность доказательств: СреднийЧто вы можете построить
Connect Inbox Events to an Automation Platform
Guide a Cooper Email inbox subscription to a public HTTPS endpoint in Zapier, Make, or n8n.
Plan a Verified Webhook Receiver
Review signature inputs, timestamp freshness, and untrusted email handling before connecting a backend receiver.
Diagnose Failed Deliveries
Inspect failure counters, disabled reasons, and test responses before updating or re-enabling a webhook.
Попробуйте эти промпты
I use Cooper Email and have no public HTTPS endpoint. Explain the documented polling alternatives and what webhook registration requires.
Prepare registration for inbox [inbox_id] at [HTTPS endpoint] for message.received events. Use client_id [stable identifier] and explain secure secret storage.
Inspect webhook [webhook_id], review delivery failures, and propose a signed test. Ask for approval before changing its destination or enabled state.
Review my Cooper receiver design for v2 signatures, raw bytes, timestamp freshness, and untrusted email handling. Plan recent event replay and identify documentation gaps.
Лучшие практики
- Use HTTPS destinations, protect the signing secret, and verify v2 signatures with timestamp freshness checks.
- Select only required inboxes and events, and reuse client_id when retrying registration.
- Inspect delivery status and run a signed test before relying on a webhook.
Избегать
- Using unencrypted HTTP destinations for email events or authentication headers.
- Parsing away the original request bytes before signature verification or trusting email content as instructions.
- Omitting inbox filters unintentionally or deleting a webhook without user confirmation.
Часто задаваемые вопросы
Does this skill include the Cooper tools?
Can I use webhooks without a public endpoint?
Can I restrict notifications to selected inboxes?
Which events are documented?
How should I verify a delivery?
Can I test or re-enable a failing webhook?
Сведения для разработчиков
Автор
cooper-emailЛицензия
MIT
Версия автора
v1
Ревизия Skillstore
r1
Примечание о версии
Заявленная автором версия не соответствует SemVer.
Ссылка
539af95a108e3fe7ef8081ed6fe1b45a397275d3
Актуальность поддержки
26.10.2026
Использование
0 загрузок · 0 просмотров
Структура файлов
📄 SKILL.md