calibration-goal

Drives the offline 7-phase calibration loop to convergence across turns and HPC waits.

Updated Aug 28, 2026
One-click install
npx skills add https://github.com/jingtao-lbl/A2MC --skill calibration-goal-jingtao-lbl
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: calibration-goal
Source: https://github.com/jingtao-lbl/A2MC/tree/main/.claude/skills/calibration-goal
Command: npx skills add https://github.com/jingtao-lbl/A2MC --skill calibration-goal-jingtao-lbl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Interactive coding agents are turn-based and cannot block for the days an HPC ensemble takes, so a multi-phase model calibration loop stalls between turns. This Skill acts as the run-to-convergence driver: it loads the persisted WorkflowStateOffline, resolves the next action, dispatches to the matching phase skill, saves state, and repeats until Phase-7 CONVERGED or a loop limit. ## Core Features & Use Cases - State-driven dispatch: Loads WorkflowStateOffline, calls resolve_next_action(), and routes to phase0 through phase6 skills, round-close steps, or housekeeping without re-implementing them. - Three valid stops only: Classifies every turn end as done (converged), wait (HPC ensemble in flight with monitors armed), or gate (one of four human decision forks), preventing silent halts with work outstanding. - Harness-neutral operation: Runs on any coding agent using only on-disk state, AGENTS.md rule 10, and whatever re-invocation trigger the harness provides, with no dependency on platform-specific features. - Use Case: A researcher calibrating an EcoSIM or PFLOTRAN site case says "keep calibrating until the targets are met"; the driver advances phases, pauses at the Phase-6 converge/redesign fork and curated-KB write gates, waits through HPC ensembles, and produces the final converged configuration. ## Quick Start Tell the agent to run the calibration to convergence for the current site case and let it drive the phase loop until the validation targets are met.

Frequently Asked Questions about calibration-goal

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

FAQPage Schema
How do I run a model calibration to convergence with an AI agent?▼

Invoke the calibration-goal driver and it loads the latest WorkflowStateOffline, resolves the next action, dispatches to the matching phase skill, saves state, and repeats. It stops only at convergence, an HPC wait, or one of four human decision gates.

What is the difference between calibration-goal and a single phase skill?▼

A phase skill executes exactly one phase of the 7-phase workflow, while calibration-goal is the conductor that sequences all phases, round-close steps, and housekeeping across turns until the calibration converges or hits a loop limit.

Does the calibration driver work with agents other than Claude Code?▼

Yes, the driver is harness-neutral and runs on any coding agent using only on-disk workflow state, AGENTS.md rule 10, and whatever re-invocation mechanism the harness provides. Platform features like stop-guards are optional hardenings, never requirements.

What happens when an HPC ensemble is still running during calibration?▼

The driver classifies this as a valid WAIT stop: it arms HPC monitors and ends the turn cleanly instead of polling. A monitor event, human continue, or scheduler trigger re-invokes the loop when the ensemble finishes.

When does the calibration loop pause for human decisions?▼

It pauses at four gates: the Phase-6 converge/redesign/stop-model-dev fork, curated knowledge-base writes, expensive or irreversible actions like full-ensemble redesigns, and standing hard stops such as destructive or ambiguous instructions.