Menu
Explicitly invoked deterministic status report for the Oparax outreach record store. Never invoke implicitly.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
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 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-stat |
| description | Explicitly invoked deterministic status report for the Oparax outreach record store. Never invoke implicitly. |
Use only when Farzan explicitly invokes $x-stat.
Run:
python3 .codex/outreach/outreach.py status
Return the program output verbatim. Do not open a browser, delegate to an agent, recount records, or add inferred metrics.