CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

ulw-loop

A goal-like loop that decomposes work into systematic, evidence-bound ultrawork steps. Use when the user wants a goal loop or durable, checkpointed execution.

Quality

68%

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/ulw-loop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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 delivers dense, highly actionable operational guidance with concrete commands, tool-call examples, and explicit validation rules, and it points cleanly to real one-level-deep references. Its main weakness is token efficiency: harness-routing rules are stated two to three times over, including one near-unreadable wall-of-text paragraph, which inflates the skill's context cost without adding information.

Suggestions

Consolidate the duplicated harness-routing guidance: state the V1/V2 tool-surface rules and the "this section wins" precedence rule once, and delete their repeats in the Non-Negotiables and Codex Tool Mapping sections.

Break the line-24 wall-of-text paragraph into a short list or move it, along with the OpenCode-to-Codex translation table, into a dedicated reference file so the SKILL.md body stays a compact overview.

Merge the repeated wait/backoff and WORKING/BLOCKED protocol bullets (lines 30 and 56-57) into a single subagent-supervision rule.

DimensionReasoningScore

Conciseness

The body duplicates the same guidance repeatedly: "If a code block below conflicts with this section, this section wins" appears three times, the wait/backoff rule and WORKING/BLOCKED protocol each appear twice, and V1/V2 tool-surface routing is explained in two separate sections (the opening compatibility section and the later Codex Tool Mapping). Line 24 is a dense wall-of-text paragraph. This is noticeably verbose with several padded, redundant passages rather than merely "could be tightened".

2 / 5

Actionability

Guidance is largely executable: exact CLI commands ("omo-agent-toolkit ulw-loop create-goals", "git rev-parse --short \"HEAD^{tree}\""), copy-paste spawn-call JSON in the mapping tables, concrete error codes (ULW_LOOP_SESSION_SCOPE_REQUIRED), and a two-condition team-mode decision rule. Minor gaps remain because key execution detail (delegation specifics, per-criterion cycle) is deferred to references without inline summaries.

4 / 5

Workflow Clarity

"Required First Steps" gives a clear numbered entry sequence naming the exact reference sections to read before acting, and validation is explicit (evidence bound to a git tree, gated checkpoint, stop rules, resume-after-compaction rule). Some checkpoints live only in the referenced workflow rather than the body, leaving minor validation gaps relative to the anchor-5 example.

4 / 5

Progressive Disclosure

The bundle structure is good: two real, one-level-deep reference files (full-workflow.md, define-goal.md), clearly signaled with phase-specific reading instructions ("Read only the sections needed for the current phase"). However, roughly 30 lines of harness-compatibility translation tables are inlined in the body and duplicated across two sections — content that belongs in a reference file — so it falls short of the clean overview anchor 5.

4 / 5

Total

14

/

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 answers both what and when with an explicit Use-when clause and a distinct niche, but it is thin on concrete capabilities and natural trigger synonyms. The jargon-heavy phrasing ("ultrawork", "evidence-bound", "checkpointed execution") limits how naturally users would trigger it.

Suggestions

List 2-3 more concrete capabilities in the what clause (e.g., plans multi-step goals, delegates code edits to subagents, records evidence per success criterion) instead of relying on the abstract "systematic, evidence-bound ultrawork steps".

Broaden the Use-when clause with natural trigger phrases and synonyms users would actually say, such as "long-running task", "resume interrupted work", or "run this to completion with checkpoints".

Replace or gloss harness jargon ("ultrawork") with plain language so the description reads naturally to users who don't know the internal terminology.

DimensionReasoningScore

Specificity

"decomposes work into systematic, evidence-bound ultrawork steps" names one concrete action, but "ultrawork" and "evidence-bound" are jargon-adjacent and no further specific actions are listed. This matches the 1-2-concrete-actions anchor, not the several-specific-actions anchor above.

3 / 5

Completeness

Both what ("decomposes work into systematic, evidence-bound ultrawork steps") and an explicit when ("Use when the user wants a goal loop or durable, checkpointed execution") are present. The when clause is explicit but narrow, with only two trigger phrases, so it falls short of the concrete-trigger-phrase anchor 5.

4 / 5

Trigger Term Quality

"goal loop" is a natural phrase, but "durable, checkpointed execution" is technical wording users would rarely say, and common variations like "long-running task", "resume work", or "checkpoint" are missing. Some relevant keywords exist, but synonym coverage is absent.

3 / 5

Distinctiveness Conflict Risk

"ultrawork" and "goal loop" carve a distinct niche with low conflict risk, but "durable, checkpointed execution" overlaps slightly with generic long-running-task or execution skills. Mostly distinct with minor overlap risk, matching anchor 4 rather than the minimal-conflict anchor 5.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

code-yeongyu/lazycodex

Path

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