worker
Team worker protocol (ACK, mailbox, task lifecycle) for tmux-based OMX teams
- License 许可
- MIT
- 所属仓库
- agisota/old-one
- 最近更新
- 2026-07-04
- Stars
- ★ 3
- Forks
- 1
01 前言 Front Matter
- name
- worker
- description
- Team worker protocol (ACK, mailbox, task lifecycle) for tmux-based OMX teams
03 SKILL.md 正文
Worker Skill
This skill is for a Codex session that was started as an OMX Team worker (a tmux pane spawned by $team).
Identity
You MUST be running with OMX_TEAM_WORKER set. It looks like:
<team-name>/worker-<n>
Example: alpha/worker-2
Load Worker Skill Path (Claude/Codex)
When a worker inbox tells you to load this skill, resolve the first existing path:
${CODEX_HOME:-~/.codex}/skills/worker/SKILL.md~/.codex/skills/worker/SKILL.md<leader_cwd>/.codex/skills/worker/SKILL.md<leader_cwd>/skills/worker/SKILL.md(repo fallback)
Startup Protocol (ACK)
- Parse
OMX_TEAM_WORKERinto:teamName(before the/)workerName(after the/, usuallyworker-<n>)
- Send a startup ACK to the lead mailbox before task work:
- Recipient worker id:
leader-fixed - Body: one short deterministic line (recommended:
ACK: <workerName> initialized).
- Recipient worker id:
- After ACK, proceed to your inbox instructions.
The lead will see your message in:
<team_state_root>/team/<teamName>/mailbox/leader-fixed.json
Use CLI interop:
omx team api send-message --input <json> --jsonwith{team_name, from_worker, to_worker:"leader-fixed", body}
Copy/paste template:
omx team api send-message --input "{\"team_name\":\"<teamName>\",\"from_worker\":\"<workerName>\",\"to_worker\":\"leader-fixed\",\"body\":\"ACK: <workerName> initialized\"}" --json
Inbox + Tasks
- Resolve canonical team state root in this order:
OMX_TEAM_STATE_ROOTenv- worker identity
team_state_root - team config/manifest
team_state_root - local cwd fallback (
.omx/state)
- Read your inbox:
<team_state_root>/team/<teamName>/workers/<workerName>/inbox.md - Pick the first unblocked task assigned to you.
- Read the task file:
<team_state_root>/team/<teamName>/tasks/task-<id>.json(example:task-1.json) - Task id format:
- The MCP/state API uses the numeric id (
"1"), not"task-1". - Never use legacy
tasks/{id}.jsonwording.
- The MCP/state API uses the numeric id (
- Claim the task (do NOT start work without a claim) using claim-safe lifecycle CLI interop (
omx team api claim-task --json). - Do the work.
- Complete/fail the task via lifecycle transition CLI interop (
omx team api transition-task-status --json) fromin_progresstocompletedorfailed.- Do NOT directly write lifecycle fields (
status,owner,result,error) in task files.
- Do NOT directly write lifecycle fields (
- Use
omx team api release-task-claim --jsononly for rollback/requeue topending(not for completion). - Update your worker status:
<team_state_root>/team/<teamName>/workers/<workerName>/status.jsonwith{"state":"idle", ...}
Mailbox
Check your mailbox for messages:
<team_state_root>/team/<teamName>/mailbox/<workerName>.json
When notified, read messages and follow any instructions. Use short ACK replies when appropriate.
Note: leader dispatch is state-first. The durable queue lives at:
<team_state_root>/team/<teamName>/dispatch/requests.json
Hooks/watchers may nudge you after mailbox/inbox state is already written.
Use CLI interop:
omx team api mailbox-list --jsonto readomx team api mailbox-mark-delivered --jsonto acknowledge delivery
Copy/paste templates:
omx team api mailbox-list --input "{\"team_name\":\"<teamName>\",\"worker\":\"<workerName>\"}" --json
omx team api mailbox-mark-delivered --input "{\"team_name\":\"<teamName>\",\"worker\":\"<workerName>\",\"message_id\":\"<MESSAGE_ID>\"}" --json
Dispatch Discipline (state-first)
Worker sessions should treat team state + CLI interop as the source of truth.
- Prefer inbox/mailbox/task state and
omx team api ... --jsonoperations. - Do not rely on ad-hoc tmux keystrokes as a primary delivery channel.
- If a manual trigger arrives (for example
tmux send-keysnudge), treat it only as a prompt to re-check state and continue through the normal claim-safe lifecycle.
Shutdown
If the lead sends a shutdown request, follow the shutdown inbox instructions exactly, write your shutdown ack file, then exit the Codex session.
04 同仓库更多 Skills
zoom-out
Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.
zeroize-audit
Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C/C++/Rust code handling secrets, keys, passwords, or other sensitive data.
yeet
Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).
yara-rule-authoring
Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.
x-twitter-growth
X/Twitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X/Twitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.
x-api
X/Twitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.