CtrlK
BlogDocsLog inGet started
Tessl Logo

ulw-loop

Goal-like loop that uses ultrawork mode to decompose work into systematic, evidence-bound steps.

58

Quality

67%

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

Quality

Content

100%

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

The body is a lean, actionable overview that delegates the full workflow to a single clearly-signaled reference file. It provides concrete commands and explicit validation checkpoints without explaining concepts Claude already knows.

DimensionReasoningScore

Conciseness

The body is deliberately compact ('This skill is intentionally compact') and dense with operational rules, assuming Claude's competence without explaining git, agents, or CLI basics. Every section earns its tokens rather than padding.

3 / 3

Actionability

It gives concrete, copy-paste-ready guidance: real CLI commands ('omo ulw-loop create-goals', 'git rev-parse --short "HEAD^{tree}"') and full spawn_agent/wait_agent call signatures in the tool-mapping table. This matches the fully-executable anchor.

3 / 3

Workflow Clarity

Multi-step work is explicitly sequenced (Required First Steps, Non-Negotiables) with validation checkpoints and feedback loops: evidence bound to a tree, re-run at current HEAD when the tree differs, and 'record only after cleanup receipts exist'. This matches the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

SKILL.md is a compact overview that clearly signals one-level-deep navigation into references/full-workflow.md (a real file in ./references/), with well-organized sections and no nested-reference chaining. This matches the clear-overview-with-well-signaled-references anchor.

3 / 3

Total

12

/

12

Passed

Description

35%

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 states a clear purpose but leans on internal jargon and omits any explicit 'Use when...' trigger guidance. It is serviceable but not user-facing in its trigger language.

Suggestions

Reword the description to use natural trigger terms a user would actually say (e.g. 'Use when the user asks for durable goal execution, checkpointed delivery, or evidence-led long-running work').

Add concrete actions the skill performs (register goals, mirror steps into a live checklist, capture evidence bound to a git tree) to lift specificity toward the top anchor.

Add an explicit 'Use when...' clause naming both natural keywords and the distinguishing scenario to raise completeness and distinctiveness.

DimensionReasoningScore

Specificity

Names the domain ('ultrawork mode') and some actions ('decompose work into systematic, evidence-bound steps'), but the action list is not comprehensive. It sits at the 'names domain and some actions' anchor rather than the multiple-concrete-actions level.

2 / 3

Completeness

It states what the skill does but has no 'Use when...' clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2. It is not a 1 because the 'what' is clearly stated.

2 / 3

Trigger Term Quality

The terms ('Goal-like loop', 'ultrawork mode', 'evidence-bound steps') are internal jargon a user would not naturally say, matching the 'technical jargon or overly generic' anchor. No common natural variations are present.

1 / 3

Distinctiveness Conflict Risk

The ultrawork framing gives it a niche, but the jargon-heavy phrasing could still overlap with generic goal/loop or execution skills, matching the 'somewhat specific but could still overlap' anchor rather than a clearly distinct niche.

2 / 3

Total

7

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
code-yeongyu/lazycodex
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.