sql-schema-placeholder

Load the full PostgreSQL schema.sql for writing and fixing SQL queries.

Updated Mar 25, 2020
One-click install
npx skills add https://github.com/daominah/gostructure --skill sql-schema-placeholder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sql-schema-placeholder
Source: https://github.com/daominah/gostructure/tree/main/.claude/skills/sql-schema-placeholder
Command: npx skills add https://github.com/daominah/gostructure --skill sql-schema-placeholder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Provides a reliable, complete PostgreSQL schema reference so developers and AI assistants can write, fix, and optimize SQL queries and migrations for the placeholder repository without guessing table structures, indexes, or foreign keys.

Core Features & Use Cases

  • Complete Schema Loading: Ensures the entire schema.sql is read into context to avoid partial or inaccurate assumptions about tables, indexes, and relationships.
  • Query and Migration Support: Use when composing or repairing SQL queries, creating migrations, or diagnosing slow queries against the placeholder project's public schema.
  • Conventions Enforcement: Encourages using full table names (no aliases) and applying sql-formatting rules to produce clear, maintainable SQL.

Quick Start

Load the full schema.sql from this skill, inspect tables, indexes, and foreign keys, and then rewrite the provided SQL query or migration to align with the schema and the no-alias convention.

Frequently Asked Questions about sql-schema-placeholder

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

FAQPage Schema
How do I fix PostgreSQL slow queries without guessing the table schema?

Fixing PostgreSQL slow queries requires loading the full schema.sql context to inspect tables, indexes, and foreign keys. This ensures query optimizations are based on actual schema structures instead of assumptions, preventing incorrect index usage or join errors.

How do I write PostgreSQL migrations that align with existing database conventions?

Writing PostgreSQL migrations involves reading the entire schema.sql file to verify table structures and foreign keys. Migrations must use explicit table naming without aliases and apply sql-formatting rules to ensure maintainable and clear database changes.

What is the best way to diagnose slow queries in a PostgreSQL public schema?

Diagnosing slow queries in a PostgreSQL public schema requires full schema context to analyze index usage and table relationships. By loading the complete schema.sql, you can identify missing indexes or inefficient joins causing the slow performance.

Do I need to load the entire schema.sql file before editing PostgreSQL queries?

Yes, editing PostgreSQL queries requires loading the entire schema.sql file. Reading the complete schema prevents partial or inaccurate assumptions about tables, indexes, and relationships, ensuring query fixes are accurate and compatible.