Database Migrations Agent Skill

Design, review, and execute safe database schema changes and data backfills with zero-downtime compatibility staging and lock-aware…

Context cost
525 tokensestimated from the bundle, loaded when it triggers
Bundle
1 file · 2.1 kBtext throughout, nothing executable
Licence
MITthe author’s own terms
Last change
—no release on file
Servers it uses
Noneruns standalone

What it does

Design, review, or execute application database schema and data migrations with existing-tool fidelity, compatibility staging, lock-aware rollout, recoverability, and isolated verification. Use for schema, data backfill, or migration pipeline changes.

What this skill changes about the agent has not been set out here as a list. Its SKILL.md, shown below, says it in the author’s own words.

database
Filed under

Databases

The skill itself

A skill is instructions the model reads, and here they are in full: the front matter loads with every session, and the body below it loads when the skill triggers.

SKILL.md2.1 kB
--- name: database-migrations ---
6# Database Migration Engineering
7
8## 使用范围
9
10用于数据库 schema 变更、数据回填、迁移脚本和迁移流水线审查。先确认数据库类型与版本、迁移工具、当前 schema、数据规模、流量模式、部署顺序和备份/恢复能力;不得在不了解这些事实时选择 DDL 语法或假定事务行为。
11
12## 工作方式
13
14- 将迁移视为一次跨版本发布,而非单个 SQL 文件。先识别旧应用、旧 schema、新应用和新 schema 在发布窗口内如何并存,并采用适合的 expand–migrate–contract 或项目既有策略。
15- 使用现有迁移工具的命名、顺序、校验和与执行模型。迁移内容保持确定、可审查且尽量小;避免把环境特定判断、临时凭据或不可控外部调用混入迁移。
16- 评估 DDL 锁、索引创建、表重写、长事务和数据量对线上延迟的影响。大规模回填应分批、可观测、可暂停,并定义重复执行或中断后的恢复语义。
17- 向后兼容阶段不要立即删除旧列、改写枚举含义或收紧仍被旧版本写入的约束。收缩操作须在所有读写方迁移完成、数据验证通过后独立进行。
18- 回退优先考虑恢复到已知可用状态和数据完整性;并非所有变更都适合简单的 down migration。对不可逆操作说明备份、快照或补偿计划。
19- 在与目标版本接近的隔离数据库上测试全新安装、升级、失败中断和必要的应用兼容性。生产执行前确认目标环境、备份状态、变更窗口和审批。
20
21## 交付与边界
22
23交付应包含变更目的、受影响对象、版本兼容策略、性能/锁风险、数据验证、恢复方案和实际测试结果。具体 ORM、数据库方言、云数据库操作和生产执行命令由项目技能与运维流程决定。
24
This is the whole of SKILL.md. Install the skill to get it and everything beside it.
In the file
SKILL.md76 words
Files1
LicenceMIT
Why you can read it

Nothing in a skill executes. The client loads the text and the model follows it, so a skill can be audited the way a runbook is — by reading it.

What it costs in context

Skills are not billed by the call. They are paid for in context: every token the instructions occupy is a token your code, your diff and your conversation cannot use. Here is what this one takes and when it takes it.

≈70
always loaded
The name and description, so the model knows the skill exists and when to reach for it.
455
on trigger
The instruction body, read only when the skill fires.
0.26%
of a 200k window
Ten skills this size would take about 3% of the window before you open a file.
050k100k150k200k context window

525 tokens, estimated from the bundle at four bytes to the token, held for the rest of the session once it triggers. Small enough to keep loaded permanently without thinking about it.

Servers bill, skills cost

A server charges by the month. A skill charges once per session, in context, and then keeps charging it for as long as the session lives.

Before and after

The same question, put to the same model twice: once as it comes, and once with these instructions loaded.

No worked example has been published for this skill yet.

The procedure it runs

The procedure has not been set out here step by step. It is in the body of its SKILL.md, shown in full above.

Prose, not code

These steps are written for a model to follow, not executed by a runtime. It can still be told to skip one, and it will say so when it does.

Servers it uses

None. This skill calls no MCP servers at all.

Everything it needs is in the instructions, so it works in a project with nothing connected — the model reads the file and changes how it works with what it can already reach.

