schema-evolution-and-contract-migrations — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited schema-evolution-and-contract-migrations (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Use this skill when a schema change can ripple through pipelines, models, dashboards, or external consumers. It helps agents make schema evolution deliberate, compatible, and recoverable.
Do not treat schema changes as isolated SQL edits. They are compatibility events.
Decide whether it is:
Include:
Options may include:
| Rationalization | Reality |
|---|---|
| "It is just a column rename." | Renames break dashboards, notebooks, and joins that depend on the old name. |
| "Consumers will update quickly." | Some consumers are undocumented or owned by other teams. |
| "Additive changes are always safe." | New columns can still change file contracts, schemas, and downstream assumptions. |
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.