What problem does it solve? Operating a solo-run community means posting the same announcement across Discord, Threads, KakaoTalk, email, and Notion, each with different APIs, tokens, tones, and failure modes. This Skill documents the verified publishing path for each channel so nothing is posted to the wrong place or silently fails. ## Core Features & Use Cases - Multi-channel publishing: Post Discord announcements via a bot (with the required custom User-Agent to bypass Cloudflare 403), queue Threads posts through a JSON queue file consumed by a launchd runner, send KakaoTalk messages via kmsg, and send Naver SMTP email with python3 smtplib. - Bulk email campaigns: Select recipients from a Notion subscriber DB by ad-consent status, reconnect SMTP every 15 messages to avoid 452 errors, and verify delivery with IMAP sent-folder checks and Notion send markers. - Compliance and verification: Enforce (광고) subject prefixes, unsubscribe HMAC links, per-recipient individual sends, and post-publish verification by re-reading each channel. - Use Case: When a new cohort opens for the GET100 community, use this Skill to send the announcement email to consenting subscribers, queue a Threads post, and post a Discord notice, then confirm all three actually went out. ## Quick Start Read this skill and publish the announcement to the Discord notice channel, then verify the message was posted.
