CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ultrawork

Binding ultrawork mode directive for omo on Codex. When a prompt contains ultrawork or ulw, the omo UserPromptSubmit hook injects a short bootstrap that points at this file. Read the whole file and follow every rule in it for the rest of the task.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/omo/skills/ultrawork/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 unusually dense, highly executable operational directive: exact commands, named tools, explicit validation gates, and strong feedback/stop rules make it near-copy-paste actionable. Its weaknesses are duplication across sections that inflates token cost and a monolithic single-file structure that inlines reference-grade detail (subagent routing compatibility, per-channel QA) instead of splitting it into one-level-deep bundle files.

Suggestions

Deduplicate repeated rules — state the never-clear-browser-data, tmux capture-pane, and fork_context guidance once and cross-reference it — to cut token cost without losing content.

Move the Codex subagent routing/TOML compatibility sections and the per-channel QA command details into reference files (e.g. references/subagent-routing.md, references/qa-channels.md) linked one level deep from the body.

Compress environment-specific tool-surface notes (multi_agent_v1 vs v2 differences) into a short table, since much of it restates what the spawn-tool schema itself exposes.

DimensionReasoningScore

Conciseness

Sentences are telegraphic and never re-explain concepts Claude already knows, but there is real duplication that could be tightened: the never-clear-cookies/caches warning appears in both the browser channel and Cleanup, the tmux capture-pane prohibition appears twice, and fork_context guidance is restated across three sections. Fits anchor 3 (mostly efficient but could be tightened) rather than 4, since the duplication is more than minor.

3 / 5

Actionability

Fully executable throughout: literal commands ("NOTE=$(mktemp -t ulw-$(date +%Y%m%d-%H%M%S).XXXXXX.md)", "node script/qa/web-terminal-visual-qa.mjs --title ... --command ...", "git log --oneline -20", "tmux kill-session -t ulw-qa-<criterion>"), exact tool names (create_goal, update_plan, multi_agent_v1.spawn_agent), exact env vars, and a mandated literal first line. Specific examples cover the common cases.

5 / 5

Workflow Clarity

Clear sequence with explicit validation and feedback loops: an ordered bootstrap (survey → goal → notepad → todos), an 8-step execution loop with blocking checkpoints (LSP diagnostics clean, read-back teardown receipts, rerun-what-moved), a reviewer loop with delta re-reviews, a 2-attempt stop rule, and an explicit stop-goal checklist including cleanup-state verification.

5 / 5

Progressive Disclosure

Internal section headers are clear, but the body is a monolithic ~490-line single file with no bundle references at all — the Codex subagent TOML-routing compatibility details and channel-specific QA commands (150+ lines) clearly belong in separate reference files per the one-level-deep model. Matches anchor 3 (some structure, content that should be separate is inline).

3 / 5

Total

16

/

20

Passed

Description

60%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 nails the trigger mechanics — explicit, distinctive keywords and a clear activation path via the UserPromptSubmit hook — but never states what ultrawork mode actually does, so a reader cannot judge its capabilities from the description alone. It reads as hook plumbing documentation rather than a capability summary.

Suggestions

Replace or augment the hook-mechanism sentences with a one-line capability summary, e.g. what the mode enforces (evidence-backed verification, QA channels, tiered process, review gates).

Add a 'what' clause alongside the existing explicit 'when' clause so both halves of the completeness contract are answered concretely.

Trim the bootstrap-injection mechanics (which concern the hook, not the skill's use) to make room for capability description without growing the description.

DimensionReasoningScore

Specificity

"Binding ultrawork mode directive for omo on Codex" names the domain, but the only actions described are loading plumbing ("hook injects a short bootstrap that points at this file", "Read the whole file and follow every rule") — the actual capabilities of the mode (evidence capture, QA channels, tiering, review gates) are never stated. Fits anchor 2 (domain named, actions minimal/generic) rather than 3, which requires 1-2 concrete capability actions.

2 / 5

Completeness

The "when" is fully explicit ("When a prompt contains ultrawork or ulw") but the "what" is vague — the description says to "follow every rule in it" without saying what the mode does. Anchor 3 (one of what/when weak or missing) fits better than anchor 4, whose example shows both a capability statement and a use clause.

3 / 5

Trigger Term Quality

"When a prompt contains ultrawork or ulw" gives both the full keyword and its abbreviation — exactly the strings a user would type to invoke the mode. Good coverage with few natural terms missing; not 5 because no further variants or context phrases exist beyond the two forms.

4 / 5

Distinctiveness Conflict Risk

Invented unique trigger words ("ultrawork", "ulw") scoped to a named harness ("for omo on Codex") give this a clear niche with distinct triggers and minimal conflict risk with any other skill.

5 / 5

Total

14

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

code-yeongyu/lazycodex

Path

plugins/omo/skills/ultrawork/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.