Use when querying data with Ecto.Query DSL including where clauses, joins, aggregates, preloading, and query composition. Use for building flexible database queries in Elixir applications.
Use when Elixir Ecto patterns including schemas, changesets, queries, and transactions. Use when building database-driven Elixir applications.
Use when Django ORM patterns with models, queries, and relationships. Use when building database-driven Django applications.
Use when working with SQLite databases in Bun. Covers Bun's built-in SQLite driver, database operations, prepared statements, and transactions with high performance.
Use when defining and working with Ecto schemas including field types, associations, and embedded schemas. Use when modeling database entities in Elixir.
Use when lINQ query and method syntax, deferred execution, and performance optimization. Use when querying collections in C#.
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Based on Supabase best practices.
SQL development best practices for writing efficient, secure, and maintainable database queries
Master SQL query optimization, indexing strategies, and EXPLAIN analysis to dramatically improve database performance and eliminate slow queries. Use when debugging slow queries, designing database...
MySQL development best practices for schema design, query optimization, and database administration
PostgreSQL development best practices for schema design, query optimization, and database administration
Generate read-only database queries for GregoryAI's PostgreSQL database — Django ORM or raw SQL. Use this skill whenever someone asks to query, count, filter, aggregate, export, or analyse data in the GregoryAI database. This includes questions like "how many articles were added last month", "show me trials by subject", "which sources haven't fetched anything recently", "articles with high ML prediction scores", "list authors with ORCID", or any ad-hoc data exploration against the gregory, subscriptions, or sitesettings models. Also trigger when someone asks for data exports, CSV dumps, or reporting queries. If the question could be answered by querying the database, use this skill.
SQL query optimization patterns including EXPLAIN plan analysis, index strategies, query rewriting, and N+1 query prevention. Use when optimizing slow database queries, analyzing query performance, designing indexes, or debugging database bottlenecks. Works with PostgreSQL, MySQL, SQLite, and other SQL databases. Typical improvements: 10x-1000x query speedup.
Use when setting up SQL database services with Kysely in a Pikku app. Covers @pikku/kysely (base), @pikku/kysely-postgres, @pikku/kysely-mysql, @pikku/kysely-sqlite — channel stores, workflow services, secret services, AI storage, agent runs, and deployment services. TRIGGER when: code uses Kysely, PikkuKysely, KyselyChannelStore, KyselyWorkflowService, KyselySecretService, or user asks about SQL database setup, Postgres/MySQL/SQLite with Pikku. DO NOT TRIGGER when: user asks about MongoDB (use pikku-mongodb) or Redis (use pikku-redis).
Analytics engineering for reliable metrics and BI readiness. Use when building dbt models, defining metrics, or designing analytics layers.
SQL optimization for OLTP systems: EXPLAIN analysis, indexing, schema design, migrations, HA, and security across major SQL platforms.
Design normalized database schemas with tables, relationships, indexes, and constraints for any application domain.
Analyze, diagnose, and optimize slow SQL queries using EXPLAIN plans, indexing strategies, query rewriting, and ORM tuning.
Generate optimized SQL queries from natural language requests, supporting SELECT, JOIN, GROUP BY, window functions, CTEs, and subqueries.
Writes and modifies sqlc queries for the xmtpd PostgreSQL database. Use when creating, editing, or reviewing .sql query files in pkg/db/sqlc/, when the user mentions sqlc, database queries, or adding new database operations.
Create and modify Dataverse tables, columns, relationships, forms, and views using the Python SDK and Web API. Use when: "add column", "create table", "add relationship", "lookup column", "create form", "create view", "modify form", "FormXml", "SavedQuery", "option set", "picklist", "MetadataService", "EntityDefinitions". Do not use when: writing data records (use dv-data), reading or querying records (use dv-query), exporting solutions (use dv-solution).
Run read-only SQL queries against a PostgreSQL database via CLI. Use when user needs to query, inspect, or retrieve data from a Postgres database.
