What problem does it solve? Deploying or debugging the PalFish GMV app fails silently when environment variables are missing, because render.yaml declares only a subset of the vars the backend actually reads. This Skill provides the complete env var catalog per service, the render.yaml coverage gap, and step-by-step procedures for rotating leaked secrets or onboarding new developers. ## Core Features & Use Cases - Full env var catalog: Every backend and frontend variable mapped to the file that reads it, with the exact failure mode (503, 401, CORS 400) when missing. - render.yaml gap detection: Lists the 16 vars absent from the Blueprint (CRM, SePay, Zalo, DingTalk, GSheet) that must be added manually in the Render Dashboard. - Rotation and setup procedures: Covers leaked-secret rotation across Render, Vercel, and local .env files, plus local dev setup for backend and frontend. - Use Case: A fresh Render deploy passes the health check but CRM sync returns 503. Use this Skill to identify that CRM_ENCRYPT_KEY and CRM_EXTENSION_INGEST_TOKEN are missing from render.yaml and add them via the Render Dashboard. ## Quick Start Ask the assistant to diagnose why the SePay webhook returns 500 on production and list which environment variables to verify on the Render service.