x-dm-auto-chat
X (Twitter) DM automated chat end-to-end Skill: scan DM inbox to identify pending-reply conversations, read message history, generate persona-based replies and send; also supports searching users and starting new conversations. Built-in E2E passcode unlock, DM permission filtering, and rate control. Use when user mentions X auto-reply DMs, Twitter DM automated chat, auto-handle unread DMs, reply to X private messages with persona, X DM outreach campaign, batch send DMs to Twitter users, auto-process pending DM replies, Twitter DM bot, automated Twitter outreach, X direct message automation.
npx skills add browser-act/skills --skill x-dm-auto-chat --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# X (Twitter) — DM Auto Chat (End-to-End) > Full X DM automation Skill: inbox scan → conversation read → persona-based reply → send; also supports search-and-outreach. The calling Agent generates reply text based on persona; this Skill handles all mechanical operations. ## Language All process output to user (progress updates, process notifications) follows the user's language. ## Objective Encapsulate "refresh DM list → identify pending replies → read context → reply with persona → send" and "search user → enter chat → send first message" into callable end-to-end capabilities. ## Prerequisites - Browser is open at X site, logged into X account (`[aria-label="Account menu"]` present) - The 4-digit DM passcode for the current account is available (required for E2E encryption) - Caller has prepared a "persona description" (used to generate replies), e.g.: - `"You are BrowserAct outreach team. Tone: friendly, concise, professional. Goal: invite creators to collaborate."` - Optional: list of target user search queries (for outreach scenario) ## Pre-execution Checks ### 1. Tool Readiness If browser-act has been confirmed available in the current session → skip. Invoke `browser-act` via
- Language
- Objective
- Prerequisites
- Pre-execution Checks
- 1. Tool Readiness
- 2. Open DM Entry + Comprehensive State Check
- 3. DM Passcode Unlock (when needpasscode is true)
- Business Flows
- Scenario A: Scan unread DMs → Persona-based reply
- Scenario B: Search users → Start new conversation → Send first message
- Capability Components (callable individually)
- Composite: Inbox scan (API + DOM merged)
- API: Fetch inbox from API only (with pagination)
- DOM: Read current conversation messages
What does the x-dm-auto-chat skill do?
X (Twitter) DM automated chat end-to-end Skill: scan DM inbox to identify pending-reply conversations, read message history, generate persona-based replies and send; also supports searching users and starting new conversations. Built-in E2E passcode unlock, DM permission filtering, and rate control. Use when user mentions X auto-reply DMs, Twitter DM automated chat, auto-handle unread DMs, reply to X private messages with persona, X DM outreach campaign, batch send DMs to Twitter users, auto-process pending DM replies, Twitter DM bot, automated Twitter outreach, X direct message automation.
How do I install it?
Run `npx skills add browser-act/skills --skill x-dm-auto-chat --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From browser-act/skills, a repository with 5,160 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.
