CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

worker

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

Quality

75%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/worker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

92%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 exemplary operational protocol: fully executable commands with concrete payloads, a clearly numbered lifecycle with explicit validation and failure-handling checkpoints, and well-organized sections at an appropriate single-file scale. The only minor weakness is density in the claim/lease step. Strong result — no suggestions needed.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — every step is operational instruction with no explanations of concepts Claude already knows. It falls short of 5 only because step 4 packs the lease/renewal policy into one dense paragraph that could be tightened. It is clearly above anchor 3 since there is no genuinely unnecessary explanation.

4 / 5

Actionability

Every lifecycle stage has a copy-paste-ready command with a concrete JSON payload (send-message ACK, claim-task, renew-task-claim, transition-task-status, mailbox-list/mark-delivered) plus exact file paths and status.json schemas. This matches the anchor for fully executable, copy-paste-ready commands covering the common cases.

5 / 5

Workflow Clarity

Steps 1-8 give a clear sequence with explicit validation checkpoints and error-recovery loops: verify the inbox handoff's claim token/version/lease against the task file and stop if they differ, stop editing and contact the leader if renewal fails, and requeue via release-task-claim only for blocked tasks. This matches the top anchor (clear sequence, explicit validation, feedback loops).

5 / 5

Progressive Disclosure

This is a short (~50-line) single-file skill with no bundle directories, and per the rubric such skills can score 5 with well-organized sections. Sections (When to use, Inputs and preconditions, Operational steps, Exit and evidence) are clearly headed, and the external pointers (AGENTS.md anchor, generated inbox instructions) are one level deep and clearly signaled.

5 / 5

Total

19

/

20

Passed

Description

46%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 identifies a distinct niche (OMX team worker protocol), but it names protocol components rather than concrete actions and omits any 'when to use' trigger guidance. Per the rubric, the missing trigger clause caps completeness and weakens trigger term quality. Adding natural 'Use when...' phrasing and stating the concrete actions performed would lift most dimensions.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a session is started as an OMX Team worker' — its absence caps completeness at 3.

Convert protocol nouns into concrete actions (e.g. 'Send startup ACKs, claim and renew tasks, acknowledge mailbox messages, transition tasks through their lifecycle') to raise specificity.

Include one or two natural terms a user or leader would actually say (e.g. 'team worker', 'claim a task', 'worker heartbeat') instead of relying solely on jargon like 'tmux-based OMX teams'.

DimensionReasoningScore

Specificity

The description names the domain ('Team worker protocol') and 2-3 concrete components ('ACK, mailbox, task lifecycle'), but these are protocol nouns rather than concrete actions and coverage is not comprehensive, matching the anchor for domain plus 1-2 concrete items. It falls below anchor 4 because it does not list several specific actions, and above anchor 2 because it is more than a bare domain name.

3 / 5

Completeness

The 'what' is reasonably clear (worker protocol covering ACK, mailbox, task lifecycle), but the 'when' is entirely missing — there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the when-condition is absent rather than merely imprecise.

3 / 5

Trigger Term Quality

Phrases like 'tmux-based OMX teams', 'ACK', and 'mailbox' are technical jargon rather than natural terms a user would say when needing this skill, and no natural trigger phrases are present. This matches anchor 2 (one or two generic keywords, missing the natural phrases users say) rather than anchor 3, which requires some genuinely relevant keywords.

2 / 5

Distinctiveness Conflict Risk

The scope 'Team worker protocol ... for tmux-based OMX teams' carves out a clear niche with little overlap risk against generic skills, sitting between anchor 3 (somewhat specific) and anchor 5 (clear niche with distinct triggers). It does not reach 5 because the description provides no explicit distinct trigger phrases.

4 / 5

Total

12

/

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

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.