CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

worker

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

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Critical

Do not install without reviewing

The canonical home for this skill is worker in Yeachan-Heo/oh-my-codex

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is an exceptionally lean, fully executable protocol: eight sequenced operational steps with copy-paste-ready CLI commands, exact file paths and JSON payloads, and explicit claim/lease validation checkpoints with escalation paths on failure. It is well organized into four sections with no padding and no explanations of concepts Claude already knows.

DimensionReasoningScore

Conciseness

The body is lean and operational throughout — no explanations of concepts Claude already knows, no padded sections; every sentence carries protocol detail (claim tokens, lease renewal intervals, evidence requirements). It matches anchor 5's "every token earns its place" and sits above anchor 4, which would require trimmable over-explanation that is absent here.

5 / 5

Actionability

Five complete, copy-paste-ready `omx team api` bash commands with full JSON inputs (send-message, claim-task, renew-task-claim, transition-task-status, mailbox-list/mark-delivered), exact state-file paths, and exact status.json payloads cover all common cases — anchor 5's "fully executable; copy-paste ready". The only deferred item, the `with_task_lease` wrapper invocation, lives in the generated inbox instructions the skill explicitly points to.

5 / 5

Workflow Clarity

Eight clearly sequenced lifecycle steps (ACK → inbox → task read → claim → work → transition → mailbox → idle) with explicit validation checkpoints and error-recovery paths: "verify they match the task file", "If they differ or the lease has expired, stop and ask the leader", "If renewal fails, stop editing and contact the leader; expired claims cannot be revived", and the wrapper's "validates both API success layers". This matches anchor 5's explicit validation with feedback/escalation loops; anchor 4 would require missing checkpoints, which are not missing.

5 / 5

Progressive Disclosure

A 44-line single-file skill organized into four clear sections (When to use, Inputs and preconditions, Operational steps, Exit and evidence) with no bundle files to split out — it qualifies for 5 under the under-50-lines exception for well-organized sections. Its only external pointers (the `AGENTS.md` invariants section and `with_task_lease` in the generated inbox instructions) are clearly signaled and one level deep, not anchor 4's "minor organization gaps".

5 / 5

Total

20

/

20

Passed

Description

62%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is concise and names a distinct, well-scoped niche with three concrete protocol components (ACK, mailbox, task lifecycle). However, it lacks an explicit "Use when..." trigger clause — the "for tmux-based OMX teams" qualifier only weakly implies invocation conditions — and its keywords are jargon-heavy without natural-language variations, limiting discoverability.

Suggestions

Add an explicit trigger clause, e.g., "Use when a session starts as an OMX Team worker (OMX_TEAM_WORKER is set)" to answer "when" directly and lift completeness.

Include natural-language variations of the jargon, such as "claim and complete assigned tasks", "acknowledge messages", or "coordinate with a team leader", to improve trigger-term quality.

Use action verbs for the enumerated capabilities (e.g., "Sends startup ACKs, claims and transitions tasks, acknowledges mailbox messages") to sharpen specificity.

DimensionReasoningScore

Specificity

"Team worker protocol" names the domain and the parenthetical "(ACK, mailbox, task lifecycle)" lists three concrete protocol components, matching anchor 4's "several specific actions; minor gaps" — though the items are nouns rather than action verbs and omit lease renewal and status writes. It is clearly above anchor 3's "1-2 concrete actions" but the noun-style enumeration and coverage gaps keep it from anchor 5.

4 / 5

Completeness

The "what" is clear ("Team worker protocol (ACK, mailbox, task lifecycle)"), but there is no "Use when..." clause; "for tmux-based OMX teams" is a scope qualifier that only weakly implies when to invoke it — anchor 3, and the guideline capping completeness at 3 without explicit trigger guidance applies. Not anchor 4 because that anchor expects an explicit "Use when" clause equivalent.

3 / 5

Trigger Term Quality

Terms like "ACK", "mailbox", "task lifecycle", and "tmux-based OMX teams" are domain-accurate but jargon-heavy, offering no natural-language variations or synonyms a user might say — matching anchor 3's "some relevant keywords but missing common variations". Not anchor 4 because keyword coverage lacks the natural phrasings (e.g., "team worker", "acknowledge messages", "claim tasks") that would broaden triggering.

3 / 5

Distinctiveness Conflict Risk

"Team worker protocol ... for tmux-based OMX teams" carves out a clear niche with distinct triggers (OMX, tmux, worker, ACK, mailbox) that is unlikely to fire for unrelated skills, matching anchor 5's "clear niche with distinct triggers; minimal conflict risk". The "worker" qualifier further distinguishes it from any sibling leader/coordination skill in the same suite.

5 / 5

Total

15

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

Yeachan-Heo/oh-my-codex

Path

plugins/oh-my-codex/skills/worker/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.