CtrlK
BlogDocsLog inGet started
Tessl Logo

performance-goal

Run an evaluator-gated performance optimization workflow over Codex goal mode with durable OMX artifacts and safe goal handoffs.

64

Quality

80%

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

The canonical home for this skill is performance-goal in Yeachan-Heo/oh-my-codex

SKILL.md
Quality
Evals
Security

Quality

Content

88%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 a strong, self-contained workflow document: fully executable commands, a clearly sequenced agent loop with explicit validation gates, and well-organized sections. Its only weaknesses are mild redundancy in the completion procedure across sections and a slightly jargon-dense but navigable structure.

DimensionReasoningScore

Conciseness

Lean and efficient overall, but the completion procedure (update_goal, get_goal, --codex-goal-json, /goal clear) is repeated across the Contract, Agent Loop, and Lifecycle sections, and 'must not mutate hidden Codex goal state' appears twice — minor trims possible, so anchor 4 rather than 5.

4 / 5

Actionability

Fully executable, copy-paste-ready CLI commands for every lifecycle stage with concrete flag values and example evidence strings; the one placeholder (<get_goal-json-or-path>) is explicitly explained by the surrounding steps. Matches the 'fully executable; covers common cases' anchor.

5 / 5

Workflow Clarity

The numbered Agent Loop has explicit validation checkpoints (evaluator pass required before complete, pass/fail/blocked checkpoint recording as a feedback loop) and a precise Completion Gate defining the exact passing condition — the 'clear sequence with explicit validation and error-recovery feedback loops' anchor.

5 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-sectioned (Contract, CLI, Agent Loop, Completion Gate) with nothing that belongs in a separate file, but at ~64 lines it exceeds the under-50-line simple-skill threshold for a full-credit score, so anchor 4 applies.

4 / 5

Total

18

/

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.

A specific, distinctive description that clearly communicates what the skill does, but it lacks any 'when to use' trigger guidance and leans heavily on internal jargon rather than natural user phrasing. Adding an explicit 'Use when...' clause with user-facing terms would move it to the top of the scale.

Suggestions

Add a 'Use when...' clause to the description, e.g. 'Use when a user asks OMX to optimize performance and wants a goal-oriented loop rather than a one-off review' (currently that trigger guidance exists only in the body).

Include natural trigger phrasings users would actually say — 'optimize performance', 'speed up', 'reduce latency', 'benchmark' — instead of relying solely on internal terms like 'evaluator-gated' and 'durable OMX artifacts'.

Briefly enumerate the core lifecycle actions (create, start, checkpoint, complete) so the description's capability coverage is comprehensive rather than implied.

DimensionReasoningScore

Specificity

Names the domain ('performance optimization workflow') and several concrete elements ('evaluator-gated', 'durable OMX artifacts', 'safe goal handoffs'), matching the 'several specific actions; minor gaps' anchor rather than 5 because the actual lifecycle actions (create, checkpoint, complete) are not enumerated.

4 / 5

Completeness

The 'what' is clear, but there is no 'Use when...' clause or equivalent trigger guidance anywhere in the description (it only exists in the body), which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

'performance optimization' is a natural term, but 'evaluator-gated', 'Codex goal mode', 'durable OMX artifacts', and 'goal handoffs' are internal jargon, and common user phrasings like 'speed up', 'benchmark', or 'faster' are missing — the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche ('Codex goal mode', 'OMX artifacts', evaluator gating) with distinct triggers and minimal overlap risk with generic optimization skills.

5 / 5

Total

15

/

20

Passed

Validation

100%

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