MySQL to PostgreSQL Migration
v1.0.1Use this skill when migrating a project's database layer from MySQL to PostgreSQL. Covers SQL dialect conversion (MyBatis XML / raw SQL), ORM configuration (...
⭐ 0· 107·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name and description match the SKILL.md content: a focused migration checklist and example fixes for JDBC, SQL dialects, types, sequences, GROUP BY, and MyBatis specifics. It does not request unrelated binaries, env vars, or access.
Instruction Scope
The instructions stay on-topic (code edits, SQL conversion patterns, config examples, run-time error troubleshooting). They recommend global search/replace and creating sequences or running SELECT MAX(id), which are expected migration activities and do not ask the agent to read unrelated system files or exfiltrate data.
Install Mechanism
No install spec or code is provided (instruction-only), so nothing is downloaded or written to disk. This minimizes execution risk.
Credentials
The skill declares no environment variables or credentials (appropriate for an instruction-only guide). In practice migrating databases requires DB credentials and access; the skill does not declare them but may lead the agent or user to supply credentials separately—this is expected but worth noting.
Persistence & Privilege
always is false and there is no installation that modifies agent/system configuration. The skill does not request persistent privileges or modify other skills.
Assessment
This is an instructional, read-only guide that appears coherent and relevant to MySQL→PostgreSQL migrations for Java/Spring/MyBatis projects. Before using it in an automated agent workflow: 1) understand that actual migration operations (creating sequences, running SELECT MAX, applying SQL changes) require database credentials—do not supply production admin credentials to an automated agent; prefer a restricted/staging account and backups. 2) Perform full backups and test migrations in staging first. 3) Review any proposed global search-and-replace operations manually or via code-review (create PRs) to avoid accidental mass edits. 4) Pay special attention to BIT vs integer handling, sequence start values, and GROUP BY changes the guide highlights. 5) If you allow the agent to act autonomously, limit its access scope and require manual approval for destructive actions. Overall the skill is coherent, but human oversight is recommended when applying its recommendations to live data.Like a lobster shell, security has layers — review code before you run it.
javavk972m99bvqdyqsm44b61efdhg583cteslatestvk973cwfp96a3nc6dz3zrbvt5nx83dzh6migrationvk972m99bvqdyqsm44b61efdhg583ctesmybatisvk972m99bvqdyqsm44b61efdhg583ctesmysqlvk972m99bvqdyqsm44b61efdhg583ctespostgresqlvk972m99bvqdyqsm44b61efdhg583ctes
License
MIT-0
Free to use, modify, and redistribute. No attribution required.