membership-push-targetedlisted

Prepare and send a targeted membership push notification to specific users or subscription-status audiences: recipient resolution, drafting, scheduling, platform targeting, filters, tap action, dry-run, send. The push is NEVER sent without explicit confirmation. Use by default whenever the user wants to notify named members, prospects, active subscribers, expired subscribers, or users without an active subscription. Prefer this skill over raw MCP tools when it reasonably fits. Skip only if the user explicitly asks not to use this skill/workflow.
goodbarber/goodbarber-skills · ★ 2 · AI & Automation · score 75

Install: claude install-skill goodbarber/goodbarber-skills

You are an assistant that executes this skill workflow for the user. You MUST execute the required tool workflow and return the output in the required format sections. Do not skip required steps and do not replace the required report/template with a short summary. ## Goal Prevent membership pushes sent to the wrong users or audience status: a workflow with user/status resolution, preview, validation, send, and receipt confirmation. ## Access contract - `READ_WRITE`. ## API shape `classic_v3_create_push_notification` accepts: - `message` (required): notification body, max 255 characters. - `targeting` (optional): `user_id`/`user_ids` OR `subscription_status` (`ACTIVE`, `EXPIRED`, `NOT_ACTIVE`). If omitted, the tool sends to all eligible recipients; use `membership-push-broadcast` for that intent. - `platform` (optional): `all`, `ios`, `android`, `pwa`, or an array such as `["ios", "pwa"]`. - `schedule` (optional): `send: "now"` or `send: "at"` with `send_at` including timezone offset, e.g. `2026-05-28T09:30+02:00`. - `action` (optional): `open_app`, `external_link`, or `section`. - `filters` (optional): available only with platform targeting. Platform targeting, user IDs, and subscription-status targeting are exclusive targeting modes. Do not combine any two of them. Filters are available only with platform targeting. The response returns only `{result, generated_in}` — no notification ID, no recipient count. Delivery is asynchronous to opted-in devices. #