ultrawork

Sunset stub — use $team instead

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/ultrawork/SKILL.md

Quality

Content

96%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 exemplary sunset stub: lean, unambiguous, and immediately actionable, with a clear migration instruction and rationale for the removal. The only structural flaw is the orphaned references/agent-tiers.md file that no part of SKILL.md points to.

Dimension	Reasoning	Score
Conciseness	Every line earns its place: removal notice with version, redirect, a two-sentence rationale, and a one-line migration instruction. The version number ("OMX 0.21") sits inside what is effectively a deprecation section ("Ultrawork — removed"), so the time-sensitive-info guideline is satisfied. Not 4 — there is nothing to trim.	5 / 5
Actionability	"Migration: replace `$ultrawork` with `$team`" is fully concrete and executable for a single-step migration, and "Task: {{ARGUMENTS}}" shows how the original request is carried over. Per the scoring notes, an instruction-only skill with actionable guidance is not penalized for lacking code.	5 / 5
Workflow Clarity	This is a single-action skill and that action is unambiguous: replace the removed command with $team. The simple-skill exception applies; no destructive or batch operations exist, so no validation checkpoint is required.	5 / 5
Progressive Disclosure	The body is well organized for its size and needs no external references, but the bundle ships references/agent-tiers.md which is never linked or signaled from SKILL.md — an orphaned file that is unreachable by navigation. That is a minor organization gap (anchor 4), not 5, since the actual bundle structure leaves a reference buried.	4 / 5
	Total	19 / 20 Passed

Description

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

This is a deprecation stub whose description does the minimum: it identifies itself as removed and names the replacement. It fails as a capability description — no actions, no trigger terms, no use-when guidance — which is a functional (if intentional) limitation of a sunset stub.

Suggestions

Add trigger coverage so users invoking the old name or parallel-execution language still route correctly, e.g. "Sunset stub — $ultrawork was removed; use $team for parallel execution, worker panes, or multi-agent dispatch."

State the 'what' explicitly in third person (e.g. "Redirects removed $ultrawork invocations to $team") so the skill's actual function is described rather than only its status.

Include a brief 'Use when...' clause (e.g. "Use when a prompt or config references $ultrawork") to satisfy the completeness requirement.

Dimension	Reasoning	Score
Specificity	The description names a concrete replacement target ("use $team instead") and labels itself a "Sunset stub", but lists zero capability actions — it describes a status, not what the skill does. Not 1 because it is not pure abstract fluff; not 3 because no concrete actions of any kind are named.	2 / 5
Completeness	The 'what' is a vague status label ("Sunset stub") with a redirect, and there is no 'when' clause or equivalent trigger guidance at all, capping completeness per the guidelines. Not 3 because a clear 'what' is absent — no function is described, only a removal notice.	2 / 5
Trigger Term Quality	"$team" is one relevant keyword, but natural phrases users would say ("parallel", "workers", "run tasks concurrently", "dispatch") are entirely missing. Anchor 2 (one or two generic keywords, missing the natural phrases) fits; anchor 3 would require broader relevant keyword coverage.	2 / 5
Distinctiveness Conflict Risk	It is distinct as a tombstone, but with no trigger terms it could be pulled in place of (or alongside) the very skill it points to, "$team". Somewhat specific with real overlap risk with the closely related $team skill — between anchors 3 and 4, closer to 3 given the routing ambiguity.	3 / 5
	Total	9 / 20 Passed

Validation

100%

Warnings & errors only

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: Yeachan-Heo/oh-my-codex
Path: skills/ultrawork/SKILL.md
Commit: 1dcf513

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.