postgres
Postgres
Goal
Use this skill to connect to Postgres, run SQL, inspect schemas, review query
performance, design tables and indexes, work with common PostGIS or pgvector
patterns, and manage migration release flow through the shipped
scripts/postgres artifact in the skill package.
Runtime surface
- The only supported runtime entrypoint is the shipped
scripts/postgresartifact inside this skill package. - If your current working directory is the skill root, run it as
./scripts/postgres. - If you are invoking the skill from another repo, resolve the skill package
path first and run
<postgres-skill-root>/scripts/postgres. <postgres-skill-root>/scripts/postgres --versionis the runtime version check.- Do not use or reintroduce per-task helper scripts from the pre-Rust runtime
More from alemar11/skills
codex-changelog
Check the installed Codex CLI and Codex App versions, then print separate changelog sections for the CLI from GitHub Releases and the app from the OpenAI Codex changelog page.
28learn
Capture durable corrections or preferences and write confirmed learnings only to AGENTS.md. Use when the user sets lasting guidance.
27ask-questions-if-underspecified
Clarify requirements before implementing when a request is underspecified or the user asks for clarification.
24skill-audit
Audit installed or user-specified Codex skills, plugins, or bundled plugin skills using project history, repo evidence, memory, sessions, and current context to plan updates, additions, merges, or disables. Use when a user asks how their installed Codex surfaces are performing, wants a one-by-one refinement roadmap, asks to audit a skill, a plugin, or a bundled plugin skill, or wants evidence-based recommendations before changing those surfaces.
13github
Handle repo-scoped GitHub work plus authenticated-user star and star-list workflows through one repo-owned skill covering triage, reviews, CI, releases, and PR publish or lifecycle flows, with `yeet` reserved for full local-worktree publish.
12commit
Create a well-formed git commit from current changes using session history for rationale and summary; prefer explicit pathspec staging and, in monorepos, default to one subproject per commit unless the user asks for a cross-cutting commit. Use when asked to commit, prepare a commit message, or finalize staged work.
7