improve-openui-harnesses

Manage iterative updates to OpenUI training and evaluation harnesses.

1|Updated Jul 12, 2026
One-click install
npx skills add https://github.com/Tyler-R-Kendrick/slm-training --skill improve-openui-harnesses
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: improve-openui-harnesses
Source: https://github.com/Tyler-R-Kendrick/slm-training/tree/main/.agents/skills/improve-openui-harnesses
Command: npx skills add https://github.com/Tyler-R-Kendrick/slm-training --skill improve-openui-harnesses

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a structured, fail-closed framework for modifying complex SLM training harnesses, ensuring that research experiments remain consistent, reproducible, and compliant with strict architectural invariants.

Core Features & Use Cases

  • Harness Lifecycle Management: Safely update training, evaluation, distillation, and RL harnesses without breaking lineage or promotion gates.
  • Invariant Enforcement: Ensures all changes adhere to non-negotiable decode invariants and deterministic bypass requirements.
  • Use Case: When adding a new training data source or modifying a model-build script, use this Skill to verify that the change maintains strict schema compliance, updates version stamps, and includes the necessary regression tests.

Quick Start

Use the improve-openui-harnesses skill to review the current training data harness and implement the required version bump for the latest synthesis feedback.

Frequently Asked Questions about improve-openui-harnesses

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

FAQPage Schema
How do I maintain SLM training harnesses without breaking experiment lineage?

Maintain SLM training harnesses by enforcing strict architectural invariants and deterministic decode constraints during modifications. This ensures experiment pipelines, data synthesis, and promotion gates remain consistent and reproducible across iterative updates without breaking lineage tracking or version-stamp contracts.

What is the best way to update OpenUI evaluation pipelines for new data sources?

Update OpenUI evaluation pipelines by verifying schema compliance, bumping version stamps, and adding regression tests when adding new training data sources. This structured approach enforces non-negotiable decode invariants and deterministic bypass requirements while maintaining strict lineage tracking.

How do I enforce decode invariants when modifying model-build scripts?

Enforce decode invariants in model-build scripts by using a fail-closed framework that validates all changes against non-negotiable deterministic decode constraints. This ensures schema compliance, updates version stamps, and includes necessary regression tests before any modification is promoted.

Can I use this approach for distillation and RL harness lifecycle management?

Yes, this approach supports training, evaluation, distillation, and RL harness lifecycle management. It safely updates all harness types while enforcing strict architectural invariants, version-stamp contracts, and deterministic decode constraints to maintain experiment reproducibility and compliance.

When do I need version-stamp contracts for training harness modifications?

Version-stamp contracts are required whenever modifying training, evaluation, or research harnesses, adding data sources, or changing model-build scripts. They ensure strict schema compliance, maintain lineage tracking, and enforce deterministic decode constraints across all experiment pipeline updates.