calibrate

Review and merge calibration drift entries from beads memory into agent calibration files.

1|Updated May 15, 2026
One-click install
npx skills add https://github.com/mslshao/claude-harness --skill calibrate-mslshao
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: calibrate
Source: https://github.com/mslshao/claude-harness/tree/main/dotclaude/skills/calibrate
Command: npx skills add https://github.com/mslshao/claude-harness --skill calibrate-mslshao

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill closes the loop on agent learning by turning queued calibration drift entries into reviewed updates instead of leaving them stranded in memory. It helps you safely maintain agent calibration files when subagents can suggest changes but are not allowed to edit those files directly.

Core Features & Use Cases

  • Human-gated calibration review: Presents each drift entry alongside the current calibration state so you can merge, reject, or defer it.
  • Structured merge workflow: Maps memory keys to the right calibration sections, handles new rules versus refinements, and writes accepted changes to the calibration file and append-only lookback log.
  • Cleanup and reconciliation: Deletes processed memory keys and warns about stale scratch files tied to fallback workflows.
  • Use case: After an autopilot or subagent-assisted session produces calibration drift notes, use this Skill to review what the agent learned and decide which behavioral adjustments should become part of its lasting calibration.

Quick Start

Run the calibrate skill to review pending drift entries for mx2-decision-maker and choose whether to merge, reject, or keep each one.

Frequently Asked Questions about calibrate

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

FAQPage Schema
How do I review and merge agent calibration drift from subagent memory?

You can review agent calibration drift by querying memory entries in JSON mode and applying human-gated approval to merge, reject, or defer behavioral updates into calibration files. Accepted changes are written to calibration files and an append-only lookback log.

What is agent calibration drift and when do I need to manage it?

Agent calibration drift consists of queued behavioral updates, rule overrides, threshold changes, and false positives or negatives emitted by subagents. You need drift management when subagents learn during sessions but lack direct write access to calibration files.

How do I update agent calibration files with human approval using a review workflow?

Update agent calibration files by presenting each drift entry alongside current calibration state, then choosing to merge, reject, or defer. The workflow maps memory keys to calibration sections and writes accepted changes to the file and lookback log.

Does the calibration review workflow support cleaning up processed memory keys and scratch files?

Yes, the calibration review workflow deletes processed memory keys after merging and warns about stale scratch fallback artifacts. This cleanup prevents processed drift entries from accumulating and ensures scratch files are safely reconciled.

Can I use this workflow to handle rule overrides and threshold adjustments for subagents?

Yes, you can use this workflow to handle subagent rule overrides, threshold adjustments, false positives, false negatives, and dismissals. It maps these drift entries to calibration sections as either new rules or refinements.