What problem does it solve? UI and API tests can pass even when the underlying database write silently regresses. This Skill closes that gap by treating the database as a verifiable oracle, generating structured SQL assertions that prove mutations actually persisted. ## Core Features & Use Cases - Schema Discovery: Introspects information_schema to map tables, columns, and foreign keys, then derives CRUD, JOIN, aggregate, and transaction test scenarios automatically. - Structured Assertions: Governs the steps.sqlQuery/sqlExecute/sqlTransaction methods and verifySql* matchers (row counts, cell values, column order, empty/non-empty results) from @civitas-cerebrum/element-interactions. - DB-as-Oracle Bridge: Adds persistence assertions after UI flows or API calls, verifying that actions like checkout actually wrote the expected order row. - Use Case: After an API test creates an order, query the orders table and assert the latest row has status COMPLETED, catching write regressions the 201 response alone would miss. ## Quick Start Ask the agent to write database tests that verify the orders table after each checkout flow using steps.sqlQuery and verifySqlValue.