Run any Skill in Manus with one click

x-recheck

Stars5

Forks0

UpdatedJuly 20, 2026 at 01:17

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.

Installation

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.

Run Skill in Manus

Source

farzanmrz

farzanmrz/oparax

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Office Clerks, GeneralOffice and Administrative Support Occupations·SOC 43-9061

File Explorer

2 files

SKILL.md

readonly

name	x-recheck
description	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.

X-recheck

Use only when Farzan explicitly invokes $x-recheck.

Perform the complete workflow inline in the current task. Never delegate it, create a goal, 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.

Run the whole queue in one task turn:

Run rtk python3 .codex/outreach/outreach.py batch recheck once. If its records array is empty, report completion.
Claim the already-open signed-in X tab and open the New message modal once.
In one continuous Browser JavaScript execution, loop through every returned record using the same search field. Do not use one Browser tool call per account.
For each record, replace the search text with its exact handle and poll for an exact-handle result every 250 milliseconds for up to five seconds. Ignore similar handles.
If the exact result is normal-bright and enabled/selectable, append {handle, outcome: "available", display_name, first_name} without clicking it.
If the exact result is muted/greyed and disabled/unselectable, append {handle, outcome: "invalid"} without clicking it.
If no exact result appears after five seconds, including when X still shows only loading skeletons, append {handle, outcome: "invalid"} and continue to the next record.
Return the complete results array from that single Browser execution, encode its JSON as base64 in the task runtime, and run rtk python3 .codex/outreach/outreach.py apply-check-batch recheck <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 unapplied batch on logout, X warning, rate limit, changed UI, closed New message modal, recipient mismatch, or another genuine browser failure. Do not open LeanSpark.

Before reporting, run rtk python3 .codex/outreach/outreach.py count recheck. Return rechecked handles, resulting states, any stop reason, and that exact global remaining count.

More from this repository

same repository

x-stat

farzanmrz/oparax

Explicitly invoked deterministic status report for the Oparax outreach record store. Never invoke implicitly.

2026-07-205

lean-log

farzanmrz/oparax

Explicitly invoked Oparax workflow for logging X-contacted reporters into the fixed LeanSpark experiment. Never invoke implicitly.

2026-07-205

x-check

farzanmrz/oparax

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.

2026-07-205

x-dm

farzanmrz/oparax

Explicitly invoked Oparax workflow for sending already-prepared X DMs sequentially until the queue ends or X refuses a send. Never invoke implicitly.

2026-07-205

feature-build

farzanmrz/oparax

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.

2026-07-185

feature

farzanmrz/oparax

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).

2026-07-185

name	x-recheck
description	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.

X-recheck

Use only when Farzan explicitly invokes $x-recheck.

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.

Run the whole queue in one task turn:

Run rtk python3 .codex/outreach/outreach.py batch recheck once. If its records array is empty, report completion.
Claim the already-open signed-in X tab and open the New message modal once.
In one continuous Browser JavaScript execution, loop through every returned record using the same search field. Do not use one Browser tool call per account.
For each record, replace the search text with its exact handle and poll for an exact-handle result every 250 milliseconds for up to five seconds. Ignore similar handles.
If the exact result is normal-bright and enabled/selectable, append {handle, outcome: "available", display_name, first_name} without clicking it.
If the exact result is muted/greyed and disabled/unselectable, append {handle, outcome: "invalid"} without clicking it.
If no exact result appears after five seconds, including when X still shows only loading skeletons, append {handle, outcome: "invalid"} and continue to the next record.
Return the complete results array from that single Browser execution, encode its JSON as base64 in the task runtime, and run rtk python3 .codex/outreach/outreach.py apply-check-batch recheck <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.

Before reporting, run rtk python3 .codex/outreach/outreach.py count recheck. Return rechecked handles, resulting states, any stop reason, and that exact global remaining count.