x-account-digest

name: x-account-digest description: Monitor selected X/Twitter accounts such as OpenAI, Google Gemini, Google, ChatGPT, and Google DeepMind, detect posts not seen in prior runs, and prepare or send a daily email digest. Use when the user asks to check specific X accounts, summarize new posts today, create an X account digest, monitor AI/company X posts, or email a daily X/Twitter update.

X Account Digest

Overview

Use this skill to check a fixed watchlist of X/Twitter accounts, identify posts that are new since the previous run, and produce a concise email-ready digest. Prefer the configured XActions MCP tools for profile/account lookup and public post retrieval.

Watchlist

Read references/accounts.md for the canonical monitored accounts and known handle candidates. If a display name maps to multiple possible handles, verify the account identity before including posts.

Default targets:

• OpenAI
• Google Gemini
• Google
• ChatGPT
• Google DeepMind

Workflow

1. Determine the check window.

   • For a scheduled daily run, use the user's local day in Asia/Taipei unless the prompt gives another timezone.
   • For an ad hoc run, use the last 24 hours unless the user asks for another range.

2. Resolve accounts.

   • Use XActions account search/profile tools such as search_twitter_users or x_get_profile.
   • Confirm official-looking accounts by handle, display name, verification signal if available, profile text, and follower count.
   • Do not rely on lookalike accounts when official identity is unclear.

3. Fetch recent posts for each resolved account.

   • Prefer XActions post tools if available in the current MCP configuration.
   • If only account search/profile tools are enabled, report that post retrieval needs the XActions post-reading tool allowlist to be expanded.
   • Cookie is not required for public account/profile checks, but some post or rate-limited lookups may fail without it.

4. Normalize posts into JSON objects and run scripts/filter_new_posts.py.

   • Include at minimum account, handle, id or url, created_at, text, and url when available.
   • Pipe JSON array input to the script or pass --input <file>.
   • The script stores state under %CODEX_HOME%/skills/x-account-digest/state/seen-posts.json by default.

5. Prepare the digest only if there are new posts.

   • Group by account.
   • For each post, include date/time, direct URL, a Chinese summary, and an English summary.
   • Keep commentary factual. Separate launches, model updates, product announcements, policy/safety notes, and research posts when useful.
   • If no new posts are found, do not send an email unless the user explicitly asks for no-news notifications.

6. Send or draft email.

   • If a Gmail/Outlook connector is active and the user supplied a recipient, send only after the user has authorized automatic sending for this workflow.
   • If email is not connected or recipient is unknown, produce an email-ready subject and body instead.
   • Suggested subject: Daily X Digest / AI �b���C��K�n - YYYY-MM-DD.

Email Format

Use this structure:

Subject: Daily X Digest / AI �b���C��K�n - YYYY-MM-DD

New posts found / �s�K���: <count>
Accounts checked / �w�ˬd�b��: OpenAI, Google Gemini, Google, ChatGPT, Google DeepMind

OpenAI (@handle)
- <time> - <short title or topic>
  ����K�n: <1-3 concise Traditional Chinese bullets or sentences>
  English summary: <1-3 concise English bullets or sentences>
  Link / ���s��: <url>

...

Notes / �Ƶ�
- Mention accounts with lookup/post-fetch failures separately.
- Mention if XActions rate limits, missing cookie, or disabled MCP tools prevented a complete check.

Safety And Accuracy

• Treat X/Twitter automation as sensitive: do not like, reply, follow, unfollow, post, or DM from this skill.
• Do not include private or login-only data unless the user explicitly provided credentials and asked for it.
• Cite direct post URLs when available.
• Preserve the state file; it is what prevents duplicate daily emails.