菜单
Explicitly invoked Oparax workflow for sending already-prepared X DMs sequentially until the queue ends or X refuses a send. Never invoke implicitly.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | x-dm |
| description | Explicitly invoked Oparax workflow for sending already-prepared X DMs sequentially until the queue ends or X refuses a send. Never invoke implicitly. |
Use only when Farzan explicitly invokes $x-dm. That invocation authorizes sending the exact prepared messages for queued x_av records.
Perform the complete workflow inline in the current task. Never delegate it or start a subagent. Use only the Codex in-app Browser and .codex/outreach/outreach.py. Keep all X work sequential.
At the start, establish one persistent Codex goal: exhaust the x_av queue or stop on a defined X hard-stop. Reuse the active goal on automatic continuation; never create parallel goals or workers. A per-turn runtime boundary is not a stopping condition: leave the goal active and continue from the next x_av record automatically. Complete the goal only when next send returns null or a defined hard-stop is reached.
Loop:
rtk python3 .codex/outreach/outreach.py next send.null, stop normally; the queue is exhausted.rtk python3 .codex/outreach/outreach.py resolve <handle> x_done and continue without resending.rtk python3 .codex/outreach/outreach.py resolve <handle> x_unav and continue.rtk python3 .codex/outreach/outreach.py resolve <handle> x_done and continue.Hard-stop immediately if X shows Failed to send message, Failed, Try Again, a warning, rate limit, locked session, changed UI, recipient mismatch, or an unverifiable send. Do not retry, inspect another handle, or update the current record. Tell Farzan that X is refusing sends and identify the unchanged handle.
Do not produce a final response while next send returns a record. Do not stop after an arbitrary batch or because one turn reaches its runtime boundary. Continue in the same task until the queue is empty or a hard-stop condition occurs.
Before reporting, run rtk python3 .codex/outreach/outreach.py count send. Never open LeanSpark. Return newly sent handles, unavailable outcomes, the stopping reason, and that exact remaining x_av count.
Explicitly invoked deterministic status report for the Oparax outreach record store. Never invoke implicitly.
Explicitly invoked Oparax workflow for logging X-contacted reporters into the fixed LeanSpark experiment. Never invoke implicitly.
Explicitly invoked Oparax workflow for checking new queued X accounts once to determine whether they can receive DMs. Never invoke implicitly and never use for unavailable-account rechecks.
Explicitly invoked Oparax workflow for rechecking every previously unavailable X account and resolving it as available or invalid. Never invoke implicitly and never use for new-contact checks.
Phase 2 of the feature flow, standalone: implement the approved plan from the ft/N issue (or a directly-stated small build) with parallel implementers, a fast per-task typecheck gate, and deep review reserved for the foundational task. Use when the user says /feature-build, "build the plan", "implement the tasks", or "just build X" mid-flight on a feature branch.
The end-to-end feature flow: plan → build → QC → triage+ship, run as one guided sequence. Use when the user wants a full slice built from idea to shipped commit. For a single phase, use the granular skills directly: /feature-plan, /feature-build, /feature-qc, /feature-ship (or /simplify, /code-review, /feature-lint for individual QC passes).