Work on Repeat
Menu

Example routine

Supabase database health review

Review schema health, advisor findings, and service signals in a non-production Supabase project.

Use this routine

Suggested rhythm

Weekly

0 9 * * 1

America/Los_Angeles

Expected result

A non-production database health brief with bounded evidence, prioritized risks, and concrete human follow-up actions.

Built for

Engineering · Product

Works with

  • Supabase

What the routine does

Use only the connected non-production Supabase project. List the public schema compactly, review security and performance advisors, and inspect only the last 24 hours of relevant Postgres or API logs. Run narrow read-only aggregate SQL only when structure, advisors, and logs do not answer the question. Never include raw row values, PII, secrets, access tokens, or connection strings in the result. Never mutate schema or data. Separate observed evidence from recommendations, cite the query or log window behind each finding, and end with a short prioritized list of human actions.

Inputs

    Required MCP capabilities

    • List database tables
    • Run read-only SQL
    • Read database advisors
    • Read bounded service logs

    Permission boundary

    Connections do not grant blanket access. Discover the MCP tools, enable only the capabilities this responsibility needs, and give write-like actions a separate automatic-execution confirmation.

    More engineering routines