Generated banner for Bigquery Udfs
Generated logo for Bigquery Udfs

Bigquery Udfs

GoogleOfficialPublished by Google

  • Skill
  • Tool integration
  • Data and AI
  • Apache-2.0
  • No issues found

From the author

Creates, deploys, and troubleshoots BigQuery User-Defined Functions (UDFs) and Remote Functions across SQL, JavaScript, Python, and Cloud Run endpoints. Use when writing custom scalar or aggregate functions in BigQuery, installing PyPI packages or Cloud Storage libraries in a Python or JavaScript UDF, or calling Google Cloud and external APIs from a Python UDF (WITH CONNECTION) or Remote Function. Don't use for standard BigQuery table/dataset CRUD (use bigquery-basics), DataFrames client workflows (use bigquery-bigframes), or BigQuery ML models (use bigquery-ai-ml).
— the description by Google

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

The bigquery-udfs skill provides a comprehensive framework for extending BigQuery's native capabilities. It supports the creation of scalar and aggregate functions across multiple runtimes, including native SQL, JavaScript, and Python 3.11. The skill also facilitates advanced integrations by enabling Python UDFs to call external APIs via secure connections and allowing the use of Remote Functions hosted on Cloud Run for complex, non-Python, or VPC-restricted workloads.

What it does

  • Creates and manages persistent or temporary SQL and JavaScript UDFs.
  • Deploys managed Python 3.11 UDFs with support for PyPI packages and Cloud Storage libraries.
  • Configures secure connections for Python UDFs to access Google Cloud and external APIs.
  • Registers Remote Functions on Cloud Run for custom scaling, non-Python runtimes, or private network access.
  • Provides troubleshooting patterns for container builds, IAM permissions, and API call errors.
  • Includes a validation workflow to test UDF logic before and after deployment.

When to use it

  • When you need custom logic that exceeds standard BigQuery SQL capabilities.
  • When you need to bundle external JavaScript libraries or Python packages for data processing.
  • When your function requires outbound network access to call external APIs or services.
  • When you need to leverage custom container environments or private VPC resources via Cloud Run.
  • When you need to perform row-independent vectorized operations using Pandas or PyArrow.

Advantages

  • Extends BigQuery with custom business logic and external service integration.
  • Supports multiple runtimes to balance performance and complexity requirements.
  • Enables secure, authenticated access to external APIs via managed connections.
  • Provides structured patterns for error handling and logging in distributed UDF environments.
  • Allows for modular code reuse through persistent functions and authorized routines.

Usage examples

“Create a persistent SQL UDF to normalize phone numbers.”
The agent generates a CREATE OR REPLACE FUNCTION statement using REGEXP_REPLACE to format raw phone strings based on a provided country code.
“How do I call the Cloud Translation API from a BigQuery Python UDF?”
The agent guides you through creating a CLOUD_RESOURCE connection, granting the necessary IAM roles to the connection's service account, and writing the Python UDF with the WITH CONNECTION clause.
“Help me troubleshoot a failed Python UDF deployment.”
The agent instructs you to query INFORMATION_SCHEMA.ROUTINES to inspect the build_status and provides steps to validate the Python code locally or via a Cloud Run Job.
“How can I use a custom Go service as a BigQuery function?”
The agent explains how to set up a Remote Function, including configuring the Cloud Run endpoint, granting the invoker role, and registering the function with REMOTE WITH CONNECTION.

Install

  1. Download the skill as a ZIP:

    https://autogineer.com/agent-skills/google/bigquery-udfs/download
  2. Unzip it into the cross-client skills folder of your project:

    mkdir -p .agents/skills && unzip bigquery-udfs.zip -d .agents/skills

Documentation by Google

BigQuery User-Defined Functions (UDFs)

BigQuery User-Defined Functions (UDFs) extend GoogleSQL with custom logic written in SQL, JavaScript, managed Python (python-3.11), or hosted externally as Remote Functions on Cloud Run and Cloud Run functions.

Usage Attribution

MUST READ: Before executing any gcloud, REST API, or MCP command, you MUST read and follow the instructions in Usage Attribution.

Choosing the Right UDF Type

