supabase-evidence
Evidence Collection Management
🔴 CRITICAL: PROGRESSIVE FILE UPDATES REQUIRED
You MUST write evidence files AS YOU GO, not just at the end.
- Save each piece of evidence IMMEDIATELY after collection
- DO NOT wait until the skill completes to save evidence
- If the audit crashes or is interrupted, all prior evidence must already be saved
This is not optional. Failure to save evidence progressively is a critical error.
This skill initializes and manages the evidence collection system for professional security audits.
When to Use This Skill
- Automatically invoked at the start of
supabase-pentest - When you need to organize evidence for a professional report
- When conducting audits that require documented proof
- For compliance and legal purposes
More from yoanbernabeu/supabase-pentest-skills
supabase-audit-rls
Test Row Level Security (RLS) policies for common bypass vulnerabilities and misconfigurations.
374supabase-pentest
Orchestrate a complete Supabase security audit with guided step-by-step execution and ownership confirmation.
240supabase-audit-auth-config
Analyze Supabase authentication configuration for security weaknesses and misconfigurations.
187supabase-audit-functions
Discover and test Supabase Edge Functions for security vulnerabilities and misconfigurations.
185supabase-help
Quick reference for all Supabase security audit skills with usage examples and command overview.
181supabase-audit-realtime
Test Supabase Realtime WebSocket channels for unauthorized subscriptions and data exposure.
174