一键导入
lean-log
Explicitly invoked Oparax workflow for logging X-contacted reporters into the fixed LeanSpark experiment. Never invoke implicitly.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Explicitly invoked Oparax workflow for logging X-contacted reporters into the fixed LeanSpark experiment. Never invoke implicitly.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Explicitly invoked deterministic status report for the Oparax outreach record store. 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).
基于 SOC 职业分类
| name | lean-log |
| description | Explicitly invoked Oparax workflow for logging X-contacted reporters into the fixed LeanSpark experiment. Never invoke implicitly. |
Use only when Farzan explicitly invokes $lean-log.
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 open X.
Loop:
rtk python3 .codex/outreach/outreach.py next lean.null, stop normally; the queue is exhausted.leanspark_url in .codex/outreach/config.json.Name or handle of who you contacted and exactly one Log a contact button.Log a contact.rtk python3 .codex/outreach/outreach.py resolve <handle> l_done and continue.Never touch Mark replied, Mark booked, interview, or any other experiment control.
If the URL, authentication, controls, labels, layout, or success behavior does not match these instructions, stop immediately. Do not guess or click an alternative. Leave the record x_done, capture a screenshot, and tell Farzan the handle, what was expected, and what changed.
Return logged handles, the stopping reason, and the remaining x_done count.