Always select the lightest-weight runtime that satisfies the requirement, because BigQuery optimizes native SQL expressions inline while external runtimes incur serialization and container startup overhead:

UDF TypeConnection Required?When to UseKey Constraints
SQL UDF (Default)NoComposable expressions, regex, struct/array manipulation, aggregate functions (CREATE AGGREGATE FUNCTION), or polymorphic ANY TYPE parameters.Lowest latency; zero external dependencies; supports TEMP or persistent functions.
JavaScript UDFNoCustom string/JSON logic or bundling .js libraries from Cloud Storage (gs://).Runs in V8 sandbox; INT64 unsupported as input (pass as FLOAT64 or STRING). Max 32 KB inline code, 1 MB per external resource. Supports TEMP or persistent functions.
Managed Python UDF (Offline)NoPure compute using Python 3.11, PyPI wheels (packages=[...]), Cloud Storage .py modules (library=[...]), or vectorized Pandas/PyArrow batches.Persistent functions only (CREATE TEMP FUNCTION unsupported). Outbound network blocked. Max container size: 4 vCPU / 16 GiB. JSON, RANGE, INTERVAL, GEOGRAPHY unsupported.
Managed Python UDF (WITH CONNECTION)Yes (CLOUD_RESOURCE)Invoking Google Cloud APIs (e.g., Cloud Translation, Gemini Enterprise Agent Platform) or online HTTP endpoints directly from Python inside BigQuery containers.Requires WITH CONNECTION. Outbound traffic restricted to restricted.googleapis.com in VPC-SC perimeters (VPC networks unsupported). Max container size: 4 vCPU / 16 GiB.
Remote Function (REMOTE WITH CONNECTION)Yes (CLOUD_RESOURCE)Calling external APIs or microservices when you need non-Python runtimes (Go, Java, Node.js), private VPC network access, GPUs, or custom Cloud Run scaling.Requires Cloud Run HTTPS endpoint implementing BigQuery JSON batch contract and roles/run.invoker. Max input 5 MB per row; response limit 15 MB (Cloud Run) / 10 MB (1st gen).

Prerequisites & Setup

Ensure the Google Cloud project has an active billing account attached (see BigQuery Pricing):

  1. Install and Authenticate Google Cloud SDK: Install the Google Cloud SDK and authenticate:

    gcloud auth login

    Pass --project={project_id} and --region={region} (or --location for bq) explicitly on each command instead of running gcloud config set, which persists beyond the task. Default to us-central1 when the user has not specified a region (see BigQuery Locations).

  2. Enable Required APIs:

    • For SQL, JavaScript, and offline Python UDFs: bigquery.googleapis.com

    • Additionally for Python UDFs calling APIs (WITH CONNECTION) and Remote Functions: bigqueryconnection.googleapis.com (and run.googleapis.com for Remote Functions)

    CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:bigquery-udfs)" \
    gcloud services enable bigquery.googleapis.com \
      bigqueryconnection.googleapis.com \
      run.googleapis.com --quiet
  3. Verify Required IAM Roles:

    • All UDFs: roles/bigquery.dataEditor on the dataset and roles/bigquery.jobUser on the project.

    • When using WITH CONNECTION (API-calling Python UDFs & Remote Functions):

      • UDF Creator: roles/bigquery.connectionAdmin on the project (plus resourcemanager.projects.setIamPolicy, e.g., roles/resourcemanager.projectIamAdmin, when granting project-level IAM roles to the connection service account via GRANT ... ON PROJECT).

      • UDF Caller: roles/bigquery.connectionUser on the connection.


Core Implementation Patterns

1. SQL UDFs (Scalar & Templated)

Use CREATE OR REPLACE FUNCTION for persistent UDFs or CREATE TEMP FUNCTION for query-scoped functions. Use ANY TYPE for polymorphic parameters:

CREATE OR REPLACE FUNCTION `{project_id}.{dataset_id}.normalize_phone`(
  raw_phone STRING,
  country_code ANY TYPE
)
RETURNS STRING
AS (
  CONCAT('+', CAST(country_code AS STRING), '-', REGEXP_REPLACE(raw_phone, r'[^0-9]', ''))
);

