Find the best skills for |

Execute apply Supabase advanced debugging techniques for hard-to-diagnose issues.\nUse when standard troubleshooting fails, investigating complex race conditions,\nor preparing evidence bundles for Supabase support escalation.\nTrigger with phrases like \

Execute choose and implement Supabase validated architecture blueprints for different scales.\nUse when designing new Supabase integrations, choosing between monolith/service/microservice\narchitectures, or planning migration paths for Supabase applications.\nTrigger with

Automate Supabase database queries, table management, project administration, storage, edge functions, and SQL execution via Rube MCP (Composio). Always search tools first for current schemas.

Configure Supabase CI/CD integration with GitHub Actions and testing.\nUse when setting up automated testing, configuring CI pipelines,\nor integrating Supabase tests into your build process.\nTrigger with phrases like \

Execute diagnose and fix Supabase common errors and exceptions.\nUse when encountering Supabase errors, debugging failed requests,\nor troubleshooting integration issues.\nTrigger with phrases like \

Implement Supabase PII handling, data retention, and GDPR/CCPA compliance patterns.\nUse when handling sensitive data, implementing data redaction, configuring retention policies,\nor ensuring compliance with privacy regulations for Supabase integrations.\nTrigger with phrases

Execute collect Supabase debug evidence for support tickets and troubleshooting.\nUse when encountering persistent issues, preparing support tickets,\nor collecting diagnostic information for Supabase problems.\nTrigger with phrases like \

Build full-stack applications with Supabase (PostgreSQL, Auth, Storage, Real-time, Edge Functions). Use when implementing authentication, database design with RLS, file storage, real-time features, or serverless functions.

Configure Supabase enterprise SSO, role-based access control, and organization management.\nUse when implementing SSO integration, configuring role-based permissions,\nor setting up organization-level controls for Supabase.\nTrigger with phrases like \

Create a minimal working Supabase example.\nUse when starting a new Supabase integration, testing your setup,\nor learning basic Supabase API patterns.\nTrigger with phrases like \

Execute Supabase incident response procedures with triage, mitigation, and postmortem.\nUse when responding to Supabase-related outages, investigating errors,\nor running post-incident reviews for Supabase integration failures.\nTrigger with phrases like \

Execute identify and avoid Supabase anti-patterns and common integration mistakes.\nUse when reviewing Supabase code for issues, onboarding new developers,\nor auditing existing Supabase integrations for best practices violations.\nTrigger with phrases like \

Implement Supabase load testing, auto-scaling, and capacity planning strategies.\nUse when running performance tests, configuring horizontal scaling,\nor planning capacity for Supabase integrations.\nTrigger with phrases like \

Comprehensive Supabase integration covering authentication, database operations, realtime subscriptions, storage, and MCP server patterns for building production-ready backends with PostgreSQL, Auth, and real-time capabilities

Execute Supabase major re-architecture and migration strategies with strangler fig pattern.\nUse when migrating to or from Supabase, performing major version upgrades,\nor re-platforming existing integrations to Supabase.\nTrigger with phrases like \

Configure Supabase across development, staging, and production environments.\nUse when setting up multi-environment deployments, configuring per-environment secrets,\nor implementing environment-specific Supabase configurations.\nTrigger with phrases like \

Execute set up comprehensive observability for Supabase integrations with metrics, traces, and alerts.\nUse when implementing monitoring for Supabase operations, setting up dashboards,\nor configuring alerting for Supabase integration health.\nTrigger with phrases like \

Supabase operational knowledge for migrations, RLS optimization, MCP tool benchmarks, and ADR-003 compliance. Use when validating database migrations, optimizing Row-Level Security policies, checking MCP tool performance, or ensuring Supabase operational standards. Triggers on:

Optimize Supabase API performance with caching, batching, and connection pooling.\nUse when experiencing slow API responses, implementing caching strategies,\nor optimizing request throughput for Supabase integrations.\nTrigger with phrases like \

Implement Supabase lint rules, policy enforcement, and automated guardrails.\nUse when setting up code quality rules for Supabase integrations, implementing\npre-commit hooks, or configuring CI policy checks for Supabase best practices.\nTrigger with phrases like \

Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.

