Skip to content

fix: correct PostgreSQL write tool documentation - #154

Merged
rishikesh-major merged 5 commits into
mainfrom
rishikesh/fix-postgresql-skill-write-tool
Sep 9, 2026
Merged

fix: correct PostgreSQL write tool documentation#154
rishikesh-major merged 5 commits into
mainfrom
rishikesh/fix-postgresql-skill-write-tool

Conversation

@rishikesh-major

@rishikesh-major rishikesh-major commented Sep 8, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • document postgresql_invoke for ordinary PostgreSQL data modifications
  • retain migration guidance using the current app-scoped orchestrator run_migration tool
  • distinguish resource writes from tracked managed-database migrations

Context

Cold Email Hackers agent runs needed ordinary UPSERT/INSERT operations but followed the PostgreSQL skill's stale instruction to use the removed postgresql_run_migration resource target. The correct resource write tool is postgresql_invoke; app-building sessions retain a separate run_migration tool for tracked managed-database migrations.

Validation

  • go test ./...
  • git diff --check

- Use parameterized queries (`$1`, `$2`, ...) — never interpolate values into SQL strings
- `psql` tool is read-only; use `run_migration` for writes (managed DBs) or the TypeScript client for writes (external DBs)
- `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 when the orchestrator tool is available

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

the orchestrator tool is always available but shouldn't be used on non-managed dbs. Docs on that live in: https://github.com/major-technology/cli/blob/main/plugins/shared/skills/resources_managed-database/SKILL.md

@rishikesh-major
rishikesh-major merged commit 6d3c33f into main Sep 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants