database

Provision and manage PostgreSQL databases with production read-only safety controls.

Updated Dec 1, 2025
One-click install
npx skills add https://github.com/KartikSharma4448/MyPortfolio --skill database-kartiksharma4448
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: database
Source: https://github.com/KartikSharma4448/MyPortfolio/tree/main/.local/skills/database
Command: npx skills add https://github.com/KartikSharma4448/MyPortfolio --skill database-kartiksharma4448

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps developers and operators manage PostgreSQL databases securely, check status, and run queries with safety checks, reducing debugging time and preventing unsafe actions in production.

Core Features & Use Cases

  • Check database provisioning and status to confirm availability.
  • Create and verify databases for projects, with safe defaults.
  • Execute SQL queries with safety controls across development or production read-only environments.
  • Guardrails for production: prevents destructive or unauthorized changes to production data.

Quick Start

Query the development database with a safe SELECT to view sample data.

Frequently Asked Questions about database

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

FAQPage Schema
How do I safely query a PostgreSQL production database without risking data changes?

To safely query a PostgreSQL production database, you need a system that enforces read-only rules and environment isolation. This approach prevents destructive or unauthorized changes while allowing you to access live data.

How do I check the provisioning status of a PostgreSQL database?

Checking PostgreSQL database provisioning status involves running a status check to confirm availability. This verifies that your database is correctly provisioned and ready for secure querying or management actions.

Can I create new PostgreSQL databases with safe defaults for development?

Yes, you can create and verify PostgreSQL databases for projects using safe defaults. This ensures new development environments are securely provisioned with explicit safety rails applied from the start.

What are the limitations when executing SQL queries across development and production contexts?

Executing SQL queries across development and production contexts has limitations including enforced parameter validation and environment isolation. Production environments are strictly read-only, safeguarding sensitive information from destructive modifications.

What is the best way to manage PostgreSQL databases securely across different environments?

The best way to manage PostgreSQL databases securely is applying environment isolation, parameter validation, and explicit safety rails. This enforces read-only rules on production while allowing safe SQL execution in development.