Its SKILL.md does not declare which tools it asks the agent for, so what it touches is whatever the instructions themselves ask for — read them before you install it.

What it asks for
Writes filesnot declared
Network accessnot declared

This SKILL.md carries no allowed-tools line, so neither is declared. A skill grants no permissions of its own — it can only ask for tools your client already has.

What it will not do

Every skill is narrow, and the useful ones say where they stop. These are the jobs this one is the wrong tool for.

What this skill is not for has not been published here. Nothing is implied by that: it is a section the author has not filled in.

What is in the bundle

1 file, 2.1 kB on disk. A bundle is text throughout: the instructions the model reads, plus the templates it fills in.

  • SKILL.md2.1 kB
What is not in it

No dependencies and nothing executable: a skill is text the agent reads, so the bundle is 1 file you can review in full before installing. The MIT licence covers the templates and examples as well as the instructions.

Install

Installing copies the bundle into your project. Nothing runs at install time — the files sit on disk until the model reads them.

# Database Migrations · 525 tokens when loaded · macOS, Linux mkdir -p .claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/weiweimhy-database-migrations/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/database-migrations" ] && { [ ! -e .claude/skills/database-migrations ] || { mv .claude/skills/database-migrations "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/database-migrations" .claude/skills/ && echo "Installed .claude/skills/database-migrations"
On Windows, or any OS with Node 20+
npx mcprush@latest skill add weiweimhy/database-migrations

Windows PowerShell says 'running scripts is disabled on this system'? Run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or type npx.cmd instead of npx (codex.cmd, gemini.cmd, grok.cmd likewise). PowerShell 7 needs neither. Writes to .claude/skills/database-migrations/ in the current project. For every project instead, run mkdir -p ~/.claude/skills && t=$(mktemp -d) && curl -fsSL -o "$t/bundle.tar.gz" https://mcprush.com/api/skills/weiweimhy-database-migrations/bundle.tar.gz && tar -xzf "$t/bundle.tar.gz" -C "$t" && [ -d "$t/database-migrations" ] && { [ ! -e ~/.claude/skills/database-migrations ] || { mv ~/.claude/skills/database-migrations "$t/.previous" && echo "Previous copy moved to $t/.previous"; }; } && mv "$t/database-migrations" ~/.claude/skills/ && echo "Installed ~/.claude/skills/database-migrations" (macOS, Linux) — or add --global to the npx line. The curl line replaces .claude/skills/database-migrations/ only after the download succeeds, so files left there by another skill of the same name, or by an older release, do not mix in. A copy already there is moved aside, not deleted, and the line prints where.

Which clients pick it up on their own

A skill is a folder of text. Most of these read a skills folder and pick it up without being told; the rest take the same folder another way — an upload in the app, a parameter on an API call — and then choose it by its description just the same.

Claude Code.claude/skills/
Claude DesktopCustomize › Skills
ChatGPTSkills › Create › Upload
Cursor.cursor/skills/
VS Code.github/skills/
Codex CLI.agents/skills/
Gemini CLI.gemini/skills/
Grok Build.grok/skills/
Microsoft CopilotSkills › Upload a skill
PerplexityComputer › Skills › Upload a skill
DeepSeek Harness.dsh/skills/
Zed.agents/skills/
Devin Desktop.devin/skills/
Windsurf (legacy).windsurf/skills/
OpenAI Agents SDKInstructions or sandbox Skills
HTTP / APIa request parameter
This release
Versionnot versioned
Publishedno release date on file
PriceFree
Referenceweiweimhy/database-migrations

Versions

Its author publishes no version number, so there is nothing here to pin to: what you install is the folder as it stands today. Instructions change more often than APIs do — a skill can be rewritten entirely without anything it depends on moving.

Pinning

Nothing to pin to: this skill carries no version number of its own. What you install is what the folder holds on the day you install it.

Reviews

—no reviews yet

Nobody has reviewed this skill yet. The rating is the mean of the reviews written here, so there is none until somebody writes the first.

Sign in to review it

A review is tied to an account so it can be answered, edited and taken down by the person who wrote it.

Sign in
Who can post

Anybody with an account, one review each. It carries the version that was current when you wrote it, and the publisher may reply once.

Publisher
Servers0
Claim this skill