CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ulw-execute

Executes a written ulw-plan work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents. Use when the user says ulw-execute or asks to run a .omo/plans plan.

Quality

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

70%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 content is exceptionally actionable and the workflow is rigorously sequenced with validation gates, feedback loops, and explicit stop conditions — top marks on both. Its weaknesses are a monolithic structure with zero progressive disclosure (harness routing tables, adversarial class definitions, and JSON schemas all inlined in SKILL.md) and significant redundancy, with the subagent backoff protocol stated twice and several 150+ word run-on sentences that hurt token efficiency and readability.

Suggestions

Extract stable, versioned detail into one-level-deep reference files — e.g. references/codex-harness-routing.md for the V1/V2 spawn-surface rules and references/ultraqa-classes.md for the 9 adversarial classes — leaving SKILL.md a lean overview with clearly signaled links.

Deduplicate the subagent reliability guidance: the backoff protocol (double wait timeouts, WORKING/BLOCKED signals, fallback conditions) appears nearly verbatim in both 'Codex Harness Tool Compatibility' and 'Codex Subagent Reliability'; state it once. Likewise, 'If a code block below conflicts with this section, this section wins' repeats three times and can be said once.

Break up the 150+ word run-on sentences (especially the [~] blocked-state rule and the phase-landing rules) into bulleted sub-rules so the stop conditions and cascading effects are scannable instead of buried mid-sentence.

DimensionReasoningScore

Conciseness

The body is noticeably verbose with real redundancy: the subagent backoff protocol (double wait timeouts, WORKING/BLOCKED signals, 'treat a running child as alive') is stated in full twice (lines 29 and 44), and 'If a code block below conflicts with this section, this section wins' repeats three times (lines 21, 23, 25). Single sentences balloon past 150 words — the [~] handling rule in Phase 4 packs stop conditions, cascading blocks, and ledger protocol into one run-on sentence — forcing re-reads. It avoids explaining concepts Claude already knows, so it sits above the 1 anchor but clearly at 2.

2 / 5

Actionability

Guidance is fully executable: exact JSON schemas for boulder.json and the DoneClaim/AdversarialVerify contract, literal commands (`git worktree add <repo>-wt/<plan>-<wave>`, `curl -i` against the live endpoint, `bun script/qa/web-terminal-visual-qa.mjs --title "<surface>" ...`), a concrete delegation-router table mapping difficulty to agent categories, explicit numeric stop conditions (third failed attempt, 4-hour bound), and exact spawn-tool call signatures. Copy-paste-ready material covers the common cases — the 5 anchor.

5 / 5

Workflow Clarity

The multi-phase process (Select plan → Boulder state → Execute → Verify and record → Mark progress → Completion) is clearly sequenced with five explicit verification gates per checkbox and mandatory validation before any checkbox closes. Feedback loops are thorough: non-confirmed verdicts re-dispatch with the exact failure signature, harness failures get a dedicated repair dispatch, and blocked checkboxes cascade to dependents with defined ledger entries. Explicit error-recovery checkpoints satisfy the 5 anchor.

5 / 5

Progressive Disclosure

The body is well-organized with clear headers, tables, and numbered phases, but it is a ~260-line monolith with no bundle files at all: the Codex V1/V2 harness-compat routing section (~40 dense lines), the delegation router, the 9 ultraqa adversarial classes, and the JSON contracts are all inlined content that clearly belongs in one-level-deep reference files. This matches the 3 anchor ('some structure but... content that should be separate is inline') — structure is genuinely good, but nothing is split out.

3 / 5

Total

15

/

20

Passed

Description

87%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.

A strong description: it states a concrete capability set with named state mechanisms and an explicit, command-level trigger clause. Minor room remains in broadening trigger synonyms and enumerating more of the execution lifecycle (verification gates, PR delivery), but it clearly communicates both what the skill does and when to use it with low conflict risk.

DimensionReasoningScore

Specificity

The description names the core action ("Executes a written ulw-plan work plan") and several concrete capabilities ("Boulder state, evidence ledger, worktree discipline, and parallel subagents"), matching the 'several specific actions; minor gaps' anchor. It stops short of a comprehensive action inventory (e.g. no mention of PR delivery, verification gates, or delegation routing), so it does not reach the 5 anchor.

4 / 5

Completeness

Both halves are explicit: the 'what' is concrete ("Executes a written ulw-plan work plan with Boulder state, evidence ledger, worktree discipline, and parallel subagents") and the 'when' gives concrete trigger phrases ("Use when the user says ulw-execute or asks to run a .omo/plans plan"), matching the 5 anchor exactly. Not below: neither half is vague or merely implied.

5 / 5

Trigger Term Quality

Triggers include natural phrases the target user would say: "says ulw-execute", "asks to run a .omo/plans plan", plus the plan vocabulary ("ulw-plan", ".omo/plans"). Coverage is good but misses common variations such as 'resume the plan', 'continue the work plan', or 'worktree delivery', placing it at the 4 anchor rather than 5.

4 / 5

Distinctiveness Conflict Risk

Niche terms ("ulw-plan", "Boulder state", ".omo/plans", "ulw-execute") are highly distinctive and unlikely to fire for unrelated skills; the trigger names the exact command. The only adjacency is the sibling ulw-plan skill, but the description consistently frames this skill as the executor, not the planner, so conflict risk is minimal — the 5 anchor.

5 / 5

Total

18

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

referenced_paths_exist

Referenced path issues: 1 possibly missing (references/planning.md)

Warning

Total

14

/

16

Passed

Repository

code-yeongyu/lazycodex

Path

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