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.

60

Quality

69%

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
SKILL.md
Quality
Evals
Security

Quality

Content

85%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 highly actionable and lays out a clearly sequenced, validation-gated workflow with strong feedback loops, and it is well-structured for a self-contained skill. The main weakness is verbatim repetition of the completion handoff across three sections, which costs conciseness.

Suggestions

State the completion handoff once authoritatively (e.g. in the Completion Gate) and reference it from the Contract and Agent Loop instead of repeating all four steps verbatim three times.

Consider extracting the lifecycle contract (create_goal / update_goal / /goal clear semantics) into a short reference table to cut the duplicated prose between the Completion Gate and Lifecycle paragraphs.

DimensionReasoningScore

Conciseness

The body is dense and operational with no padding about concepts Claude already knows, but the multi-step completion handoff (update_goal complete -> get_goal -> omx performance-goal complete --codex-goal-json -> /goal clear) is restated nearly verbatim across the Contract, Agent Loop, and Completion Gate/Lifecycle sections, which is unnecessary repetition that could be tightened; this fits 'mostly efficient but includes some unnecessary explanation' rather than 4's 'minor instances'.

3 / 5

Actionability

Provides copy-paste-ready CLI commands with real flags and a concrete example objective/evaluator ("Reduce CLI startup latency by 20%", "npm run perf:startup"), covers create/start/checkpoint across pass/fail/blocked/complete, and names exact tool calls (get_goal, create_goal, update_goal({status: "complete"})); matches 'fully executable; copy-paste ready commands covering common cases'.

5 / 5

Workflow Clarity

A numbered Agent Loop with an explicit validation gate ('No optimization work may start until an evaluator command and pass/fail contract exist'), pass/fail/blocked checkpoints, and a Completion Gate requiring lastValidation.status==pass plus a matching get_goal snapshot constitutes explicit validation steps with error-recovery feedback loops, matching the top anchor; validation is present so the destructive/batch cap does not apply.

5 / 5

Progressive Disclosure

The skill is a compact, self-contained body (~64 lines) with no bundle files and no nested references, organized into clearly signaled sections (Contract, CLI, Agent Loop, Completion Gate, Lifecycle); per the simple-skill guidance a well-organized self-contained skill with no need for external references scores at the top, and it does not fall to 4 since there are no organization gaps or buried references.

5 / 5

Total

18

/

20

Passed

Description

53%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 is specific and distinguishes a clear niche, but it relies heavily on internal jargon and omits any explicit 'when to use' trigger guidance, capping completeness. Adding a concrete trigger clause and a couple of natural synonyms would lift the weaker dimensions.

Suggestions

Append a 'Use when ...' clause naming natural triggers, e.g. 'Use when a user asks to optimize performance and wants an evaluator-gated goal loop rather than a one-off review.'

Soften jargon with one or two natural synonyms users actually say (e.g. 'speed up', 'reduce latency') alongside 'performance optimization'.

List 1-2 more concrete actions (e.g. 'creates an evaluator contract, records pass/fail checkpoints, completes on a passing audit') instead of the single composite verb 'Run a workflow'.

DimensionReasoningScore

Specificity

Quotes "Run an evaluator-gated performance optimization workflow over Codex goal mode with durable OMX artifacts and safe goal handoffs" — names the domain plus a couple concrete mechanisms (evaluator-gating, durable artifacts, goal handoffs), but offers only one composite verb ("Run a workflow") rather than a list of concrete actions, so it sits at the 'domain + 1-2 concrete actions' anchor and not at 4's 'several specific actions'.

3 / 5

Completeness

Provides a clear 'what' (run an evaluator-gated optimization workflow) but no 'Use when...' clause or equivalent trigger guidance, so per the boundary guidance completeness is capped at 3 and cannot reach 4's 'both what and when'.

3 / 5

Trigger Term Quality

Contains the natural phrase "performance optimization" but is otherwise dominated by internal jargon ("Codex goal mode", "OMX artifacts", "evaluator-gated", "goal handoffs"), and is missing common synonyms a user might say ("speed up", "faster", "latency"); this matches 'some relevant keywords but missing common variations' rather than 2's near-total absence of natural terms.

3 / 5

Distinctiveness Conflict Risk

The specialized framing ("Codex goal mode", "durable OMX artifacts", "safe goal handoffs") carves a clear niche with only minor overlap risk against a generic performance-optimization skill; it does not reach 5 because it lacks an explicit distinct trigger phrase like the anchor's 'Use when working with PDFs'.

4 / 5

Total

13

/

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.

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