{"id":67939,"plugin_id":"plugin_asdk_app_6accab1e67648191a3b49c791f7e117e","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-28T13:11:50.509Z","digest":"96704d5987073761b7c6502ea4e89d53a715a307f9cc9ed36337153cd4230c1d","against":null,"payload":{"description":"Check or update explicit email and phone exclusions in Openmart when the user asks to suppress contacts or undo a suppression rule.","included_files":[],"name":"manage-exclusions","skill_md_contents":"---\nname: manage-exclusions\ndescription: Check or update explicit email and phone exclusions in Openmart when the user asks to suppress contacts or undo a suppression rule.\n---\n\nFor “is this excluded?”, use `check_contact_exclusions` with the exact supplied values. The API cannot list all exclusion rules. Do not claim that these rules constitute a complete legal consent registry or that they modify a CRM.\n\nUse `update_contact_exclusions` only when the user explicitly requests a change. Map “exclude/do not contact” to add and “remove this exclusion” to remove. If the request is ambiguous, clarify the action and values before mutation. A clear user instruction already authorizes the change; do not require a second confirmation.\n\nUse a stable request ID when retrying the same change. Report only the values and action acknowledged by the API. Never broaden a single email or phone exclusion to a domain or company exclusion. Never infer permission to send outreach from removing an exclusion.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}