ClawHub

database-migrations

v1.0.0

Safe, zero-downtime database migration strategies — schema evolution, rollback planning, data migration, tooling, and anti-pattern avoidance for production systems. Use when planning schema changes, writing migrations, or reviewing migration safety.

⭐ 0· 929·5 current·5 all-time
by@wpank
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
✓
Purpose & Capability
The skill's name and description (database migration patterns and safety) match the SKILL.md content. It does not request unrelated binaries, environment variables, or config paths.
✓
Instruction Scope
Runtime instructions are purely procedural guidance, examples, SQL snippets, and CI examples related to migrations. They do not instruct the agent to read system files, steal secrets, call external endpoints, or perform actions outside migration planning and testing.
✓
Install Mechanism
There is no install spec and no code files — the skill is instruction-only. The README contains suggested manual install commands (including an npx line pointing at a GitHub path), but those are documentation only and not an automated install step in the registry metadata.
✓
Credentials
The skill declares no required environment variables, credentials, or config paths. The guidance does reference common tooling (docker, npm, migration CLIs) in examples, which is expected and proportionate.
✓
Persistence & Privilege
always is false and the skill has no install-time persistence, does not modify other skills, and does not request elevated presence or system configuration changes.
Assessment
This skill is an instruction-only reference for safe, zero-downtime migrations and appears internally consistent. It doesn't request secrets or install code, so risk is low. Before using the SQL/CI examples in production: review and adapt queries to your schema, test on staging with production-like data and backups, and never blindly run suggested commands. Also be cautious when using any README-provided install commands that pull code (e.g., npx or copying from remote locations): confirm the source repository and content before executing those commands. If you need higher assurance, ask the publisher for a homepage or source repository to verify provenance.

Like a lobster shell, security has layers — review code before you run it.

latestvk97889q2nnjzhr4w78q5g29vtx80wcxf

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments