Database
Database management and queries
postgresql-scaling
by pluginagentmarketplace
Scale PostgreSQL - partitioning, connection pooling, high availability
postgresql-extensions
by pluginagentmarketplace
Essential PostgreSQL extensions - pg_stat_statements, pg_trgm, PostGIS
postgresql-plpgsql
by pluginagentmarketplace
Write PL/pgSQL - functions, procedures, triggers, error handling
postgresql-json
by pluginagentmarketplace
Work with JSONB data - queries, indexing, transformations
postgresql-fundamentals
by pluginagentmarketplace
Master PostgreSQL SQL fundamentals - data types, tables, constraints, schema design
postgresql-advanced-queries
by pluginagentmarketplace
Master advanced PostgreSQL queries - CTEs, window functions, recursive queries
write_sql
by srsubramanian
"Write and execute SQL queries against the database with query optimization, validation, and dialect-aware syntax"
syncable-entity-runner-and-actions
by twentyhq
Implement action handlers for executing workspace migrations in Twenty. Use when creating database operations for syncable entities, implementing universal-to-flat entity transpilation, or handling create/update/delete actions in the runner layer.
generate-migration
by getsentry
Generate Django database migrations for Sentry. Use when creating migrations, adding/removing columns or tables, adding indexes, or resolving migration conflicts.
wiki-query
by paperclipai
Use when an LLM Wiki operation issue asks a question. Answer from wiki pages and raw sources with citations, name gaps plainly, and offer to file durable synthesis when the answer should compound.
chronicle
by microsoft
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting session data.
lightdash-analytics
by lightdash
Use when answering business questions, exploring governed metrics, querying Lightdash data, or creating Lightdash charts and dashboards through the Lightdash MCP server.
sql-queries
by anthropics
Write correct, performant SQL across all major data warehouse dialects (Snowflake, BigQuery, Databricks, PostgreSQL, etc.). Use when writing queries, optimizing slow SQL, translating between dialects, or building complex analytical queries with CTEs, window functions, or aggregations.
db-migrations
by lobehub
'Use for database rollout strategy, Drizzle migrations, online index creation, data backfills, migration regeneration, sequence conflicts after rebase, idempotent SQL review, or migration renames.'
code-review
by vectorize-io
Review changed code against project standards. Checks for missing tests, dead code, type safety, lint issues, and coding conventions. Run after completing any implementation work.
explorer
by supabase
Build and modify Studio Explorer surfaces, including notebooks, chats, SQL snippets, query cells, and their shared toolbar patterns.
clickhouse-logs-queries
by supabase
Write, review, and migrate Supabase logs queries against the ClickHouse-backed logs table (the logs.all.otel analytics endpoint). Use this whenever a task involves Logs Explorer SQL, the log_attributes map, querying a log source (edge_logs, postgres_logs, auth_logs, etc.), translating an old BigQuery cross join unnest(metadata) logs query to ClickHouse, or wiring analytics log SQL in apps/studio/data/logs and apps/studio/components/interfaces/Settings/Logs. Reach for it even when the user just says "logs query", "Logs Explorer", or pastes a BigQuery logs query to convert, not only when they name ClickHouse.
telemetry-standards
by supabase
PostHog event tracking standards for Supabase Studio. Use when adding
safe-sql-execution
by supabase
Use whenever code will build, return, fetch, or execute SQL that runs against a user's real Postgres database — even when the request reads like an ordinary feature or bug fix and never says "security," "injection," or "SafeSqlFragment." This covers: writing or editing any pg-meta function, query builder, or endpoint that builds/returns SQL for database objects (tables, views, functions, DB triggers, indexes, RLS policies); interpolating a schema/table/column/search/route-param value into SQL text; storing, fetching, or re-running SQL that round-trips from the database (a policy's definition, a function/view definition, a snippet's saved content); and any "Run"/"Apply"/"Execute" action that sends SQL to a project's database (SQL editor run-selection, policy editor apply, snippet runner). Load this BEFORE writing such code, not only when reviewing a finished diff. Skip only for changes that never touch SQL text or execution — styling, unrelated data hooks, non-SQL form validation, or UI layout work.
cloudflare
by cloudflare
Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF, DDoS), and infrastructure-as-code (Terraform, Pulumi). Use for any Cloudflare development task. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.
backend-patterns
by affaan-m
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
clickhouse-io
by affaan-m
ClickHouse database patterns, query optimization, analytics, and data engineering best practices for high-performance analytical workloads.
planning-and-task-breakdown
by addyosmani
Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.
supabase-postgres-best-practices
by supabase
"Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query."