Skip to content
Back to skills

Os Eval Backport

ASecurity

Reviews a completed os-eval-runner lab run and backports approved changes to master plugin sources. Trigger with "backport the eval results", "review the lab run", "apply eval improvements to master", "check what the eval agent changed".

  • 7 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 2, 2026
ai-agentsbashgit

Security analysis

A100/100

Pro scans all 7 files and shows the line behind each finding

Scanned October 3, 2026

npx -y skills add richfrem/agent-plugins-skills --skill os-eval-backport --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Os Eval Backport?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Os Eval Backport
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/richfrem-os-eval-backport/badge)](https://www.skillsdirectory.com/skills/richfrem-os-eval-backport)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: os-eval-backport
plugin: agent-agentic-os
description: >
  Reviews a completed os-eval-runner lab run and backports approved changes to master
  plugin sources. Trigger with "backport the eval results", "review the lab run",
  "apply eval improvements to master", "check what the eval agent changed".
argument-hint: "[lab-repo-path] [master-plugin-path] [--baseline-commit <sha>]"
allowed-tools: Bash, Read, Write
---

# Backport Reviewer (`os-eval-backport`)

Reviews evaluation changes from an experimental lab repo and backports approved modifications to master plugin sources in `agent-plugins-skills`.

## Contents

- [Critical Constraints](#critical-constraints)
- [Quick start](#quick-start)
- [Workflow](#workflow)
- [Verification](#verification)
- [References](#references)

## Critical Constraints

1. **No Blind Copies**: Understand the rationale and eval score delta behind each lab change before applying.
2. **Hub-First Updates**: Edit only canonical sources in `plugins/<plugin>/`; spokes are managed symlinks.
3. **Preserve Valid Constraints**: Never backport changes that remove or weaken safety guards.

## Quick start

Inspect the git diff of the lab repository against its baseline:

```bash
git -C <lab-repo-path> diff <baseline-commit> HEAD
```

## Workflow

1. **Intake & Scope**: Determine lab repo path, master plugin path, and baseline commit SHA.
2. **Progress Audit**: Read `<lab-repo>/LOG_PROGRESS.md` and check evaluation logs.
3. **Assess Diff**: Classify changed files as `ACCEPT`, `ADAPT`, `REJECT`, or `REVIEW`.
4. **Apply Approved Changes**: Apply targeted diffs to master sources in `plugins/<plugin>/`.
5. **Debrief & Capture**: Record operational learnings via `os-memory-manager`.

## Verification

Run test suites and audits against modified master plugin sources:

```bash
git diff plugins/<plugin>/
```

## References

- [detailed-reference.md](references/detailed-reference.md) — Intake questions, assessment table formats, and source mapping.
- [acceptance-criteria.md](references/acceptance-criteria.md) — Backport criteria and verification standards.
- [fallback-tree.md](references/fallback-tree.md) — Remediation pathways when lab diffs conflict or fail tests.

Files in this skill

  • SKILL.md8.5 KB
  • evals/evals.json860 B
  • evals/results.tsv172 B
  • references/acceptance-criteria.md42 B
  • references/os-eval-backport-phase-guide.md51 B
  • references/os-eval-backport-phases.mmd47 B
  • references/os-eval-backport-sequence.mmd49 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…