Diagnose Postgres queries and operations while separating generic behavior from PlanetScale-specific features.
Editorial review checked 2026-10-29 against this instruction snapshot. Supporting scripts and runtime behavior remain outside this editorial review.
What it does
The guide covers indexing, connection management and architecture, with additional provider-oriented references. That separation helps avoid applying a hosted-platform command to a self-managed instance or assuming a general Postgres recommendation has identical operational consequences everywhere.
Best for
Developers reviewing Postgres performance, schema design or connection problems in a known environment.
Tradeoffs and requirements
Query plans depend on data distribution, statistics and configuration. Maintenance and migration operations can affect locks and availability, and a hosted connection pool may impose semantics different from a direct session to the database.
Unknown; inspect source requirements and supporting scripts.
Install from the source
Inspect the pinned source snapshot and its supporting files first. The command selects this skill through the open-source skills CLI. Node.js and agent-specific setup may be required. Installation can download code. Catalog ingestion never executes skill instructions or install scripts.
After source review, use npx skills check and npx skills update to inspect and apply upstream updates. Re-check changed instructions before running them.
Safety & review signals
Static review only. This is not a security audit or a guarantee of safety.
SKILL.md text only; scripts, dependencies and runtime behavior not audited.
Network Access — review the source context.
Allowed tools declaration: Unknown. Runtime permissions and network behavior: Unknown.
Offline package integrity
A temporary folder-copy check, not an agent installation or runtime safety verdict.
23 files copied and checksummed from this exact source snapshot. No package code or installation scripts were executed.
Scores summarize observable discovery signals. Popularity and repository activity apply to the whole repository. Unknown runtime safety earns no certification.
Identify the server and hosting model, inspect a representative plan and gather relevant connection and workload evidence. Propose a focused query, index or pooling change, preserving transaction assumptions and a safe method for applying any persistent modification.
How to judge the result
Compare result correctness and measured latency, inspect concurrency and transaction behavior and repeat the same workload after the change. Record provider-specific steps explicitly and avoid inferring production improvement from a small local dataset or an estimated plan alone.
Similar skills to compare
Related by category; compare scope and dependencies before choosing an alternative.
Explore 360 feedback system as a data & databases workflow from sickn33/agentic-awesome-skills. Compare its source, maintenance and review signals before choosing it for your agent.
Community sourceMIT3 matching source records
Repository star change: +147 over 41.38 hours. 2026-10-31
Explore access matrix as a data & databases workflow from sickn33/agentic-awesome-skills. Compare its source, maintenance and review signals before choosing it for your agent.
Community sourceMIT3 matching source records
Repository star change: +147 over 41.38 hours. 2026-10-31
Explore adhx as a data & databases workflow from sickn33/agentic-awesome-skills. Compare its source, maintenance and review signals before choosing it for your agent.
Community sourceMIT3 matching source records
Repository star change: +147 over 41.38 hours. 2026-10-31