See SQL and JavaScript UDFs for aggregate UDFs (CREATE AGGREGATE FUNCTION) and JavaScript Cloud Storage library loading.

2. JavaScript UDFs

Use raw triple-quoted strings (r"""...""") to avoid escaping backslashes:

CREATE OR REPLACE FUNCTION `{project_id}.{dataset_id}.extract_url_query_keys`(
  url_str STRING
)
RETURNS ARRAY<STRING>
DETERMINISTIC
LANGUAGE js
OPTIONS (
  library = ['gs://{bucket_name}/libs/uri-parser.js']
)
AS r"""
  if (!url_str) return [];
  try {
    return URIParser.getQueryKeys(url_str);
  } catch (err) {
    return [];
  }
""";
3. Managed Python UDFs (With and Without Connection)

Python UDFs must be persistent (do not use TEMP), specify runtime_version = 'python-3.11', and define an entry_point. numpy, pandas, and pyarrow are pre-installed in the python-3.11 base image.

BigQuery defaults to container_memory = '512Mi', container_cpu = 1.0, and container_request_concurrency = 80. Omit these options when the defaults are sufficient, and configure them explicitly only when a workload requires custom container sizing or concurrency (see Python UDFs).

Top-level Python statements (import, helper functions, classes, and def {entry_point}(...)) inside AS r'''...''' must have zero leading indentation (flush to the left margin). Indenting top-level Python definitions to align with surrounding SQL causes an IndentationError when BigQuery loads the container module.

A. Offline / Vectorized Python UDF (No Connection Needed)

Omit WITH CONNECTION when the UDF only performs computation or uses PyPI packages (packages=[...]) / Cloud Storage libraries (library=['gs://...']). To vectorize execution over batches of rows, annotate the parameter with pd.DataFrame (or pyarrow.RecordBatch) and return a pd.Series:

[!WARNING] Vectorized operations must be row-independent: BigQuery calls vectorized UDFs on arbitrary row batches (up to max_batching_rows). Do NOT compute global column statistics (such as z-scores, dataset mean/std, or rank) across df, because each batch only sees an arbitrary slice of rows. Use SQL window functions ((val - AVG(val) OVER()) / NULLIF(STDDEV(val) OVER(), 0)) for dataset-wide statistics. Vectorized Python UDFs should perform row-independent calculations (e.g. geometric distances or multi-column math).

CREATE OR REPLACE FUNCTION `{project_id}.{dataset_id}.vectorized_distance`(
  x1 FLOAT64, y1 FLOAT64, x2 FLOAT64, y2 FLOAT64
)
RETURNS FLOAT64
LANGUAGE python
OPTIONS (
  runtime_version = 'python-3.11',
  entry_point = 'compute_distance'
)
AS r'''
import numpy as np
import pandas as pd

def compute_distance(df: pd.DataFrame) -> pd.Series:
    return pd.Series(
        np.hypot(df['x2'] - df['x1'], df['y2'] - df['y1']),
        index=df.index,
    )
''';
B. Online Python UDF Calling an External / Cloud API (WITH CONNECTION)

Include WITH CONNECTION only when the Python code makes outbound network or API calls at runtime.

