performance-goal

Runs an evaluator-gated performance optimization workflow with durable OMX goal artifacts.

Updated Feb 1, 2024
One-click install
npx skills add https://github.com/ogiboy/portfolio-app --skill performance-goal-ogiboy
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-goal
Source: https://github.com/ogiboy/portfolio-app/tree/main/.codex/skills/performance-goal
Command: npx skills add https://github.com/ogiboy/portfolio-app --skill performance-goal-ogiboy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Performance optimization work often drifts without a measurable pass/fail contract, making it impossible to know when an objective is actually done. This Skill enforces an evaluator-first loop so every optimization is validated against a declared benchmark before completion. ## Core Features & Use Cases - Evaluator-Gated Workflow: No optimization begins until an evaluator command and pass/fail contract are defined via omx performance-goal create. - Durable State Artifacts: Workflow state persists under .omx/goals/performance/<slug>/, surviving across sessions and threads. - Checkpoint Tracking: Record pass, fail, or blocked evaluator outcomes with evidence for each iteration. - Safe Codex Goal Handoffs: Coordinates with Codex goal mode (create_goal, update_goal, get_goal) without shell commands mutating hidden goal state. - Use Case: A developer wants to reduce CLI startup latency by 20%. They create the goal with a benchmark evaluator, iterate in small reversible patches, checkpoint each run, and complete only after a passing checkpoint and completion audit. ## Quick Start Ask the agent to start a performance goal for reducing startup latency by 20% using your benchmark command as the evaluator contract.

Frequently Asked Questions about performance-goal

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up a measurable performance optimization goal?

Run omx performance-goal create with an objective, an evaluator command, and a pass/fail contract. The workflow refuses to start optimization until that evaluator contract exists, ensuring every change is measured against a declared benchmark.

How do I track progress during a performance optimization loop?

Record each evaluator run with omx performance-goal checkpoint using a status of pass, fail, or blocked plus evidence. These checkpoints persist in the goal's state.json under .omx/goals/performance/<slug>/ for auditing.

Can I complete a performance goal just because tests pass?

No. Completion requires a checkpoint with status pass from the declared evaluator contract, a completion audit, and a fresh Codex get_goal snapshot passed to omx performance-goal complete. Ordinary tests only count if they are the declared evaluator.

Does this workflow modify Codex goal state from shell commands?

No. Shell commands only write OMX artifacts and emit handoff text. Codex goal state is managed exclusively through goal primitives like create_goal, update_goal, and get_goal, with /goal clear run manually in the Codex UI after completion.

What happens if the evaluator is blocked or fails?

Record the outcome with a fail or blocked checkpoint including evidence, then iterate with small reversible patches. The goal cannot be completed until a passing checkpoint exists in the state artifact.