Schema Evolution And Contract Migrations logo

Schema Evolution And Contract Migrations

Community
vaquarkhan
schema-evolution-and-contract-migrations

Guides agents through schema changes and contract migrations. Use when adding, renaming, removing, or changing columns, data types, nullability, keys, or downstream-facing data contracts.

Overview

Publishervaquarkhan
Repositorydata-engineering-agent-skills
Skill nameschema-evolution-and-contract-migrations
Stars
60
Forks
8
Bundled files
Instructions only
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by vaquarkhan on GitHub. Read the source before you install it.

Installation

Install the Schema Evolution And Contract Migrations AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/schema-evolution-and-contract-migrations
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/vaquarkhan/data-engineering-agent-skills.git /tmp/data-engineering-agent-skills
mkdir -p .claude/skills
cp -r /tmp/data-engineering-agent-skills/skills/schema-evolution-and-contract-migrations .claude/skills/schema-evolution-and-contract-migrations
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Schema Evolution And Contract Migrations in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Schema Evolution And Contract Migrations on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Schema Evolution And Contract Migrations is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Schema Evolution And Contract Migrations

Overview

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.

When to Use

  • changing input or output schemas
  • renaming or dropping columns
  • changing data types or nullability
  • adding keys or changing grain
  • migrating consumers from an old contract to a new one

Do not treat schema changes as isolated SQL edits. They are compatibility events.

Workflow

  1. Classify the change. Decide whether it is:

    • additive
    • backward compatible
    • breaking
    • temporary dual-schema support
  2. Map consumers and blast radius. Include:

    • upstream producers
    • downstream models
    • dashboards
    • APIs or extracts
    • external consumers
  3. Create the migration path. Options may include:

    • dual writes
    • compatibility views
    • phased deprecation
    • explicit consumer cutover windows
  4. Validate old and new contracts during the transition.

  5. Remove deprecated paths only after confirmation that consumers moved.

Common Rationalizations

RationalizationReality
"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.

Red Flags

  • no consumer inventory exists
  • breaking changes ship without transition support
  • type changes are made without data validation
  • deprecation timing is based on hope instead of confirmation

Verification

  • The change type and compatibility level are classified
  • Consumers and blast radius are identified
  • A migration and rollback path exists
  • Old and new contract behavior are validated during transition

Frequently asked questions

What does the Schema Evolution And Contract Migrations AI skill do?

Guides agents through schema changes and contract migrations. Use when adding, renaming, removing, or changing columns, data types, nullability, keys, or downstream-facing data contracts.

Why use Schema Evolution And Contract Migrations on TypingMind?

Because you install it once and use it with any model. Schema Evolution And Contract Migrations is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Schema Evolution And Contract Migrations in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/vaquarkhan/data-engineering-agent-skills/tree/main/skills/schema-evolution-and-contract-migrations. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Schema Evolution And Contract Migrations?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Schema Evolution And Contract Migrations?

As many as you like. As long as a model supports skills, you can use Schema Evolution And Contract Migrations with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Schema Evolution And Contract Migrations AI skill free?

Yes. It is published on GitHub by vaquarkhan under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