os-eval-backport

Backport approved lab-eval changes to master plugin sources with traceability.

5|3|Updated Feb 21, 2026
One-click install
npx skills add https://github.com/richfrem/agent-plugins-skills --skill os-eval-backport
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: os-eval-backport
Source: https://github.com/richfrem/agent-plugins-skills/tree/main/plugins/agent-agentic-os/skills/os-eval-backport
Command: npx skills add https://github.com/richfrem/agent-plugins-skills --skill os-eval-backport

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reviews a completed os-eval-runner lab run and backports approved changes to master plugin sources.

Core Features & Use Cases

  • Intake and analysis of lab eval results to identify approved changes
  • Safe, deliberate edits to the canonical sources within the agent-plugins-skills repository
  • Fully traceable backport workflow with phase gating and review checkpoints

Quick Start

Backport approved eval changes from a lab run into the master plugin sources.

Frequently Asked Questions about os-eval-backport

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

FAQPage Schema
How do I backport approved lab eval changes to master plugin sources?

Backport approved lab eval changes by applying patches only to the canonical master sources in the agent-plugins-skills repository with deliberate edits and full traceability. You provide the lab repo path, the master plugin path, and an optional baseline commit for context.

What inputs do I need to port lab-eval changes to canonical master sources?

Porting lab-eval changes to master sources requires the lab repository path and the master plugin path as mandatory inputs. An optional baseline commit can also be provided to give additional context for the deliberate edit workflow.

How does traceability work when applying approved patches to master sources?

Traceability during backporting is maintained through a workflow with phase gating and explicit review checkpoints. This ensures that only approved lab-eval changes are deliberately applied to the canonical master sources.

Can I use a baseline commit when porting eval results into the agent-plugins-skills repository?

Yes, you can use an optional baseline commit to provide context when porting approved changes. This helps anchor the deliberate edits made to the canonical master sources within the agent-plugins-skills repository.

What is the safest way to apply lab-eval patches to master sources?

The safest way to apply lab-eval patches is through a deliberate backport workflow that uses phase gating and review checkpoints. This process ensures only approved changes are applied directly to the canonical master sources.