skills.rest
ihistand
ihistandCOMMUNITY
Explore all skills by this author →
Website𝕏@ihistandGitHub

acuantia-dataform

Enforce Acuantia Dataform conventions for BigQuery ODS and Looker tables.

1|Updated Nov 5, 2025
Search Tags:#data modeling#etl#bigquery#dataform#acuantia#looker
One-click install
npx skills add https://github.com/ihistand/claude-skills --skill acuantia-dataform
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: acuantia-dataform
Source: https://github.com/ihistand/claude-skills/tree/main/acuantia-dataform
Command: npx skills add https://github.com/ihistand/claude-skills --skill acuantia-dataform

SYSTEM DOCUMENTATION & REQUIREMENTS

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

What problem does it solve?

This Skill standardizes and enforces Acuantia-specific conventions within BigQuery Dataform pipelines, ensuring consistency and integration across various data sources and reporting layers.

Core Features & Use Cases

  • Enforces Acuantia ODS Architecture: Mandates the use of two-argument ref() for ODS tables to correctly handle schema suffixes.
  • Standardizes Looker Table Naming: Requires looker_ prefix for tables destined for Acuantia's Looker instance and specifies looker_prod/looker_dev schemas.
  • Integrates Source System Data: Provides patterns for coordinating with CallRail, Dialpad, HubSpot, and Magento data sources.
  • Use Case: When developing a new Dataform model that pulls data from CallRail and needs to be exposed to Looker, this Skill ensures the correct ref() syntax, table naming, and schema configurations are applied.

Quick Start

Use the acuantia-dataform skill to define a new Dataform table for customer metrics, ensuring it uses the two-argument ref() for ODS and the looker_ prefix for the schema.

Frequently Asked Questions about acuantia-dataform

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

FAQPage Schema
How do I use two-argument ref() syntax for BigQuery ODS tables in Dataform?▼

Two-argument ref() syntax in Dataform correctly handles schema suffixes for BigQuery ODS tables, ensuring proper data pipeline architecture and consistent source system integration.

What naming conventions does Dataform require for BigQuery tables exposed to Looker?▼

Looker-bound BigQuery tables require a looker_ prefix and must be assigned to either looker_prod or looker_dev schemas to ensure proper integration with Acuantia's reporting instance.

How do I integrate CallRail and Dialpad source data into BigQuery Dataform pipelines?▼

Integrating CallRail and Dialpad into BigQuery Dataform pipelines involves applying specific data modeling conventions that coordinate cross-project data flows into the ODS architecture.

Does this Dataform approach enforce specific dataset naming conventions for BigQuery?▼

Yes, this approach enforces Acuantia-specific dataset naming conventions for BigQuery, mandating schema suffixes and Looker table prefixes to maintain pipeline consistency across projects.

What is the best way to standardize BigQuery Dataform pipelines across multiple source systems?▼

Standardizing BigQuery Dataform pipelines across systems like HubSpot and Magento requires enforcing consistent ODS architecture, ref() syntax, and Looker schema configurations across all data flows.

Related Skills

Explore More Software Engineering Skills→
AubreyHanAubreyHan

dataform-bigquery

Generates Dataform pipeline code for BigQuery ELT workflows.

Community
Advanced
terrylicaterrylica

bigquery-ethereum-data-acquisition

Acquire Ethereum blockchain data from BigQuery and export to Parquet.

Community
Intermediate
interflownexinterflownex
2

dataform-bigquery

Generate and optimize Dataform pipeline code for Google BigQuery ELT workflows.

Community
Advanced
timequitytimequity
6

dbt-expert

Generates compliant YAML docs and maintains standards for dbt projects.

Official
Advanced