Always configure explicit timeouts, logging, and prescriptive exception handling in the try...except block:

  • Transient errors only → NULL: Catch retryable exceptions (google.api_core.exceptions.TooManyRequests, ServiceUnavailable, DeadlineExceeded, InternalServerError, and RetryError), log them with logging.warning, and return None so a transient blip does not abort the query. Do not catch the base class GoogleAPICallError here: it also matches PermissionDenied, Unauthenticated, and InvalidArgument.

  • Fatal errors → raise: Let auth, permission, and invalid-argument errors propagate (or log and re-raise as RuntimeError) so they surface as a user error on the query instead of silently producing NULLs.

  • Never log row values: Anyone with Cloud Logging access can read UDF logs regardless of BigQuery table permissions. Log exception types and messages, not input or output data. Logs are only emitted when the session sets SET @@udf.properties = JSON '{"enableDebugOutput": true}';.

  • Set a per-request timeout: Retry(timeout=...) only caps the total retry duration; also pass timeout= on each client call.

  1. Create a Cloud Resource Connection and Retrieve its Service Account:

    bq mk --connection --connection_type=CLOUD_RESOURCE \
      --location={region} --project_id={project_id} {connection_id}
    
    bq show --connection {project_id}.{region}.{connection_id}
  2. Grant Permissions to the Connection Service Account: Grant roles/serviceusage.serviceUsageConsumer on {project_id} plus the required API role (e.g., roles/cloudtranslate.user) on the target project. Running GRANT ... ON PROJECT modifies the project's IAM policy and requires resourcemanager.projects.setIamPolicy (for example, roles/resourcemanager.projectIamAdmin); confirm with the user before running project-level IAM grants. The DCL connection: grantee takes the connection path ([project_id.]location.connection_id), not the service account email; BigQuery resolves the connection's service account automatically (use "serviceAccount:{connection_sa_email}" to grant by email instead):

    GRANT `roles/serviceusage.serviceUsageConsumer`
    ON PROJECT `{project_id}`
    TO "connection:{project_id}.{region}.{connection_id}";
    
    GRANT `roles/cloudtranslate.user`
    ON PROJECT `{project_id}`
    TO "connection:{project_id}.{region}.{connection_id}";
  3. Create the Python UDF with WITH CONNECTION (keep top-level Python statements flush-left at column 0):

CREATE OR REPLACE FUNCTION `{project_id}.{dataset_id}.translate_to_es`(
  text STRING
)
RETURNS STRING
LANGUAGE python
WITH CONNECTION `{project_id}.{region}.{connection_id}`
OPTIONS (
  entry_point = 'do_translate',
  runtime_version = 'python-3.11',
  packages = ['google-cloud-translate>=3.11', 'google-api-core']
)
AS r'''
import logging
from google.api_core import exceptions
from google.api_core.retry import Retry
from google.cloud import translate

client = translate.TranslationServiceClient()

TRANSIENT_ERRORS = (
    exceptions.TooManyRequests,
    exceptions.ServiceUnavailable,
    exceptions.DeadlineExceeded,
    exceptions.InternalServerError,
    exceptions.RetryError,
)

def do_translate(text: str) -> str:
    if not text:
        return None
    try:
        # Note: Replace {project_id} with your Google Cloud Project ID
        response = client.translate_text(
            request={
                "parent": "projects/{project_id}/locations/us-central1",
                "contents": [text],
                "target_language_code": "es",
                "mime_type": "text/plain",
            },
            retry=Retry(timeout=30.0),  # Total retry budget.
            timeout=10.0,  # Per-attempt deadline.
        )
        return response.translations[0].translated_text
    except TRANSIENT_ERRORS as e:
        # Log the error type only; never log row values.
        logging.warning("Transient Translation API error: %s", type(e).__name__)
        return None
    except exceptions.GoogleAPICallError as e:
        # PermissionDenied, Unauthenticated, InvalidArgument, etc. are fatal.
        logging.error("Fatal Translation API error: %s: %s", type(e).__name__, e)
        raise RuntimeError(f"Translation failed: {type(e).__name__}") from e
''';

See Python UDFs for container sizing (container_cpu, container_memory, container_request_concurrency), Cloud Logging (SET @@udf.properties = JSON '{"enableDebugOutput": true}';), and checking container build status via INFORMATION_SCHEMA.ROUTINES.

4. Remote Functions (Cloud Run Endpoints)

Use Remote Functions when the endpoint is hosted on Cloud Run or Cloud Run functions (for non-Python languages, VPC networking, or custom hardware):

  1. Grant roles/run.invoker to the Connection Service Account (confirm with the user before modifying the Cloud Run service IAM policy):

    CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:bigquery-udfs)" \
    gcloud run services add-iam-policy-binding {cloud_run_service} \
      --region={region} \
      --member="serviceAccount:{connection_sa_email}" \
      --role="roles/run.invoker"
  2. Register the Remote Function: The endpoint must accept {"calls": [[arg1, ...], ...]} and return {"replies": [res1, ...]} with matching element count:

    CREATE OR REPLACE FUNCTION `{project_id}.{dataset_id}.enrich_address`(
      street STRING, postal_code STRING
    )
    RETURNS JSON
    REMOTE WITH CONNECTION `{project_id}.{region}.{connection_id}`
    OPTIONS (
      endpoint = 'https://{cloud_run_service_url}',
      max_batching_rows = 1000
    );

