Database
Database management and queries
deepsearch-service
by Lin-A1
基于 LLM 的深度迭代搜索与推理服务。擅长处理复杂问题，通过自动分解查询、多轮迭代检索、信息评估与验证，最终生成全面且结构化的深度分析报告。
@tank/desktop-app-dev
by tankpkg
Build, convert, and ship cross-platform desktop applications from web projects using Electron, Tauri v2, or Wails. Covers framework selection and automatic project detection, architecture and IPC patterns, native desktop APIs (menus, tray, notifications, file system, dialogs, shortcuts, clipboard), packaging and distribution (installers, code signing, notarization, auto-update), migration patterns (web-to-desktop conversion, Electron-to-Tauri migration), and CI/CD build pipelines. Synthesizes Electron v40 docs, Tauri v2 docs, Wails v2/v3 docs, and 2025-2026 ecosystem research. Trigger phrases: "Electron", "Tauri", "Wails", "desktop app", "desktop application", "web to desktop", "convert to desktop app", "cross-platform app", "native app", "electron-builder", "electron-forge", "electron-vite", "tauri command", "system tray", "auto-update", "code signing", "notarize", "DMG", "MSI", "AppImage", "package desktop app", "IPC", "main process", "preload script", "BrowserWindow", "wails build", "desktop wrapper", "ship desktop app", "distribute app", "Electron to Tauri", "migrate from Electron", "wrap web app"
nancy-send-message
by srobinson
Send a message to the orchestrator. Use for blockers, progress updates, requesting review, or communicating status during autonomous execution.
graphql
by samChang72
"GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully."
ensembl-database
by Victory-Hugo
查询Ensembl基因组数据库REST API，覆盖250多个物种。基因查找、序列检索、变异分析、比较基因组学、同源基因、VEP预测，用于基因组研究。
db-extractor
by famaoai-creator
Extract schema and sample data from databases for analysis.
memory
by srobinson
Persistent geometric memory across sessions. Use when the user asks about memory, wants to recall prior sessions, inspect memory, check stats, or manage memory state.
migration-observability
by dmonteroh
"Make database migrations safe and observable. Define progress + safety metrics, dashboards, and runbook gates (go/no-go criteria) for live migrations, backfills, and cutovers. Works standalone and is database/tooling agnostic."
update
by cadrianmae
Update the current development session with progress notes
@tank/google-calendar
by tankpkg
"Create, query, update, and manage Google Calendar events and availability. Covers event CRUD, free/busy queries, recurring events with RRULE, Google Meet conferencing, attendee management, multi-calendar operations, and incremental sync. Triggers: calendar, event, meeting, schedule, availability, free busy, recurring event, RRULE, Google Meet, attendee, reminder, timezone, booking, appointment, Google Calendar."
ace-serena-collaborator
by tianguzhe
Ace-Tool 与 Serena MCP 协作流程。触发场景：(1) 需要理解代码库结构 (2) 语义代码搜索 (3) 符号级代码定位 (4) 代码导航和分析。提供两阶段协作：Ace-Tool 语义搜索→Serena 精确定位，强调只读安全与工具互补。
@tank/system-design
by tankpkg
Practical system design for production distributed systems. Covers scalability patterns (load balancing, horizontal scaling, CDN, auto-scaling), data layer design (database selection, replication, sharding, consistency models, CAP theorem applied), caching strategies (cache-aside, write-through, invalidation, stampede prevention), messaging and async patterns (queues vs streams, event-driven architecture, CQRS, saga pattern, delivery guarantees), reliability (circuit breakers, bulkheads, retries, rate limiting, timeouts, chaos engineering), service architecture (monolith vs microservices, API gateway, service mesh, distributed transactions), and capacity planning (back-of-envelope estimation, SLOs/SLIs, monitoring, distributed tracing). Synthesizes Kleppmann (Designing Data-Intensive Applications), Vitillo (Understanding Distributed Systems), Newman (Building Microservices), Ford et al. (Software Architecture: The Hard Parts), Nygard (Release It!), Petrov (Database Internals), Richards & Ford (Fundamentals of Software Architecture), and Beyer et al. (Site Reliability Engineering). Trigger phrases: "system design", "distributed systems", "scalability", "load balancing", "horizontal scaling", "vertical scaling", "database sharding", "database replication", "caching strategy", "cache invalidation", "message queue", "event-driven", "Kafka", "RabbitMQ", "pub/sub", "circuit breaker", "rate limiting", "bulkhead", "retry strategy", "microservices", "monolith", "API gateway", "service mesh", "CAP theorem", "eventual consistency", "strong consistency", "CQRS", "event sourcing", "saga pattern", "back-of-envelope", "SLO", "SLI", "capacity planning", "distributed tracing", "back pressure", "cache stampede", "thundering herd", "how should I scale", "which database", "when to use microservices"
designing-relational-databases
by sumik5
Guides relational database design from requirements to implementation covering entity modeling, ER diagrams, normalization (1NF-BCNF), optimization, and PostgreSQL-specific implementation (microservices data architecture, ACID transactions, functions/stored procedures, AAA security). Use when designing database schemas, creating ER diagrams, normalizing tables, implementing SQL DDL, or developing PostgreSQL-backed applications. For database internals (storage engines, distributed systems), use understanding-database-internals instead. For SQL antipattern detection and avoidance, use avoiding-sql-antipatterns instead.
update
by cadrianmae
DEPRECATED in v2.0 - Retroactive scanning no longer needed with hooks-based tracking
mcp-terraform-connector
by famaoai-creator
status: implemented
prisma-docs
by jasonz-ncc42
Local Prisma documentation reference. Use when asked about Prisma ORM, Prisma Client, Prisma Schema, migrations, database queries, Prisma Accelerate, or Prisma Postgres.
zod-docs
by jasonz-ncc42
Local Zod documentation reference. Use when asked about Zod schema validation, TypeScript type inference, parsing, error handling, JSON Schema conversion, or schema composition.
architect-review
by dmonteroh
"Review system designs and major changes for architectural integrity, scalability, and maintainability; use for architecture decisions, tradeoffs, and risks across distributed systems and clean architecture patterns."
tofu
by poindexter12
OpenTofu infrastructure-as-code reference for HCL syntax, state management, module design, and provider configuration. Use when working with OpenTofu configurations (.tf files), running tofu commands, troubleshooting state issues, or designing modules. Includes Proxmox provider patterns. Triggers: tofu, opentofu, tfstate, .tf files, HCL, modules, providers.
stakeholder-communicator
by famaoai-creator
Output file path
normalized
by Semprini
Use this skill when the user asks for a normalized operational model, practical/pragmatic 3NF, OLTP schema design, or non-dimensional physical outputs. Also use when producing database DDL, JSON Schema, or Parquet-oriented schema contracts from MD-DDL.
avoiding-sql-antipatterns
by sumik5
Identifies and prevents common SQL database design mistakes across logical design, physical design, query construction, and application development. Use when designing database schemas, writing SQL queries, reviewing data models, or implementing database-backed features. Covers 25 named antipatterns with detection signals, solutions, and exception cases. For code-level security (input validation, XSS, OWASP), use securing-code instead. For database model selection and data architecture decisions, use understanding-database-internals instead. For positive relational database design methodology (entity modeling, normalization process), use designing-relational-databases instead.
postgres
by alemar11
Connect to Postgres databases, run queries/diagnostics, and search official PostgreSQL docs only when explicitly requested.
architecting-data
by sumik5
Data architecture patterns covering read-side optimization (replicas, materialized views, CQRS, CDC, event sourcing), domain-based decomposition, polyglot persistence, and caching strategies (cache-aside, read-through, write-through, write-around). Use when designing data flow architecture, choosing read scalability strategies, or implementing caching for enterprise systems. For microservices patterns (Saga, granularity), use architecting-microservices instead. For DDD domain modeling, use applying-domain-driven-design instead. For database engine internals, use understanding-database-internals instead. For relational DB schema design, use designing-relational-databases instead. For GCP-specific data services (BigQuery, Dataflow, Dataproc), use developing-google-cloud instead.