菜单
Drive this repo's app end-to-end to verify a change at its real surfaces — boot, the /api/chat agent route, the /api/cron/tick dispatcher, and the browser UI. Use when a change needs runtime proof beyond `pnpm build` (which compiles /api/chat and /api/cron/tick but never calls either).
用 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 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.
| name | verify |
| description | Drive this repo's app end-to-end to verify a change at its real surfaces — boot, the /api/chat agent route, the /api/cron/tick dispatcher, and the browser UI. Use when a change needs runtime proof beyond `pnpm build` (which compiles /api/chat and /api/cron/tick but never calls either). |
| model | inherit |
Surfaces and the commands that reach them (all verified working):
pnpm dev (background, log to a file). Ready when the log has
Next.js's Ready in. Failure signatures to sweep: error|failed|unhandled
— expect zero on a clean boot.pnpm build can't see): curl -i -X POST localhost:3000/api/chat -H 'content-type: application/json' -d '{"messages":[]}' with no session
cookie → expect 401. This is the fail-closed check; the authed happy
path (streaming, tool calls, reasoning) is exercised via the browser below
— curl can't easily carry a real Supabase session cookie.app/api/cron/tick/route.ts — the per-minute
dispatcher, no browser needed):
curl -i localhost:3000/api/cron/tick with no Authorization header →
expect 401.curl -i localhost:3000/api/cron/tick -H 'authorization: Bearer wrong'
→ expect 401.CRON_SECRET unset in the running dev server's env → expect 401
even with a bearer header (fail-closed, not fail-open).curl -i localhost:3000/api/cron/tick -H "authorization: Bearer $CRON_SECRET" → expect 200 and a JSON body of counts (due,
claimed, done, failed).claimed count for that agent must be 0; the CAS advance-at-claim on
next_run_at means only the first tick can win the row./login with the AGENTS.md test account, then:
/agents (sidebar shell) and /agents/new (chat — send a beat
description, expect a streamed onboarding reply, a reasoning block, and
a oparax_x_search tool call round trip — the tool surface is only
oparax_x_search and save_agent; there is no handle-verify step)./agents/[id] (the desk dashboard): confirm the three tabs render as
Scans / Drafts / Agent runs; Pause/Resume flips the status badge and
clears/sets the "Next scan" label; Scan-now queues a run that (after the
next tick) appears in the Agent runs tab, whose trace card expands to
show the reasoning + drafted/executed search trace.