wda-query-translator

Convert standard SQL into WDA Query Builder Go code and validate against the WDA stage API.

31|4|Updated Aug 24, 2021
One-click install
npx skills add https://github.com/razorpay/trino-gateway --skill wda-query-translator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wda-query-translator
Source: https://github.com/razorpay/trino-gateway/tree/main/.agents/skills/wda-query-translator
Command: npx skills add https://github.com/razorpay/trino-gateway --skill wda-query-translator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Translate standard SQL queries into WDA Query Builder Go code and validate the translation against the WDA stage API. This enables developers to automate code generation, produce WDA-compatible JSON, and verify semantic equivalence through an API-driven stage check.

Core Features & Use Cases

  • Translation of SQL to the WDA Query Builder Go code using the goutils/wda/query-builder SDK.
  • Generation of WDA Query JSON from SQL for stage validation and integration.
  • Validation against the WDA stage API to ensure the translated query is semantically equivalent.

Quick Start

Provide a SQL query and request translation to WDA Go code, the corresponding JSON, and API-stage validation.

Frequently Asked Questions about wda-query-translator

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

FAQPage Schema
How do I convert SQL to WDA Query Builder Go code?

To convert SQL to WDA Query Builder Go code, provide a standard SQL query and request translation. The skill generates the corresponding Go code using the goutils/wda/query-builder SDK.

What is WDA Query JSON generation used for?

WDA Query JSON generation produces the JSON representation from SQL input for stage validation and integration, verifying semantic equivalence against the WDA stage API.

How do I validate translated Go code against the WDA stage API?

To validate translated Go code against the WDA stage API, the skill performs an API-driven stage check using the generated JSON to verify semantic equivalence with the original SQL.

Does the query builder support frontmatter-driven activation for SQL translation?

Yes, the SQL translation supports frontmatter-driven activation, satisfying requirements for mapping SQL constructs to builder methods before generating the Go code and JSON.

What are the limitations of translating SQL to Go code via a query builder?

The translation requires standard SQL input and relies on the goutils/wda/query-builder SDK, meaning complex or non-standard SQL constructs may fail semantic equivalence validation against the stage API.