ce-optimize

Run deterministic experiments against a shared measurement harness to select the best code variant.

Updated Mar 14, 2026
One-click install
npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill ce-optimize-andreicr1
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ce-optimize
Source: https://github.com/Andreicr1/netz-analysis-engine/tree/main/.gemini/skills/ce-optimize
Command: npx skills add https://github.com/Andreicr1/netz-analysis-engine --skill ce-optimize-andreicr1

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

ce-optimize enables teams to systematically search and optimize code or configuration spaces by running deterministic experiments against a shared measurement harness, collecting guardrail metrics, and preserving the best-performing variants for deployment. It coordinates multi-step evaluation, including baseline measurement, hypothesis backlog, judge-based qualitative scoring when needed, and robust state persistence to ensure durability across long-running sessions.

Core Features & Use Cases

  • Iterative optimization loops: define a measurable goal, run parallel experiments, and converge toward the best solution.
  • Hard metrics or LLM-as-judge evaluation: choose objective scales or semantic quality scoring as needed.
  • Guardrails and persistence: enforce degenerates gates, maintain an experiment log, and resist data loss across crashes.
  • Evolves from baseline to best: automatically updates the best-known configuration and supports safe rollbacks.

Quick Start

Start with the hard-spec baseline from references/example-hard-spec.yaml and the judge-spec from references/example-judge-spec.yaml, run with serial execution, then review the baseline and readiness before proceeding.

Frequently Asked Questions about ce-optimize

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

FAQPage Schema
How do I systematically optimize code and configuration spaces using iterative experiments?▼

Systematic optimization of configuration spaces uses deterministic experiments against a shared measurement harness to evaluate variants, collecting guardrail metrics and preserving the best-performing configurations for deployment.

Can I use LLM-as-judge for qualitative scoring when optimizing search relevance?▼

LLM-as-judge evaluation supports qualitative scoring for search relevance or clustering outcomes, allowing semantic quality assessment when objective hard metrics are insufficient for measuring optimization progress.

What's the best way to start performance tuning with an optimization spec and measurement harness?▼

Performance tuning begins with a defined hard-spec baseline and optional judge-spec, running serial execution to establish baseline measurements and verify readiness before proceeding with parallel experiments.

How do guardrails and robust state persistence handle crashes during long-running optimization loops?▼

Guardrails enforce degenerates gates and maintain an experiment log, while robust state persistence resists data loss across crashes to ensure durability throughout long-running optimization sessions.

Does this approach work for both performance tuning and clustering relevance optimization?▼

This approach applies to performance tuning, clustering, search relevance, and any measurable outcome where iteration and guardrails provide value, adapting to diverse optimization targets through configurable measurement harnesses.

When should I not use metric-driven optimization for my codebase?▼

Metric-driven optimization requires a defined optimization spec and measurable outcomes; it is unsuitable when qualitative goals cannot be formalized into either hard metrics or LLM-judge evaluation criteria.