ultragoal

Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts.

Quality

56%

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 ./plugins/oh-my-codex/skills/ultragoal/SKILL.md

Quality

Content

77%

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

The content is highly actionable with concrete commands and a well-sequenced, validated workflow including explicit feedback loops for the final review gate. Its main weakness is conciseness and progressive disclosure: it is a long monolithic document that could be tightened and could offload detailed reference material into bundle files.

Suggestions

Move the full quality-gate JSON schema and the steering mutation-kind list into a references/ file, keeping SKILL.md as a lean overview with a one-level-deep pointer.

Tighten the legacy per-story and migration prose into a short 'Deprecated/legacy' note, since the default is aggregate mode.

Consider condensing the State/HUD phase contract into a compact table or bullet summary to reduce token weight.

Dimension	Reasoning	Score
Conciseness	The body is dense and long, devoting substantial prose to legacy per-story modes, migration, and edge cases that could be tightened, but it does not explain concepts Claude already knows, so it sits at 'mostly efficient but could be tightened' rather than the verbose level 1.	2 / 3
Actionability	It provides fully executable, copy-paste-ready commands (e.g. `omx ultragoal create-goals --brief`, `omx state write --input '{...}'`, the full checkpoint command with flags) plus a complete quality-gate JSON example, matching 'fully executable code/commands; copy-paste ready'.	3 / 3
Workflow Clarity	The 'Complete goals' 11-step loop and the 7-step 'Mandatory final cleanup and review gate' give a clear sequence with explicit validation steps (rerun verification after cleaner) and feedback loops for error recovery (non-clean review records blockers instead of calling update_goal), matching the top anchor.	3 / 3
Progressive Disclosure	The body is well-sectioned with headers, but it is a single ~180-line monolithic document with no bundle files (references/scripts/assets absent) and inline reference material (full quality-gate JSON, steering mutation kinds, constraints) that could be split out, matching 'some structure but content that should be separate is inline'.	2 / 3
	Total	10 / 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, domain-specific purpose but relies on technical jargon and omits any explicit 'Use when' trigger guidance, which limits trigger-term quality and completeness. Adding natural-language trigger terms and a when-to-use clause would materially raise the score.

Suggestions

Add an explicit 'Use when the user asks for ultragoal, create-goals, complete-goals, or durable multi-goal planning over Codex /goal' clause to the description so completeness and trigger-term quality can reach 3.

Replace jargon like 'repo-native' and 'Codex goal mode artifacts' with natural terms users would actually say (e.g. 'multi-goal plans', 'Codex goals').

List a few more concrete capabilities (e.g. create goals, checkpoint progress, steer mid-execution, run a final review gate) to move specificity from 2 to 3.

Dimension	Reasoning	Score
Specificity	"Create and execute durable repo-native multi-goal plans over Codex goal mode artifacts" names the domain and two actions (create, execute), but does not list multiple distinct concrete capabilities, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.	2 / 3
Completeness	It clearly states what the skill does but provides no 'Use when...' clause or equivalent explicit trigger guidance, so per the guidelines completeness is capped at 2 ('Has what, but when is missing or only implied').	2 / 3
Trigger Term Quality	The phrasing "durable repo-native multi-goal plans over Codex goal mode artifacts" is technical jargon with no natural keywords a user would actually say (the natural triggers like "ultragoal", "create-goals" live in the body, not the description), matching the 'technical jargon or overly generic' anchor.	1 / 3
Distinctiveness Conflict Risk	The Codex-goal-mode niche is fairly specific, but the jargony triggers and generic 'multi-goal plans' framing could still overlap with other planning skills, matching 'somewhat specific but could still overlap'.	2 / 3
	Total	7 / 12 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: plugins/oh-my-codex/skills/ultragoal/SKILL.md
Commit: 435d4a9

Reviewed: 2 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.