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

75%

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 ./packages/omo-codex/plugin/components/ulw-loop/skills/ulw-loop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

This is a well-engineered instruction-only skill: compact, jargon-free of generic explanations, with concrete commands, exact tool-call signatures, and disciplined gating of evidence and checkpoints. Its only real costs are a few overloaded run-on bullets and end-to-end loop sequencing that lives in the reference rather than the body. Progressive disclosure is exemplary, with verified, clearly-signaled one-level references.

DimensionReasoningScore

Conciseness

The body is dense and operational with essentially no padding — every rule is CLI- or harness-specific knowledge Claude would not already have (session scoping, error codes like ULW_LOOP_SESSION_SCOPE_REQUIRED, tree-hash evidence binding, tool version mapping). It misses the 5 anchor because several bullets are long run-ons (e.g., the register-goals bullet interleaving four rules in one sentence) and the team-mode rationale prose could be tightened without losing the decision criteria.

4 / 5

Actionability

Guidance is largely executable: exact commands (omo-agent-toolkit ulw-loop create-goals, --session-id, CODEX_THREAD_ID, git rev-parse --short "HEAD^{tree}"), concrete tool-call signatures in the mapping table (spawn_agent({"task_name":..., "fork_turns":"none"})), and message protocols (TASK:/DELIVERABLE/SCOPE/VERIFY, WORKING:, BLOCKED:). It stops short of 5 because some commands are named but not shown with full syntax (checkpoint --codex-goal-json, record-evidence, team_create), deferring exact usage to the reference.

4 / 5

Workflow Clarity

The Required First Steps give a clear, explicitly gated pre-flight sequence ('before running any ULW command or recording evidence', 'Goal creation is NEVER skipped'), and the delegated workflow's phases (Bootstrap, Execution Loop, Stop Rules) are named so the sequence is traceable into the reference, which itself contains gated checkpoints ('Only after that gated checkpoint succeeds'). Not 5 because the body-level view of the execute→verify→record loop is indirect — the reader must assemble the full checkpoint cadence from the reference rather than seeing an end-to-end sequence with feedback loops inline.

4 / 5

Progressive Disclosure

The body is an intentionally compact overview ('The full workflow lives in references/full-workflow.md. Read only the sections needed for the current phase') with exactly two one-level-deep references, both verified to exist, and every cited section (Bootstrap, Execution Loop, Manual-QA channels table, Stop Rules in full-workflow.md; goal shaping in define-goal.md) is actually present and clearly signaled with when to read it. Always-required rules stay inline while bulk detail is split out, matching the clear-overview anchor.

5 / 5

Total

17

/

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 cleanly answers both what and when in a compact, third-person sentence, and its niche is reasonably distinct. Its weaknesses are thin capability coverage and trigger terms that omit the skill's own invocation names (ulw-loop, ulw) and other natural phrasings users would say.

Suggestions

Add one or two more concrete capabilities to the what-clause (e.g., recording tree-bound evidence, checkpointed state under .omo/ulw-loop) so specificity moves from 'domain + 1-2 actions' toward comprehensive coverage.

Include the literal invocation names users type — 'ulw-loop', 'ulw', 'ultrawork' — and natural synonyms such as 'long-running delivery' or 'resume work across sessions' in the Use-when clause.

Replace abstract triggers like 'durable, checkpointed execution' with more concrete user-side phrasings (e.g., 'keep a long task going with checkpoints and verifiable evidence') to sharpen when-coverage and distinctiveness.

DimensionReasoningScore

Specificity

The description names the domain ("goal-like loop") and one or two concrete actions ("decomposes work into systematic, evidence-bound ultrawork steps"), matching the anchor for domain plus 1-2 actions. It is not score 4 because it does not list several specific capabilities (checkpointing, evidence recording, delegation, QA) as distinct actions, and 'systematic, evidence-bound ultrawork steps' leans on jargon rather than concrete verbs.

3 / 5

Completeness

Both parts are explicitly present: what ("A goal-like loop that decomposes work into systematic, evidence-bound ultrawork steps") and when ("Use when the user wants a goal loop or durable, checkpointed execution"). It falls short of the 5 anchor because the trigger phrases are abstract ('durable', 'checkpointed execution') rather than the concrete, varied triggers users would naturally type.

4 / 5

Trigger Term Quality

The when-clause offers some relevant natural phrases ("goal loop", "durable, checkpointed execution") but misses common variations users would actually say: the skill's own invocation names 'ulw-loop'/'ulw' (which the body lists as triggers but the description omits), 'ultrawork', and phrasings like 'long-running' or 'resume across sessions'. This matches 'some relevant keywords but missing common variations or synonyms' rather than the good-coverage anchor at 4.

3 / 5

Distinctiveness Conflict Risk

The 'goal loop' + 'ultrawork' framing carves a fairly clear niche with distinct triggers, but there is minor overlap risk with the closely related bundled 'ultrawork' skill and with generic loop/goal-execution skills, matching 'mostly distinct; minor overlap risk with closely related skills'. Not 5 because 'durable, checkpointed execution' could plausibly fire for general persistence or resume-oriented skills.

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/oh-my-openagent

Path

packages/omo-codex/plugin/components/ulw-loop/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.