CtrlK
BlogDocsLog inGet started
Tessl Logo

worker

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

59

Quality

67%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/oh-my-codex/skills/worker/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

The body is highly actionable with executable CLI templates and a clear, guarded lifecycle workflow, but it is monolithic with no file-level progressive disclosure and contains some abstract process padding that could be tightened or split out.

Suggestions

Extract the 'Team Big Five / ATEM Coordination Gate' checklist and detailed CLI interop templates into a referenced file (e.g. COORDINATION.md) to add one-level-deep progressive disclosure.

Tighten the ATEM section from abstract process philosophy ('Shared mental model', 'Mutual performance monitoring') into concrete, directive checkpoints to improve conciseness.

Add an explicit validate/retry note for the lifecycle transitions (e.g. what to do if claim-task or transition-task-status fails) to make the workflow's error-recovery path explicit.

DimensionReasoningScore

Conciseness

The body is mostly lean operational content, but the 'Team Big Five / ATEM' section reads as abstract process philosophy and 'Dispatch Discipline' restates the state-first point, so it could be tightened.

2 / 3

Actionability

It provides fully executable CLI commands with complete copy-paste JSON templates, exact file paths, env-var names, and ordered resolution lists — copy-paste ready.

3 / 3

Workflow Clarity

The task lifecycle is a clear numbered 10-step sequence with explicit guards (claim before work, no direct lifecycle writes, release-claim only for rollback) plus an ATEM checklist for complex cases.

3 / 3

Progressive Disclosure

Sections are well-labeled, but the skill is a monolithic single file over 50 lines with no external references, and inline content (ATEM checklist, CLI templates) that could be split is kept inline.

2 / 3

Total

10

/

12

Passed

Description

57%

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 clearly identifies a distinct niche and its core mechanisms, but lacks an explicit 'Use when...' trigger clause and leans on domain jargon, capping completeness and trigger-term quality at 2.

Suggestions

Add an explicit trigger clause, e.g. 'Use when a Codex session is spawned as an OMX Team worker' to satisfy the 'when should Claude use it' requirement.

Soften jargon with more natural trigger phrasing a user would actually say (e.g. 'team worker', 'task claim', 'inbox') to improve trigger-term coverage.

Reframe the mechanism list as concrete actions ('ACK the leader, read your inbox, claim and complete tasks') to lift specificity toward 3.

DimensionReasoningScore

Specificity

Names the domain and concrete mechanisms ('ACK, mailbox, task lifecycle') but as noun-phrase concepts rather than enumerated concrete actions, matching the 'names domain and some actions' anchor.

2 / 3

Completeness

It states the 'what' (the protocol) clearly, but the 'when' is only implied via 'for tmux-based OMX teams' with no 'Use when...' clause, so completeness is capped at 2 per the guideline.

2 / 3

Trigger Term Quality

Terms like 'worker', 'mailbox', 'task lifecycle', and 'ACK' are relevant within the niche but lean technical/jargon with no explicit 'Use when' trigger phrasing, so it has some relevant keywords but is missing natural trigger variations.

2 / 3

Distinctiveness Conflict Risk

It carves a very specific niche (tmux-based OMX team workers) with distinct triggers, making it unlikely to conflict with other skills.

3 / 3

Total

9

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
Yeachan-Heo/oh-my-codex
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.