cooper-suppressions-bounces
Manage Cooper Email Bounces and Suppressions
Bounces and spam complaints can interrupt delivery and harm sender reputation. This skill guides Cooper Email investigations, rate checks, and consent-based suppression management.
Установить с помощью моего Агента
Скопируйте этот запрос в своего Агента. Он содержит каноническую страницу Skill и манифест.
Review the Skillstore skill "cooper-suppressions-bounces" from https://skillstore.io/skills/cooper-email-cooper-suppressions-bounces.md and its manifest at https://skillstore.io/api/skills/cooper-email-cooper-suppressions-bounces/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Ваш Агент по-прежнему должен показать план и запросить все подтверждения, требуемые политикой безопасности.
Ресурсы для AI-агентов
Используйте эти ссылки, когда AI-агенту, crawler или script нужен чистый контекст вместо полной страницы.
Протестировать
Использование «cooper-suppressions-bounces». Cooper reports recipient_suppressed. The suppression record shows a bounce. What should I do?
Ожидаемый результат:
- The address is suppressed because of a bounce.
- Do not retry the same address. Ask for a corrected address.
- Remove the suppression only after confirming the address is valid and the recipient wants the mail.
Использование «cooper-suppressions-bounces». My inbox-scoped key returns permission_denied when listing Cooper suppressions.
Ожидаемый результат:
- Suppression listing requires an account-level key or OAuth.
- Use an authorized account connection before investigating the suppression record.
- Do not paste credentials into the conversation.
Использование «cooper-suppressions-bounces». Cooper reports recipient_blocked. Is this the same as recipient_suppressed?
Ожидаемый результат:
- No. A block or allow list match can return recipient_blocked.
- Suppressions are separate and can result from bounces, complaints, or manual action.
- Inspect list entries before considering policy changes. Removing a suppression does not resolve a list restriction.
Аудит безопасности
БезопасноAll 16 static findings are false positives involving Markdown formatting, homepage metadata, or recipient consent language. No evidence found of shell execution, reconnaissance, credential exfiltration, or prompt injection. The skill documents authenticated Cooper operations and requires confirmation of address validity and recipient consent before suppression removal.
Факторы риска
⚙️ Внешние команды (14)
🌐 Доступ к сети (1)
Поделиться и цитировать этот отчет
Делитесь версионным отчетом об оценке, нейтральным значком, встраиваемой карточкой и цитатами. Skillstore публикует доказательства, не решая, безопасен ли этот Skill.
Копировать ссылку на отчёт
https://skillstore.io/skills/cooper-email-cooper-suppressions-bounces/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportЗначок Markdown
[](https://skillstore.io/skills/cooper-email-cooper-suppressions-bounces?utm_source=security_passport_badge)Значок HTML
<a href="https://skillstore.io/skills/cooper-email-cooper-suppressions-bounces?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/cooper-email-cooper-suppressions-bounces/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Встраиваемая карточка
<iframe src="https://skillstore.io/embed/skills/cooper-email-cooper-suppressions-bounces.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-suppressions-bounces security audit report (audit version 1) [Author version 1]. Skillstore. https://skillstore.io/skills/cooper-email-cooper-suppressions-bounces/audits/1Цитата BibTeX
@techreport{cooper-email-cooper-email-cooper-suppressions-bounces-2026,
author = {cooper-email},
title = {cooper-suppressions-bounces security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/cooper-email-cooper-suppressions-bounces/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-suppressions-bounces 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-suppressions-bounces/audits/1"
identifiers:
- type: other
value: "skillstore:cooper-email-cooper-suppressions-bounces:audit:1"
description: "Skillstore immutable audit report identifier"
Оценка Skillstore
Почему такая оценка Достоверность доказательств: СреднийЧто вы можете построить
Resolve a suppressed recipient
Find why a customer address was suppressed and report the source message before requesting a correction or consent confirmation.
Investigate delivery trends
Review bounce and complaint rates, inspect related events, and recommend slower sending or stricter outbound controls.
Handle application delivery errors
Distinguish recipient_suppressed from recipient_blocked and identify the appropriate suppression or list management workflow.
Попробуйте эти промпты
Explain recipient_suppressed in Cooper Email and identify what information I need to investigate it. Do not change account settings.
Investigate why [recipient] is suppressed in Cooper Email. Summarize the reason, source message, and related events without removing the suppression.
Review Cooper Email bounce and complaint rates for the default reporting period. Summarize related events and recommend actions without changing outbound policies.
Investigate suppression and block-list status for [recipient]. Ask for confirmation of validity and consent before suppression removal; keep list policies unchanged.
Лучшие практики
- Inspect the suppression reason, source message, and related events before recommending action.
- Confirm address validity and recipient consent before removing a suppression.
- Monitor bounce and complaint rates, slow sending when rates rise, and review recipient lists.
Избегать
- Retrying the same bounced address without correcting the underlying problem.
- Removing suppressions merely to bypass spam complaints or recipient consent.
- Treating suppressions and block or allow lists as the same control.
Часто задаваемые вопросы
What does recipient_suppressed mean?
Which credentials can list suppressions?
When can I remove a suppression?
How should I handle a spam complaint?
How can I check bounce and complaint rates?
Does this skill install Cooper tools or configure webhooks?
Сведения для разработчиков
Автор
cooper-emailЛицензия
MIT
Версия автора
v1
Ревизия Skillstore
r1
Примечание о версии
Заявленная автором версия не соответствует SemVer.
Ссылка
539af95a108e3fe7ef8081ed6fe1b45a397275d3
Актуальность поддержки
26.10.2026
Использование
0 загрузок · 0 просмотров
Структура файлов
📄 SKILL.md