skills.rest
BruceTyndall
BruceTyndallCOMMUNITY
Explore all skills by this author →
GitHub

api-kill-switch-validator

Validate API kill-switch implementation across Supabase migrations, React components, and edge functions.

Updated Aug 23, 2026
Search Tags:#api#validation#runtime#control#edge function#kill switch
One-click install
npx skills add https://github.com/BruceTyndall/socelle-global --skill api-kill-switch-validator
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: api-kill-switch-validator
Source: https://github.com/BruceTyndall/socelle-global/tree/main/.agents/skills/api-kill-switch-validator
Command: npx skills add https://github.com/BruceTyndall/socelle-global --skill api-kill-switch-validator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill ensures that critical API kill-switch functionalities are correctly implemented across the application, preventing accidental outages and ensuring robust control mechanisms.

Core Features & Use Cases

  • Schema Validation: Checks the database schema for the edge_function_controls table and its relevant fields (is_enabled, last_toggled).
  • Control Enforcement: Verifies that seeded controls are present and that the admin UI and runtime logic correctly interact with these controls.
  • Use Case: After modifying how API endpoints are enabled or disabled, use this Skill to confirm that the database, admin interface, and backend logic all align to support the kill-switch functionality.

Quick Start

Run the api-kill-switch-validator skill to verify API kill-switch coverage.

Frequently Asked Questions about api-kill-switch-validator

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

FAQPage Schema
How do I validate API kill-switch coverage across edge functions and admin interfaces?▼

You can validate API kill-switch coverage by running checks against Supabase migrations, React components, and edge function code to verify control schemas, seeded data, and runtime enforcement logic are correctly configured and functional.

What does an API kill-switch validation process check in the database schema?▼

The validation process checks the database schema for the `edge_function_controls` table and verifies that relevant fields like `is_enabled` and `last_toggled` are correctly defined to support runtime control enforcement.

Do I need Supabase migrations and React components to verify my kill-switch implementation?▼

Yes, comprehensive kill-switch verification requires checking Supabase migrations for schema and seeded controls, React components for administrative toggle surfaces, and edge function code for runtime enforcement logic.

When should I check my API kill-switch mechanisms to prevent accidental outages?▼

You should check your API kill-switch mechanisms after modifying how API endpoints are enabled or disabled, ensuring the database, admin interface, and backend logic all align to support the control functionality and prevent accidental outages.

Why does my API kill-switch validation fail even after updating the admin UI?▼

Validation can fail if seeded controls are missing or if the runtime logic in edge function code does not correctly interact with the administrative toggle surfaces, requiring alignment across the database, admin interface, and backend.

Related Skills

Explore More Software Engineering Skills→
theslashdojotheslashdojo

migrations

Automate versioned SQL schema migrations for Supabase projects.

Official
Advanced
dasheck0dasheck0
8

supabase-logs

Fetches and analyzes Supabase Edge Function logs to diagnose runtime and HTTP issues.

Community
Advanced
CJCreator-NewCJCreator-New

workflow-creator

Scaffold clinical and administrative workflows for the CareSync HIMS platform.

Community
Advanced
bughqbughq
2

stacks-migrations

Generate and execute database migrations for Stacks applications.

Official
Intermediate