Db Migrate
v1.0.0Deep database migration workflow—expand/contract, backward-compatible deploys, backfills, locking risks, and verification. Use when changing production schem...
⭐ 0· 56·0 current·0 all-time
byClawKK@codekungfu
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the content of SKILL.md: it provides a six‑stage, zero/low‑downtime migration workflow and best practices. There are no unexpected environment variables, binary requirements, or install steps that would be inconsistent with a migration advisory.
Instruction Scope
The instructions are procedural guidance (classify, expand, backfill, cutover, contract, verify). A few items suggest actions like 'search repo, logs, feature usage' which could lead an agent to read project files or logs when performing the workflow — that is consistent with migration verification, but it implicitly expects access to repo/logs and monitoring data. The SKILL.md does not itself request specific credentials or paths, and it does not include commands that perform I/O or network calls.
Install Mechanism
No install spec and no code files — instruction-only. Nothing will be written to disk or downloaded by the skill itself, which minimizes install risk.
Credentials
The skill declares no required environment variables or credentials. The guidance refers to database engines and tools (pt-online-schema-change) but does not request keys or passwords. This is proportionate to an advisory workflow. Note: if an agent acting with this skill is later provided DB credentials by the user, the workflow would naturally use them — that is not a property of the skill itself.
Persistence & Privilege
The skill is not marked always:true and is user-invocable only. It does not request persistent privileges or modify other skills or global agent settings.
Assessment
This skill is a guidance document for performing safe DB migrations and appears internally consistent. Before using it, confirm how the agent will be given access to your codebase, logs, and production database: the SKILL.md suggests inspecting repo and logs (reasonable for verification) but the skill itself does not request credentials — you should avoid pasting production DB credentials into chat. If you let the agent run actions, grant only the minimum access needed (read-only access to schema/monitoring where possible), and verify any generated migration steps before applying them. If you prefer, treat this as a checklist for a human operator rather than an autonomous agent task.Like a lobster shell, security has layers — review code before you run it.
latestvk979effcd5mbfz33axe5dd9nen83q0h9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.