postgres

Execute PostgreSQL queries, schema changes, and maintenance via psql.

1|Updated Feb 1, 2026
One-click install
npx skills add https://github.com/xukrutdonut/openclaw-skills --skill postgres
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: postgres
Source: https://github.com/xukrutdonut/openclaw-skills/tree/main/postgres
Command: npx skills add https://github.com/xukrutdonut/openclaw-skills --skill postgres

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

PostgreSQL database management often requires repetitive manual commands for querying, schema changes, backups, and performance checks. This Skill centralizes those tasks and provides safe defaults to reduce human error.

Core Features & Use Cases

  • Ad-hoc SQL querying and result inspection
  • Schema management and index optimization
  • Backups, restores, and basic performance monitoring
  • Use Case: You need to quickly verify the integrity of a schema after a migration and run a set of queries across multiple tables.

Quick Start

  • export DATABASE_URL="postgresql://user:pass@localhost:5432/dbname"
  • psql "$DATABASE_URL" -c "SELECT * FROM users LIMIT 5"

Frequently Asked Questions about postgres

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run safe ad-hoc SQL queries on a PostgreSQL database?

You can execute safe ad-hoc SQL queries by connecting through the psql client with a valid DATABASE_URL connection string, which applies safe defaults to reduce human error during database management.

How do I manage PostgreSQL schema changes and index tuning?

PostgreSQL schema management and index optimization are handled by executing targeted commands through the psql client, streamlining schema modifications and index tuning across development and production environments.

Do I need psql and a DATABASE_URL to perform PostgreSQL backups and performance monitoring?

Yes, performing PostgreSQL backups, restores, and basic performance monitoring requires the psql client installed and access to a valid DATABASE_URL connection string to operate across your environments.

What's the best way to verify PostgreSQL database integrity after a migration?

The best way to verify PostgreSQL database integrity after a migration is to run a set of ad-hoc queries across multiple tables using the psql client to inspect the schema and results directly.

Can I use this approach for PostgreSQL database management in both development and production?

Yes, this approach supports PostgreSQL database management across both development and production environments, enabling consistent schema modifications, backups, and performance monitoring with safe defaults.