What problem does it solve? Working with Denodo Virtual DataPort often produces objects that exist only on a server, with no reviewable artifact, no naming consistency, and no safe path for destructive changes. This Skill enforces a file-first loop where every CREATE, ALTER, and DROP is written into a .vql file in the project, applied to a live server, and verified before it stays in git. ## Core Features & Use Cases - File-based VQL workflow: Writes every statement into a .vql file, applies it whole, and verifies results with DESC and test SELECTs so objects are always reproducible. - Naming conventions and placement: Applies Denodo VDP naming conventions (ds_, bv_, iv_, a_ prefixes, numbered layer folders) with project-level overrides via .denodo/conventions.md. - Safety gate for destructive operations: Requires explicit human confirmation for DROP, TRUNCATE, DELETE, ALTER of existing objects, destructive marketplace REST calls, and any change on production profiles. - Use Case: You ask to "onboard these return files and build a mart of returns by store" — the Skill decides database and folder placement, writes CREATE OR REPLACE statements for data sources, wrappers, base views, and derived views into a .vql file, applies it, and verifies each object reads correctly. ## Quick Start Ask the agent to create a Denodo database with a JDBC data source and a base view, and have it write the VQL into a file in your project before applying it to the server.
