菜单
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.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
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 sending already-prepared X DMs sequentially until the queue ends or X refuses a send. Never invoke implicitly.
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).
| name | x-check |
| description | 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. |
Use only when Farzan explicitly invokes $x-check.
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. Never send a message.
Open the X New message modal once and keep it open for the entire run. Never click or select a search result and never navigate into a conversation. The search result row already provides the exact handle, visible display name, and DM availability.
Run the whole queue in one task turn:
rtk python3 .codex/outreach/outreach.py batch check once. If its records array is empty, report completion.{handle, outcome: "available", display_name, first_name} to the in-memory results array without clicking it.{handle, outcome: "unavailable"} without clicking it.{handle, outcome: "invalid"} and continue to the next record.rtk python3 .codex/outreach/outreach.py apply-check-batch check <base64-payload> exactly once.Do not create a goal, subagent, parallel worker, or per-account shell/browser loop. Do not split a complete queue into arbitrary batches.
Stop immediately without changing the current record on logout, X warning, rate limit, changed UI, closed New message modal, recipient mismatch, or any inconclusive state. Do not open LeanSpark.
Before reporting, run rtk python3 .codex/outreach/outreach.py count check. Return checked handles, resulting states, any stop reason, and that exact global remaining count. Never infer the remaining count from a vertical row in the status table.