query-warehouse

Query BigQuery and Snowflake with schema discovery, cost estimation, and SQL execution.

1|Updated May 13, 2026
One-click install
npx skills add https://github.com/argen/hornero --skill query-warehouse
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: query-warehouse
Source: https://github.com/argen/hornero/tree/main/skills/query-warehouse
Command: npx skills add https://github.com/argen/hornero --skill query-warehouse

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill streamlines querying of analytics warehouses like BigQuery or Snowflake, providing schema discovery, cost estimation, and SQL execution with a hard cap on scanned bytes to prevent overages.

Core Features & Use Cases

  • Schema Discovery: Quickly understand the structure of a table, including columns, types, and partitioning.
  • Cost Estimation: Estimate the cost of a query before running it to prevent overages.
  • SQL Execution: Execute SQL queries with a hard limit on scanned bytes to ensure cost control.
  • Use Case: When you need to validate a metric in a PRD, use this Skill to first discover the schema and then estimate the cost of a query to confirm the metric definition.

Quick Start

Use the query-warehouse skill to discover the schema of the 'analytics.events.fact_activations' table.

Frequently Asked Questions about query-warehouse

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

FAQPage Schema
How do I estimate query costs in BigQuery and Snowflake before execution?

Estimate query costs in BigQuery and Snowflake using a pre-execution cost estimation mechanism that calculates projected resource usage based on scanned bytes. This prevents overages by evaluating the query footprint before running it.

What is the best way to discover table schemas across different analytics warehouses?

Discover table schemas across analytics warehouses using a schema discovery process that reveals columns, data types, and partitioning details. This mechanism hides engine-specific SQL differences between platforms like BigQuery and Snowflake.

How do I enforce a hard limit on scanned bytes when executing SQL queries?

Enforce a hard limit on scanned bytes during SQL execution by applying a guardrail mechanism. This ensures cost control by strictly capping the data volume processed during the query.

Can I validate a metric definition in a PRD by querying analytics warehouses safely?

Validate a metric definition in a PRD by querying analytics warehouses safely through schema discovery followed by cost estimation. This structured interface confirms the metric definition without risking unexpected data scan charges.

Does this SQL execution approach work with both BigQuery and Snowflake without changing syntax?

Yes, this SQL execution approach works with both BigQuery and Snowflake without changing syntax. It provides a structured interface that hides engine-specific SQL differences, allowing seamless cross-platform querying.