accidental-data-loss-prevention

Requires explicit user consent before executing irreversible data deletion commands.

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Yashyasik/zexca-api --skill accidental-data-loss-prevention-yashyasik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: accidental-data-loss-prevention
Source: https://github.com/Yashyasik/zexca-api/tree/main/.gemini/skills/accidental-data-loss-prevention
Command: npx skills add https://github.com/Yashyasik/zexca-api --skill accidental-data-loss-prevention-yashyasik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Destructive commands like DROP TABLE, TRUNCATE, or gsutil rm can permanently delete production data when executed without verification. This Skill enforces a mandatory confirmation checkpoint so irreversible operations never run without explicit user approval. ## Core Features & Use Cases - Destructive SQL Detection: Flags DROP TABLE/VIEW/SCHEMA/DATABASE, TRUNCATE, and broad DELETE statements missing WHERE clauses or using 1=1. - Cloud Resource Protection: Intercepts gsutil rm, gcloud storage rm, project deletion, and removal of Spanner, BigQuery, Dataproc, secrets, or KMS keys. - Mandatory Consent Workflow: Halts execution, explains the impact and rationale, and waits for explicit affirmative approval before proceeding. - Use Case: Before running a migration script containing DROP TABLE on a production database, the Skill pauses, explains the data loss impact, and only proceeds after you confirm. ## Quick Start Ask the assistant to review and confirm any destructive database or cloud storage command before it is executed.

Frequently Asked Questions about accidental-data-loss-prevention

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

FAQPage Schema
How do I prevent accidental deletion of production database tables?▼

Use a mandatory consent checkpoint that halts any DROP TABLE, TRUNCATE, or broad DELETE statement before execution. The operator must explain the impact and receive explicit user approval before the command runs.

What SQL commands are considered destructive?▼

Destructive SQL includes DROP TABLE, DROP VIEW, DROP SCHEMA, DROP DATABASE, and TRUNCATE. DELETE statements without a WHERE clause or using conditions like 1=1 are also treated as destructive because they remove all rows.

Does this cover Google Cloud storage and resource deletion?▼

Yes, it covers gsutil rm and gcloud storage rm targeting production buckets, plus gcloud projects delete. It also intercepts deletion of Spanner, BigQuery, Dataproc resources, secrets, and KMS key destruction.

When should I ask for confirmation before running a command?▼

Ask for confirmation whenever a command causes irreversible data loss, such as deleting tables, buckets, projects, or encryption keys. When in doubt, request approval rather than risk deleting production data or critical assets.

What happens if user consent is not given for a destructive command?▼

The command is not executed. Execution only proceeds after the user provides clear, affirmative consent in the conversation; otherwise the operation remains halted.