deploy-prod

Automate ETL pipeline execution and deployment to production Supabase.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/ronniepinnell/benchsight --skill deploy-prod-ronniepinnell
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: deploy-prod
Source: https://github.com/ronniepinnell/benchsight/tree/main/.claude/skills/deploy-prod
Command: npx skills add https://github.com/ronniepinnell/benchsight --skill deploy-prod-ronniepinnell

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates running the full ETL pipeline and deploying results to PRODUCTION Supabase, with explicit confirmation requirements to prevent accidental deployments.

Core Features & Use Cases

  • End-to-end ETL execution and upload to PRODUCTION Supabase.
  • Enforced confirmation step and safety guardrails to prevent unintended deployments.
  • Audit logging and rollback readiness for production releases.

Quick Start

Type DEPLOY TO PRODUCTION to confirm and initiate the production ETL deployment.

Frequently Asked Questions about deploy-prod

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate ETL deployment to production Supabase with safety guards?

Automating ETL deployment to production Supabase requires a dedicated agent with safety guards that enforces explicit textual confirmation before executing data pipeline uploads and verification steps.

What is the best way to prevent accidental production ETL pipeline deployments?

Preventing accidental production ETL pipeline deployments is achieved by enforcing a mandatory textual confirmation step before execution, supported by audit logging and rollback readiness for production releases.

Can I use automated safeguards for uploading data pipeline results to Supabase?

Automated safeguards for uploading data pipeline results to Supabase work by applying explicit confirmation requirements and safety guardrails across ETL execution, data upload, and verification steps.

How does the confirmation step work before running a full ETL pipeline release?

The confirmation step before running a full ETL pipeline release works by requiring the user to type a specific textual command, ensuring intentional execution of the production deployment workflow.

Do I need audit logging and rollback readiness for Supabase ETL production releases?

Audit logging and rollback readiness are necessary for Supabase ETL production releases to maintain safety guardrails and provide recovery options during end-to-end ETL execution and upload.

When should I not use automated production deployment for ETL data pipelines?

Automated production deployment for ETL data pipelines should not be used when explicit confirmation and safety guards cannot be enforced, risking unintended data uploads to the production environment.