performance-goal

Manage Codex goal mode performance optimizations with OMX artifacts and secure goal transitions.

Updated May 25, 2026
One-click install
npx skills add https://github.com/BetaS/swm-gis-workshop --skill performance-goal-betas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: performance-goal
Source: https://github.com/BetaS/swm-gis-workshop/tree/main/.codex/skills/performance-goal
Command: npx skills add https://github.com/BetaS/swm-gis-workshop --skill performance-goal-betas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill facilitates performance optimization of Codex goal mode with OMX artifacts and secure goal handoffs, streamlining the evaluation and completion of performance objectives.

Core Features & Use Cases

  • Objective-Based Optimization: Supports goal-oriented loops for performance tuning with Codex.
  • Evaluator Contract Handling: Ensures safe transitions of performance objectives and maintains evaluator state integrity.
  • Durable OMX Artifacts: Creates long-term records of workflow state for accountability and analysis.
  • Use Case: When you need to run an optimized performance workflow for a Codex goal mode with artifacts and ensure secure goal transitions, this Skill automates the process.

Quick Start

To create a new performance optimization goal for 'Reduce CLI startup latency by 20%', execute:

omx performance-goal create --objective "Reduce CLI startup latency by 20%" --evaluator-command "npm run perf:startup" --evaluator-contract "PASS when p95 latency improves by 20% and regression tests pass" --slug startup-latency

Frequently Asked Questions about performance-goal

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

FAQPage Schema
How do I optimize Codex goal mode workflows with evaluator contracts?

Codex goal mode workflows are optimized using evaluator-contracted loops that secure objective transitions. This ensures automated performance evaluations and completion checks run safely while maintaining evaluator state integrity throughout the process.

What are durable OMX artifacts and when do I need them for performance optimization?

Durable OMX artifacts are long-term records of workflow state created during performance tuning. You need them when automating Codex performance evaluations requires accountability and historical analysis of objective-based optimization loops.

How do I create a performance optimization goal for reducing CLI startup latency?

Creating a performance optimization goal uses the omx performance-goal create command with an objective, evaluator command, evaluator contract, and slug. This initiates an automated workflow to evaluate and complete the performance target safely.

Can I automate performance evaluations and completion checks without manual intervention?

Automating performance evaluations and completion checks is supported through evaluator-contracted workflows. By defining a passing evaluator contract upfront, the system safely transitions performance objectives and verifies completion without manual intervention.

Does this approach support secure goal transitions for automated performance tuning?

Secure goal transitions are supported through evaluator contract handling during automated performance tuning. This mechanism ensures that objective handoffs maintain state integrity and prevent unsafe modifications to the evaluation criteria.

What is the best way to maintain workflow state accountability during performance optimization?

Maintaining workflow state accountability is best achieved by generating durable OMX artifacts during performance optimization. These artifacts provide a persistent record of the evaluator-contracted workflow for later analysis and auditing.