See Remote Functions for Cloud Run handler templates and retry handling.


Validation Checklist

After generating or modifying a UDF, follow this validate→fix→repeat loop:

  • [ ] [ ] Step 1 — Validate Python code before BigQuery DDL: For Python UDFs, validate the Python function and packages dependencies before submitting the BigQuery DDL—either locally with python3 test inputs (None, edge cases, pd.DataFrame batches) or in a containerized Cloud Run Job (gcloud run jobs deploy {job_name} --source . --region={region} and gcloud run jobs execute {job_name} --region={region} --wait; see Python UDFs Validation).

  • [ ] [ ] Step 2 — Execute DDL and poll container build status: Run CREATE OR REPLACE FUNCTION. Because the DDL statement returns before the Python container image finishes building, poll INFORMATION_SCHEMA.ROUTINES until build_state transitions from IN_PROGRESS to SUCCEEDED (or fix and re-run if FAILED):

    SELECT build_status.*
    FROM `{project_id}.{dataset_id}`.INFORMATION_SCHEMA.ROUTINES
    WHERE routine_name = '{udf_name}';
  • [ ] [ ] Step 3 — Test the UDF with SQL SELECT: Once build_state = 'SUCCEEDED' (or immediately after DDL for SQL/JS UDFs), run a test SELECT query covering NULL and valid inputs.

Cleanup & Teardown

Delete unused routines, connections, Cloud Run services, and staged Cloud Storage artifacts (note that the size of all Python UDF containers per project and per region is restricted to a sum total of 10 GiB):

bq query --use_legacy_sql=false "DROP FUNCTION IF EXISTS \`{project_id}.{dataset_id}.{udf_name}\`;"
bq rm --connection --location={region} {connection_id}
CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:bigquery-udfs)" \
gcloud run services delete {cloud_run_service} --region={region} --project={project_id}
CLOUDSDK_METRICS_REQUEST_ATTRIBUTION="agent-skills/1.0 (skill:bigquery-udfs)" \
gcloud storage rm gs://{bucket_name}/udf_libs/bundle.js

Reference Directory

  • SQL and JavaScript UDFs: Templated SQL parameters (ANY TYPE), aggregate UDFs, JavaScript type mappings, and Cloud Storage library loading (https://docs.cloud.google.com/bigquery/docs/user-defined-functions.md.txt).

  • Python UDFs: Offline vs. WITH CONNECTION online service access, Pandas/PyArrow vectorization, container resource limits (container_cpu/container_memory), and Cloud Logging debugging (https://docs.cloud.google.com/bigquery/docs/user-defined-functions-python.md.txt).

  • Remote Functions: Cloud Run HTTP request and response JSON schema, batch sizing, retry semantics, and VPC egress (https://docs.cloud.google.com/bigquery/docs/remote-functions.md.txt).

  • IAM, Authorized Routines, and Quotas: Sharing routines across datasets (Authorized Routines), container quotas, and troubleshooting errors.

  • BigQuery Basics (bigquery-basics): Dataset, table, and job management.

  • BigQuery DataFrames: Creating Python UDFs from Python via @bpd.udf.

  • BigQuery AI & ML: Built-in ML.GENERATE_TEXT and AI.GENERATE functions.

Files

LICENSE


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Needs a command-line tool, Needs Python

Security

No issues found by our static scan· No issues found

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Published by
Google
Publisher
Google (Official)
Source
google/skills · skills/cloud/bigquery-udfs · commit 2194d3b
Licence
Apache License 2.0 (redistribution allowed)
  • LICENSE (added by AutoGineer from LICENSE)
  • ATTRIBUTION.md (written by AutoGineer)
Synced

AutoGineer is not affiliated with or endorsed by Google or Google.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download bigquery-udfs.zip