From adde1f0534721939cf169361bc7681897a675a1b Mon Sep 17 00:00:00 2001 From: Rishikesh Balaji Date: Tue, 8 Sep 2026 17:47:11 -0700 Subject: [PATCH] Remove run_migration guidance from PostgreSQL skill --- plugins/shared/skills/resources_postgresql/SKILL.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/plugins/shared/skills/resources_postgresql/SKILL.md b/plugins/shared/skills/resources_postgresql/SKILL.md index 9cfbc09..91086fc 100644 --- a/plugins/shared/skills/resources_postgresql/SKILL.md +++ b/plugins/shared/skills/resources_postgresql/SKILL.md @@ -28,7 +28,6 @@ description: Implements PostgreSQL connections, SQL queries, and migration patte - `mcp__resources__postgresql_psql` — Execute read-only SQL queries and psql backslash commands (`\dt`, `\d`, `\di`, `\df`, etc.). Args: `resourceId`, `command`, `timeoutMs?` - `mcp__resources__postgresql_invoke` — Execute write SQL against managed or external PostgreSQL resources. Args: `resourceId`, `sql`, `params?`, `timeoutMs?`, `description` -- `run_migration` on the platform MCP server — Run tracked migrations on an application's managed database in app-building/orchestrator sessions. Args: `applicationId`, `migration`, `description` ## TypeScript Client @@ -50,7 +49,6 @@ if (result.ok) { - Use parameterized queries (`$1`, `$2`, ...) — never interpolate values into SQL strings - `psql` is read-only; use `postgresql_invoke` for data modifications against managed or external PostgreSQL resources -- Use `run_migration` for tracked schema migrations on an application's managed database - The TypeScript client supports full read/write operations regardless of managed status - Use `psql` exclusively for read-only tasks. Never use invoke for read only.