Execute Supabase production deployment checklist and rollback procedures.\nUse when deploying Supabase integrations to production, preparing for launch,\nor implementing go-live procedures.\nTrigger with phrases like \

Implement Supabase rate limiting, backoff, and idempotency patterns.\nUse when handling rate limit errors, implementing retry logic,\nor optimizing API request throughput for Supabase.\nTrigger with phrases like \

Implement Supabase reliability patterns including circuit breakers, idempotency, and graceful degradation.\nUse when building fault-tolerant Supabase integrations, implementing retry strategies,\nor adding resilience to production Supabase services.\nTrigger with phrases like \

Generate Supabase RLS policies from Prisma schema. Use when securing database.

This skill should be used when the user requests to generate, create, or add Row-Level Security (RLS) policies for Supabase databases in multi-tenant or role-based applications. It generates comprehensive RLS policies using auth.uid(), auth.jwt() claims, and role-based access

Execute apply Supabase security best practices for secrets and access control.\nUse when securing API keys, implementing least privilege access,\nor auditing Supabase security configuration.\nTrigger with phrases like \

Execute analyze, plan, and execute Supabase SDK upgrades with breaking change detection.\nUse when upgrading Supabase SDK versions, detecting deprecations,\nor migrating to new API versions.\nTrigger with phrases like \

Implement Supabase webhook signature validation and event handling.\nUse when setting up webhook endpoints, implementing signature verification,\nor handling Supabase event notifications securely.\nTrigger with phrases like \

Save important project knowledge to memory. Use when user wants to preserve architectural decisions, significant bug fixes, design patterns, or important implementation details for team reference.

Search your coding memory. Use when user asks about past work, previous sessions, how something was implemented, what they worked on before, or wants to recall information from earlier sessions.

Store and retrieve memories using the SuperMemory API. Add content, search memories, and chat with your knowledge base.

Produces a structured brainstorm: goals, constraints, risks, options, recommendation, and acceptance criteria. Use before non-trivial implementation or design changes.

Systematic debugging: reproduce, isolate, form hypotheses, instrument, fix, and add regression tests. Use when troubleshooting errors, failing tests, or unexpected behavior.

Finalizes work: runs verification, summarizes changes, notes follow-ups, and ensures repo hygiene. Use at the end of an implementation or debugging session.

Writes an implementation plan with small steps, exact files to touch, and verification commands. Use before making non-trivial changes.

Implements reliable automations in Python for REST APIs: httpx/requests patterns, retries, timeouts, pagination, typing, config, logging, and tests. Use when writing Python scripts/services that call external APIs.

Builds reliable automations that integrate with REST APIs: auth, pagination, retries, rate limits, idempotency, webhooks, data mapping, and safe error handling. Use when calling external APIs, syncing systems, or building ETL-style workflows.

Reviews changes for correctness, edge cases, style, security, and maintainability with severity levels (Blocker/Major/Minor/Nit). Use before finalizing changes.

Applies tests-first discipline (red/green/refactor) and adds regression tests for bugs. Use when implementing features, fixing bugs, or refactoring.

Enforces a disciplined workflow for coding, debugging, refactoring, and automation: brainstorm -u003e plan -u003e implement with verification (prefer TDD) -u003e review -u003e finish. Use for almost any non-trivial change.

BK-CI 支撑模块架构指南，涵盖凭证管理(Ticket)、构建机环境(Environment)、通知服务(Notify)、构建日志(Log)、质量红线(Quality)、开放接口(OpenAPI)等支撑性服务模块。当用户开发这些模块功能或需要理解支撑服务架构时使用。

Running Suricata against PCAPs offline and validating results via eve.json

Core building blocks of Suricata signatures and multi-condition DPI logic

Survey Creator - Auto-activating skill for Business Automation.\nTriggers on: survey creator, survey creator\nPart of the Business Automation skill category.

Audit PostHog survey SDK features and version requirements

Create surveys and collect responses via SurveyMonkey API. Manage surveys, view results, and export data.

Svelte 5 patterns including TanStack Query mutations, shadcn-svelte components, and component composition. Use when writing Svelte components, using TanStack Query, or working with shadcn-svelte UI.