본문으로 건너뛰기
cccskills
무료GitHub에 공개

worker

Coordinate a worker agent in a tmux-based OMX Team through startup acknowledgements, task claims, status transitions, and mailbox checks. Keep task ownership, completion evidence, and idle status visible to the team.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

원문원문 설명 보기

Team worker protocol (ACK, mailbox, task lifecycle) for tmux-based OMX teams

Yeachan-Heo/oh-my-codex
설치 방법 보기

이럴 때 유용합니다

  • Coordinate startup and task assignment for an OMX Team worker
  • Record task ownership and completion evidence
  • Check and acknowledge team mailbox messages
  • Handle worker idle status and shutdown acknowledgements

포함된 파일(1)

  • SKILL.md2.7 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Worker Skill

When to use

Use only when the session was started as an OMX Team worker. Read AGENTS.md#durable-runtime-invariants-canonical-ssot before acting; it defines the durable ownership and coordination boundaries.

Inputs and preconditions

  • Require OMX_TEAM_WORKER=<team-name>/worker-<n>.
  • Resolve this skill from the first existing path: ${CODEX_HOME:-~/.codex}/skills/worker/SKILL.md, ~/.codex/skills/worker/SKILL.md, <leader_cwd>/.codex/skills/worker/SKILL.md, then <leader_cwd>/skills/worker/SKILL.md.
  • Resolve the Team state root in this order: OMX_TEAM_STATE_ROOT, worker identity team_state_root, config/manifest team_state_root, local .omx/state.

Operational steps

  1. Split the environment into teamName and workerName; Send a startup ACK before task work: 
    omx team api send-message --input '{"team_name":"<teamName>","from_worker":"<workerName>","to_worker":"leader-fixed","body":"ACK: <workerName> initialized"}' --json
  2. Read <team_state_root>/team/<teamName>/workers/<workerName>/inbox.md and take the first unblocked assignment.
  3. Read <team_state_root>/team/<teamName>/tasks/task-<id>.json; APIs use the bare numeric task_id (for example "1").
  4. Claim before editing: 
    omx team api claim-task --input '{"team_name":"<teamName>","task_id":"<id>","worker":"<workerName>"}' --json
  5. Do the assigned work. Do not write task lifecycle fields directly.
  6. Complete or fail through the lifecycle API, from in_progress to completed or failed: 
    omx team api transition-task-status --input '{"team_name":"<teamName>","task_id":"<id>","from":"in_progress","to":"completed","claim_token":"<token>","result":"<evidence>"}' --json
    Use release-task-claim only to requeue a blocked task to pending.
  7. Check and acknowledge mailbox messages: 
    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
  8. Write idle status after the transition: <team_state_root>/team/<teamName>/workers/<workerName>/status.json with {"state":"idle","updated_at":"<ISO timestamp>"}.

Exit and evidence

Completion evidence names the task id, changed artifacts, verification performed, and any blocker. ACKs, task transitions, mailbox acknowledgements, and status writes must be observable through the Team API/state files. On shutdown, follow the lead's inbox instructions and write the required shutdown acknowledgement before exiting.

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

ai-slop-cleaner

무료

Clean up working code by identifying duplication, dead code, unnecessary layers, and error paths that hide failures. Preserve behavior with targeted tests, simplify the requested files in stages, and report verification results and remaining risks.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Simplify bloated or repetitive AI-generated code
  • Remove unused code and unnecessary wrappers
  • Review fallback paths that hide errors
Yeachan-Heo/oh-my-codex3.4만2026년 10월 20일 업데이트

analyze

무료

Investigate repository behavior, architecture, or possible causes without changing files. Trace relevant code and supporting material, then rank explanations by evidence and confidence, with concrete file references and clear distinctions between observations, conclusions, and unresolved questions.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Investigate possible causes of a bug
  • Understand behavior across multiple files
  • Explain architecture and tradeoffs
Yeachan-Heo/oh-my-codex3.4만2026년 10월 20일 업데이트

ask

무료

Ask Claude or Gemini through a locally installed command-line tool for focused questions, reviews, brainstorming, or second opinions. Save the prompt, original response, summary, and next steps in a reusable Markdown file.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Get a second opinion on a proposed approach
  • Ask Claude or Gemini to review work
  • Save brainstorming results for later use
Yeachan-Heo/oh-my-codex3.4만2026년 10월 20일 업데이트

autopilot

무료

Take an idea or issue through requirements clarification, reviewed planning, implementation, and verification. Supervise all stages in one recoverable OMX workflow, preserving artifacts and progress so work can resume or return to planning when findings require changes.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Deliver an issue from requirements clarification through verification
  • Turn an initial idea into a reviewed implementation plan
  • Resume interrupted work from its saved phase
Yeachan-Heo/oh-my-codex3.4만2026년 10월 20일 업데이트

autoresearch

무료

Run a persistent research workflow with a defined goal and explicit acceptance checks. It saves progress and finishes only when a recorded result passes either a validation script or an architect review of the research output.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Research with explicit acceptance criteria
  • Verify research results with a script
  • Require review approval before completing research
Yeachan-Heo/oh-my-codex3.4만2026년 10월 20일 업데이트

autoresearch-goal

무료

Find the replacement for a research command removed in OMX 0.21. This migration notice directs existing autoresearch-goal usage to $autoresearch, the canonical research loop that requires validation before proceeding.

한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.

  • Check the replacement for a removed research command
  • Update requests to use $autoresearch
  • Confirm which command owns the research mission lifecycle
Yeachan-Heo/oh-my-codex3.4만2026년 10월 20일 업데이트

Yeachan-Heo의 스킬 모두 보기

이 스킬의 문제 신고