Align the estate to a changed upstream Oak Open Curriculum API (OpenAPI) spec — summon on "upstream spec changed", "schema drift check fired", "refresh the schema cache", "sdk-codegen refresh", a failing correction-layer removal-condition test after an upstream deploy, or an upstream changelog entry. Drives the owning runbooks: characterise the drift first-hand (doc-only vs structural, additive vs consumer-breaking), refresh deliberately, treat correction-layer test failures as lifecycle sign...
Installs into .claude/skills of the current project.
Are you the author of Oak Update Upstream Api Spec?
Add the live security badge to your README. It updates with every re-scan.
[](https://www.skillsdirectory.com/skills/oaknational-oak-update-upstream-api-spec-oak-open-curriculum-ecosystem)
---
name: oak-update-upstream-api-spec
description: 'Align the estate to a changed upstream Oak Open Curriculum API (OpenAPI) spec — summon on "upstream spec changed", "schema drift check fired", "refresh the schema cache", "sdk-codegen refresh", a failing correction-layer removal-condition test after an upstream deploy, or an upstream changelog entry. Drives the owning runbooks: characterise the drift first-hand (doc-only vs structural, additive vs consumer-breaking), refresh deliberately, treat correction-layer test failures as lifecycle signals, re-attest the MCP content audit, verify the served descriptions, and route upstream falsehoods as bug reports. Do NOT use for the bulk-download surface (that is update-bulk-download-schema) or for building new tools against an unchanged spec. Failure shapes it exists to prevent: hand-editing generated files, blind expectation edits on red sentinel tests, loosening validation to make upstream drift pass, and skipping the content-audit re-attestation so the served surface silently diverges from its reviewed record.'
---
# Update Upstream Api Spec (Claude Code)
Read and follow `.agent/skills/update-upstream-api-spec/SKILL-CANONICAL.md`.
