General Correctness rules, Rust patterns, comments, avoiding over-engineering.
Create a database migration to add a table, add columns to an existing table, add a setting, or otherwise change the schema of Ghost's…
Generate Django database migrations for Sentry.
MySQL and MariaDB schema, query, indexing, transaction, replication, and connection-pool patterns for production backends.
Schema migrations and versioning for PocketBase.
>
PostgreSQL database patterns for query optimization, schema design, indexing, and security. Quick reference for common patterns, index types, data types, and anti-pattern detection. Based on…
High-performance vector similarity search engine for RAG and semantic search.
Use when writing Snowflake SQL, building data pipelines with Dynamic Tables or Streams/Tasks, using Cortex AI functions, creating Cortex…
Agent skill for v3-memory-specialist - invoke with $agent-v3-memory-specialist
Optimize AgentDB performance with quantization (4-32x memory reduction), HNSW indexing (150x faster search), caching, and batch operations.
Database migration best practices for schema changes, data migrations, rollbacks, and zero-downtime deployments across PostgreSQL, MySQL…
Design and implement event stores for event-sourced systems.
Authors n8n database migrations. Use when creating or modifying files under packages/@n8n/db/src/migrations/, when the user asks to add a…
Automate Turso tasks via Rube MCP (Composio).
>-
Build ClickHouse with various configurations (Release, Debug, ASAN, TSAN, etc.).
Agent skill for crdt-synchronizer - invoke with $agent-crdt-synchronizer
Schema lifecycle management for Basic Memory: discover unschemaed notes, infer schemas, create and edit schema definitions, validate…
Reduce an unoptimized-query-oracle test failure log to the simplest possible reproduction case.
Load before calling data-tables or parse-file. Use for natural standalone requests like "what data tables do I have?", "show/list my tables", or "what columns are in this table?", and whenever the…
Databases agent skills on mcprush decide how an agent is allowed to touch data: what a query has to prove before it runs, what a migration must ship with, what a table has to be profiled for before anyone charts it. The kinds are workflow, expertise, output format, voice & style and guardrail, and the one a skill belongs to is the fastest way to guess what it will do to your prompt.
What to look at before installing one is what it costs in context and what it takes away: a guardrail that refuses an action and a voice that rewrites a sentence are both skills, and only one of them will stop the agent doing something. Every skill here says which kind it is, what it costs in context, what it needs beside it to work and the licence it is published under, next to the publisher it came from and whether that publisher has been verified. The filters on the left narrow it further and the sort at the top decides what comes first.
A skill is not connected to anything: there is no endpoint to authorise and nothing routed through the gateway. Installing one drops a folder of instructions into the client’s own skill folder, and uninstalling it is deleting that folder. The exact line for each client is on the skill’s own page, because it differs by client rather than by skill.