[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M698ZXCY2PAFZR6BRZ75F0S5":3,"skill-same:01M698ZXCY2PAFZR6BRZ75F0S5":220},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":31,"publishedAt":51,"linkOnly":52,"markdownContent":53,"markdownBody":54,"frontMatter":55,"refName":59,"commitSha":60,"skillDirectory":61,"forksCount":62,"repositoryHtmlUrl":63,"repositoryHomepageUrl":6,"ownerHtmlUrl":64,"ownerBlogUrl":65,"ownerDescription":66,"updatedAt":67,"install":68,"resources":81},"01M698ZXCY2PAFZR6BRZ75F0S5","bigquery-migration-sql-translator",null,"Translates SQL queries, DDL schemas, and stored procedures from legacy database dialects (Teradata, Oracle, Redshift, Snowflake, SparkSQL, HiveQL) to BigQuery GoogleSQL using the BigQuery Migration Service (BQMS) MCP server. Use when translating legacy SQL queries, migrating schemas or metadata zip archives, or configuring BigQuery Migration Service (BQMS) YAML translation settings. Don't use for executing BigQuery queries or managing datasets and tables (use bigquery-basics), diagnosing runtime job errors (use bigquery-troubleshooting), or tuning slot reservations (use bigquery-optimization).","google\u002Fskills","google","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1342004?v=4","01M698VYEFDM0VJBZDYYJ2T83S","Google","01M698WR0H76ENHE587T9EJT89",24122,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002FSKILL.md",[18,23,26],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":27,"categoryName":28,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,9],"bigquery migration sql translator","sql","bigquery","migration","translator","server","when","zip","tables","errors","translation","sql queries","tuning","MCP","snowflake","redshift","database","mcp server","oracle","2026-11-10 10:12:30",false,"---\nname: bigquery-migration-sql-translator\nmetadata:\n  version: \"1.0.2\"\n  category: BigDataAndAnalytics\n  publisher: google\ndescription: >-\n  Translates SQL queries, DDL schemas, and stored procedures from legacy database\n  dialects (Teradata, Oracle, Redshift, Snowflake, SparkSQL, HiveQL) to BigQuery\n  GoogleSQL using the BigQuery Migration Service (BQMS) MCP server. Use when\n  translating legacy SQL queries, migrating schemas or metadata zip archives,\n  or configuring BigQuery Migration Service (BQMS) YAML translation settings.\n  Don't use for executing BigQuery queries or managing datasets and tables (use\n  bigquery-basics), diagnosing runtime job errors (use bigquery-troubleshooting),\n  or tuning slot reservations (use bigquery-optimization).\n---\n\n# BigQuery Migration Service (BQMS) SQL Translator\n\nThe BigQuery Migration Service (BQMS) translates legacy database SQL scripts,\nqueries, and schemas into GoogleSQL. This skill coordinates translation\nworkflows, Cloud Storage staging, compiler error triage, and YAML configuration.\n\n## Usage Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read and follow the instructions in\n[Usage Attribution](references\u002Fattribution.md).\n\n## Before you begin\n\nBefore translating queries or schemas, verify the following prerequisites:\n\n1.  **Google Cloud SDK & Project Setup**: Ensure the\n    [Google Cloud SDK](https:\u002F\u002Fcloud.google.com\u002Fsdk\u002Fdocs\u002Finstall) is installed,\n    verify that your Google Cloud project has an active Cloud Billing account\n    attached, and select the target project:\n\n    ```bash\n    gcloud config set project {project_id}\n    ```\n\n2.  **Enable the API**: Enable the BigQuery Migration API\n    (`bigquerymigration.googleapis.com`) in your Google Cloud project:\n\n    ```bash\n    gcloud services enable bigquerymigration.googleapis.com\n    ```\n\n3.  **Required IAM Roles**: Verify that your identity or service account has:\n    -   `roles\u002Fmcp.toolUser` (MCP Tool User)\n    -   `roles\u002Fbigquerymigration.editor` (Migration Workflow Editor)\n    -   For batch translation, `roles\u002Fstorage.objectViewer` and\n        `roles\u002Fstorage.objectCreator` (or `roles\u002Fstorage.objectAdmin`) on the\n        Cloud Storage buckets that hold the input and output files.\n4.  **MCP Server Connection**: If BigQuery Migration Service (BQMS) tools (e.g.\n    `translate_query`, `translate_batch_queries`) are not present in your active\n    tool list, configure the remote BigQuery Migration Service (BQMS) MCP\n    server. For setup instructions across clients (Claude, Cursor, Gemini CLI,\n    VS Code), see [mcp_config.md](references\u002Fmcp_config.md).\n5.  **Cost & Cloud Storage Cleanup**: Review\n    [Google Cloud Pricing](https:\u002F\u002Fcloud.google.com\u002Fpricing) for Cloud Storage\n    and BigQuery usage details. After completing a batch migration, clean up\n    temporary staged input and output folders in Cloud Storage:\n\n    ```bash\n    gcloud storage rm -r gs:\u002F\u002F{bucket}\u002F{folder}\n    ```\n\n6.  **Translation Tracking**: For batch translations, and for queries that need\n    more than one translation iteration, keep a translation tracker (e.g.\n    `translation_tracker.md`) to document goals, planned steps, and progress.\n    After each translation, record one row with this template:\n\n    Iteration | Status | Total Errors | Correctness Errors | Completeness Errors | Compatibility Errors | Key Actions \u002F Transformations\n    --------- | ------ | ------------ | ------------------ | ------------------- | -------------------- | -----------------------------\n\n    A single query that translates cleanly on the first attempt needs no\n    tracker: report its translation ID and logs in your response.\n\n## Workflow Selection\n\nChoose the workflow based on your migration scope:\n\n-   **Interactive Translation (Single Query)**: Best for ad-hoc queries,\n    exploratory testing, dialect syntax comparison, or quick error debugging.\n-   **Batch Translation (Multiple Files & Cloud Storage)**: Use for more than\n    one file or a directory, including SQL embedded in application code (extract\n    it into `.sql` files first). For multi-file Python codebases containing\n    embedded SQL, use\n    [python_embedded_sql_migrator_template.py](assets\u002Fpython_embedded_sql_migrator_template.py)\n    to extract queries into staged files and re-inject translated SQL. Batch\n    translation is faster and cheaper than translating files one by one, and it\n    resolves cross-file dependencies, so it usually gives better results. Run\n    `translate_batch_queries` on the staged files first; use `translate_query`\n    only afterwards if needed to debug a specific statement from\n    `translation_report.csv`.\n\n## 1. Interactive Translation Workflow\n\nUse the interactive workflow to translate a single query string, inspect\ncompiler logs, and iteratively resolve issues.\n\n### Steps\n\n1.  **Submit Query (`translate_query`)**: Call `translate_query` with\n    `projectNumber`, `location`, `inputQuery`, `sourceDialect`, and\n    `targetDialect` (`BigQuery`). Include optional parameters:\n\n    -   `metadataFilePath`: Cloud Storage URI to a metadata zip file\n        (`gs:\u002F\u002F...\u002Fmetadata.zip`) for schema resolution.\n    -   `translationConfigs`: Inline YAML configurations (e.g. object renaming,\n        schema redirection, optimizer rules). Show the YAML you used in your\n        response so the user can reuse it (e.g. in batch translation).\n\n2.  **Poll Status (`get_translation`)**: If the returned `translation_state` is\n    `RUNNING` or `PENDING`, poll `get_translation` using the `translation` ID,\n    `projectNumber`, and `location` until `translation.state` is `SUCCEEDED` or\n    `FAILED`, at the interval given in the BigQuery Migration Service (BQMS) MCP\n    tool descriptions. While the job runs, do work that doesn't need the result\n    (e.g. read the dialect gotchas reference).\n\n3.  **Inspect Output & Logs**:\n\n    -   Examine `translated_query` for the converted GoogleSQL.\n    -   Review each entry in `translation_logs`: inspect `severity` (`ERROR`,\n        `WARNING`), `category` (e.g. `RelationNotFound`), and `effect`\n        (`CORRECTNESS`, `COMPLETENESS`, `COMPATIBILITY`).\n    -   Check the SQL itself, not only the logs: BigQuery Migration Service\n        (BQMS) emits `ERROR_TYPE(...)` for types it cannot map, sometimes with\n        no log entry. Treat any `ERROR_TYPE` or inline error comment as an\n        error, and when a BigQuery project is available, dry-run the result (`bq\n        query --dry_run --use_legacy_sql=false`). A `Not found` or `must be\n        qualified with a dataset` error still means the SQL is syntactically\n        valid; the referenced objects just don't exist in BigQuery yet. Say so\n        and move on, even if the error suggests a fix: don't stub tables or\n        change the SQL or `bq` flags to get past it.\n    -   A `NoSuchFunction` error means BigQuery Migration Service (BQMS) copied\n        that call unchanged, sometimes with the function name in backticks.\n        Treat it as untranslated even if BigQuery has a function with that name:\n        a dry run that stops at missing tables doesn't check it.\n    -   If the source dialect has a gotchas reference (see\n        [Dialect-Specific Gotchas](#dialect-specific-gotchas)), read it and\n        check the output for the patterns it lists. Some semantic differences\n        produce no log entry and still pass a dry run.\n\n4.  **Iterate Until Clean**: If the logs contain errors or warnings, the\n    translated SQL contains `ERROR_TYPE` or inline error comments, the dry run\n    fails, or the output matches a dialect gotcha, resolve the issues as\n    described in [Resolving Translation Issues](#resolving-translation-issues)\n    and re-translate.\n\n5.  **Explain & Compare Differences (`explain_translation`)**: When requested to\n    explain a translation, compare syntax differences, or understand how\n    specific query logic was converted, call `explain_translation` with\n    `translation` (the translation ID), `projectNumber`, and `location`. This\n    returns a structured explanation of the query's purpose and a detailed\n    breakdown of syntax, function, and behavioral differences between the source\n    query and the translated GoogleSQL. The explanation doesn't validate the\n    output, so check the translation as in step 3 rather than relying on it.\n\n## 2. Batch Translation Workflow\n\nBatch translation handles multiple files staged in Cloud Storage. It resolves\ncross-file dependencies and produces a consolidated translation summary report\n(`translation_report.csv`).\n\n### Steps\n\n1.  **Stage Input Files to Cloud Storage**: Upload the raw SQL files,\n    configuration files (`*.config.yaml`), and any metadata file from the local\n    workspace to a Cloud Storage input folder:\n\n    ```bash\n    gcloud storage cp input\u002F*.sql gs:\u002F\u002Fmy-bucket\u002Fmigration\u002Finput\u002F\n    gcloud storage cp *.config.yaml gs:\u002F\u002Fmy-bucket\u002Fmigration\u002Finput\u002F\n    ```\n\n    *Note: Do not pass configuration file paths in tool parameters if those\n    files are already located inside `sourceBaseUri`.*\n\n    Use new, empty Cloud Storage input and output folders for each run (e.g.\n    with a timestamp suffix). Stage only files from the local workspace or\n    generated in this run. Never reuse or copy inputs, DDL, or outputs that are\n    already in a bucket from earlier runs: they may come from different inputs\n    or settings.\n\n2.  **Initiate Batch Translation**:\n\n    -   **Translating SQL Queries (`translate_batch_queries`)**: Call\n        `translate_batch_queries` with `projectNumber`, `location`,\n        `sourceDialect`, `targetDialect`, `sourceBaseUri`, and `targetBaseUri`.\n    -   **Translating Metadata Zip Files (`translate_metadata`)**: To aid batch\n        translation by generating target BigQuery DDL schema definitions from an\n        extracted database metadata zip file (`metadata.zip` from Teradata,\n        Oracle, etc.), call `translate_metadata` specifying `sourceBaseUri`\n        (Cloud Storage URI to `metadata.zip`) and `targetBaseUri` (destination\n        Cloud Storage folder).\n\n3.  **Poll Completion (`fetch_batch_translation`)**: Poll using the returned\n    workflow ID until `translation.state` is `SUCCEEDED` or `FAILED`, at the\n    interval given in the BigQuery Migration Service (BQMS) MCP tool\n    descriptions.\n\n4.  **Retrieve & Inspect Outputs**: Download the generated files from\n    `translation.target_base_uri`:\n\n    ```bash\n    gcloud storage cp -r gs:\u002F\u002Fmy-bucket\u002Fmigration\u002Foutput\u002F .\u002Flocal_output\u002F\n    ```\n\n    Locate and inspect `report\u002Ftranslation_report.csv` to review all warnings,\n    errors, and line-level diagnostics. Then scan the generated `.sql` files for\n    `ERROR_TYPE(...)` and inline error comments, which the report can miss, and\n    dry-run the generated SQL when a BigQuery project is available (handle `Not\n    found` errors as in the interactive workflow). Check the output for the\n    patterns in the source dialect's gotchas reference, if one exists. Resolve\n    or clearly report every remaining issue; do not describe the output as clean\n    until this check passes.\n\n5.  **Iterate Until Clean**: Resolve the issues found in step 4 as described in\n    [Resolving Translation Issues](#resolving-translation-issues), and re-run\n    from step 1 with the changed inputs.\n\n6.  **Post-processing (Final Step Only)**: Only after resolving every compiler\n    error that re-translation can fix, execute any application-level\n    post-processing (e.g. AST re-injection) to restore host source files.\n    [effect_correctness.md](references\u002Feffect_correctness.md) lists the errors\n    that may remain when re-injecting embedded SQL.\n\n## Resolving Translation Issues\n\nBoth workflows resolve issues the same way:\n\n-   Identify the **Effect** (`CORRECTNESS`, `COMPLETENESS`, `COMPATIBILITY`) of\n    each issue, and resolve them in order of compiler phase dependencies:\n    `CORRECTNESS` (parse errors) first, then `COMPLETENESS` (missing objects),\n    then `COMPATIBILITY` (unsupported features).\n-   **MUST Read the Reference Guide** for each effect in\n    [Troubleshooting by Error Effect](#troubleshooting-by-error-effect) BEFORE\n    applying fixes, and follow its resolution workflow.\n-   Fixes can preprocess the input (e.g. prepend DDL) or post-process the\n    BigQuery Migration Service (BQMS) output (e.g. a rewrite that a dialect\n    gotcha calls for). Run BigQuery Migration Service (BQMS) on the preprocessed\n    input rather than translating it yourself.\n-   Keep the source system's dialect for every re-translation. Another dialect\n    may accept the same SQL but translate it with different semantics (e.g.\n    return types, numeric types, or identifier case), so don't switch dialects\n    to get cleaner output.\n-   Rewrites of the BigQuery Migration Service (BQMS) output, including\n    optimizations the user asks for, must return the same rows as the source\n    query. For example, a filter that runs after a row limit (`TOP`, `LIMIT`)\n    can't be merged into the query before the limit.\n-   Wait for each re-translation to finish, record its translation ID, error\n    counts, and any pre- or post-processing in the tracker, and compare the\n    counts with the previous iteration. Repeat until no errors remain or all\n    options are exhausted.\n-   Report the final SQL from the tracked iteration, the pre- and\n    post-processing you applied, and any errors that remain.\n\n## Reference Lookup Index\n\nUse these reference guides when troubleshooting errors or authoring\nconfiguration files:\n\n### Troubleshooting by Error Effect\n\nEffect          | Common Causes                                                                              | Reference Guide\n:-------------- | :----------------------------------------------------------------------------------------- | :--------------\n`CORRECTNESS`   | Syntax errors, unescaped literals, application script wrappers, `NoSuchFunction`.          | [effect_correctness.md](references\u002Feffect_correctness.md)\n`COMPLETENESS`  | Missing tables, views, columns (`RelationNotFound`, `AttributeNotFound`), DDL suggestions. | [effect_completeness.md](references\u002Feffect_completeness.md)\n`COMPATIBILITY` | Functions or features without direct GoogleSQL mapping.                                    | [effect_compatibility.md](references\u002Feffect_compatibility.md)\n\n### Configuration & Setup Guides\n\nTask                    | Description                                                                                                                                                                                                                                                              | Reference Guide\n:---------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------\n**YAML Configurations** | Database\u002Fschema redirection, name mapping, table partitioning and clustering injection, optimizer transformations, statement rewriters, and environment settings. Schemas in `assets\u002Ftranslation_config_schemas\u002F` and examples in `assets\u002Ftranslation_config_examples\u002F`. | [translation_yaml_config.md](references\u002Ftranslation_yaml_config.md)\n**MCP Server Setup**    | Configuring the remote BigQuery Migration Service (BQMS) MCP server, OAuth scopes, and IAM roles.                                                                                                                                                                        | [mcp_config.md](references\u002Fmcp_config.md)\n\n### Dialect-Specific Gotchas\n\nDialect       | Key Considerations                                                    | Reference Guide\n:------------ | :-------------------------------------------------------------------- | :--------------\n**Teradata**  | SET\u002FMULTISET tables, `SAMPLE` clause, primary index mapping.          | [teradata_gotchas.md](references\u002Fteradata_gotchas.md)\n**Oracle**    | PL\u002FSQL procedures, `ROWNUM` emulation, outer join `(+)`, sequences.   | [oracle_gotchas.md](references\u002Foracle_gotchas.md)\n**Snowflake** | Dynamic templates, `USE` statements, metadata merging, lateral joins. | [snowflake_gotchas.md](references\u002Fsnowflake_gotchas.md)\n","# BigQuery Migration Service (BQMS) SQL Translator\n\nThe BigQuery Migration Service (BQMS) translates legacy database SQL scripts,\nqueries, and schemas into GoogleSQL. This skill coordinates translation\nworkflows, Cloud Storage staging, compiler error triage, and YAML configuration.\n\n## Usage Attribution\n\n**MUST READ**: Before executing any `gcloud`, REST API, or MCP command, you\nMUST read and follow the instructions in\n[Usage Attribution](references\u002Fattribution.md).\n\n## Before you begin\n\nBefore translating queries or schemas, verify the following prerequisites:\n\n1.  **Google Cloud SDK & Project Setup**: Ensure the\n    [Google Cloud SDK](https:\u002F\u002Fcloud.google.com\u002Fsdk\u002Fdocs\u002Finstall) is installed,\n    verify that your Google Cloud project has an active Cloud Billing account\n    attached, and select the target project:\n\n    ```bash\n    gcloud config set project {project_id}\n    ```\n\n2.  **Enable the API**: Enable the BigQuery Migration API\n    (`bigquerymigration.googleapis.com`) in your Google Cloud project:\n\n    ```bash\n    gcloud services enable bigquerymigration.googleapis.com\n    ```\n\n3.  **Required IAM Roles**: Verify that your identity or service account has:\n    -   `roles\u002Fmcp.toolUser` (MCP Tool User)\n    -   `roles\u002Fbigquerymigration.editor` (Migration Workflow Editor)\n    -   For batch translation, `roles\u002Fstorage.objectViewer` and\n        `roles\u002Fstorage.objectCreator` (or `roles\u002Fstorage.objectAdmin`) on the\n        Cloud Storage buckets that hold the input and output files.\n4.  **MCP Server Connection**: If BigQuery Migration Service (BQMS) tools (e.g.\n    `translate_query`, `translate_batch_queries`) are not present in your active\n    tool list, configure the remote BigQuery Migration Service (BQMS) MCP\n    server. For setup instructions across clients (Claude, Cursor, Gemini CLI,\n    VS Code), see [mcp_config.md](references\u002Fmcp_config.md).\n5.  **Cost & Cloud Storage Cleanup**: Review\n    [Google Cloud Pricing](https:\u002F\u002Fcloud.google.com\u002Fpricing) for Cloud Storage\n    and BigQuery usage details. After completing a batch migration, clean up\n    temporary staged input and output folders in Cloud Storage:\n\n    ```bash\n    gcloud storage rm -r gs:\u002F\u002F{bucket}\u002F{folder}\n    ```\n\n6.  **Translation Tracking**: For batch translations, and for queries that need\n    more than one translation iteration, keep a translation tracker (e.g.\n    `translation_tracker.md`) to document goals, planned steps, and progress.\n    After each translation, record one row with this template:\n\n    Iteration | Status | Total Errors | Correctness Errors | Completeness Errors | Compatibility Errors | Key Actions \u002F Transformations\n    --------- | ------ | ------------ | ------------------ | ------------------- | -------------------- | -----------------------------\n\n    A single query that translates cleanly on the first attempt needs no\n    tracker: report its translation ID and logs in your response.\n\n## Workflow Selection\n\nChoose the workflow based on your migration scope:\n\n-   **Interactive Translation (Single Query)**: Best for ad-hoc queries,\n    exploratory testing, dialect syntax comparison, or quick error debugging.\n-   **Batch Translation (Multiple Files & Cloud Storage)**: Use for more than\n    one file or a directory, including SQL embedded in application code (extract\n    it into `.sql` files first). For multi-file Python codebases containing\n    embedded SQL, use\n    [python_embedded_sql_migrator_template.py](assets\u002Fpython_embedded_sql_migrator_template.py)\n    to extract queries into staged files and re-inject translated SQL. Batch\n    translation is faster and cheaper than translating files one by one, and it\n    resolves cross-file dependencies, so it usually gives better results. Run\n    `translate_batch_queries` on the staged files first; use `translate_query`\n    only afterwards if needed to debug a specific statement from\n    `translation_report.csv`.\n\n## 1. Interactive Translation Workflow\n\nUse the interactive workflow to translate a single query string, inspect\ncompiler logs, and iteratively resolve issues.\n\n### Steps\n\n1.  **Submit Query (`translate_query`)**: Call `translate_query` with\n    `projectNumber`, `location`, `inputQuery`, `sourceDialect`, and\n    `targetDialect` (`BigQuery`). Include optional parameters:\n\n    -   `metadataFilePath`: Cloud Storage URI to a metadata zip file\n        (`gs:\u002F\u002F...\u002Fmetadata.zip`) for schema resolution.\n    -   `translationConfigs`: Inline YAML configurations (e.g. object renaming,\n        schema redirection, optimizer rules). Show the YAML you used in your\n        response so the user can reuse it (e.g. in batch translation).\n\n2.  **Poll Status (`get_translation`)**: If the returned `translation_state` is\n    `RUNNING` or `PENDING`, poll `get_translation` using the `translation` ID,\n    `projectNumber`, and `location` until `translation.state` is `SUCCEEDED` or\n    `FAILED`, at the interval given in the BigQuery Migration Service (BQMS) MCP\n    tool descriptions. While the job runs, do work that doesn't need the result\n    (e.g. read the dialect gotchas reference).\n\n3.  **Inspect Output & Logs**:\n\n    -   Examine `translated_query` for the converted GoogleSQL.\n    -   Review each entry in `translation_logs`: inspect `severity` (`ERROR`,\n        `WARNING`), `category` (e.g. `RelationNotFound`), and `effect`\n        (`CORRECTNESS`, `COMPLETENESS`, `COMPATIBILITY`).\n    -   Check the SQL itself, not only the logs: BigQuery Migration Service\n        (BQMS) emits `ERROR_TYPE(...)` for types it cannot map, sometimes with\n        no log entry. Treat any `ERROR_TYPE` or inline error comment as an\n        error, and when a BigQuery project is available, dry-run the result (`bq\n        query --dry_run --use_legacy_sql=false`). A `Not found` or `must be\n        qualified with a dataset` error still means the SQL is syntactically\n        valid; the referenced objects just don't exist in BigQuery yet. Say so\n        and move on, even if the error suggests a fix: don't stub tables or\n        change the SQL or `bq` flags to get past it.\n    -   A `NoSuchFunction` error means BigQuery Migration Service (BQMS) copied\n        that call unchanged, sometimes with the function name in backticks.\n        Treat it as untranslated even if BigQuery has a function with that name:\n        a dry run that stops at missing tables doesn't check it.\n    -   If the source dialect has a gotchas reference (see\n        [Dialect-Specific Gotchas](#dialect-specific-gotchas)), read it and\n        check the output for the patterns it lists. Some semantic differences\n        produce no log entry and still pass a dry run.\n\n4.  **Iterate Until Clean**: If the logs contain errors or warnings, the\n    translated SQL contains `ERROR_TYPE` or inline error comments, the dry run\n    fails, or the output matches a dialect gotcha, resolve the issues as\n    described in [Resolving Translation Issues](#resolving-translation-issues)\n    and re-translate.\n\n5.  **Explain & Compare Differences (`explain_translation`)**: When requested to\n    explain a translation, compare syntax differences, or understand how\n    specific query logic was converted, call `explain_translation` with\n    `translation` (the translation ID), `projectNumber`, and `location`. This\n    returns a structured explanation of the query's purpose and a detailed\n    breakdown of syntax, function, and behavioral differences between the source\n    query and the translated GoogleSQL. The explanation doesn't validate the\n    output, so check the translation as in step 3 rather than relying on it.\n\n## 2. Batch Translation Workflow\n\nBatch translation handles multiple files staged in Cloud Storage. It resolves\ncross-file dependencies and produces a consolidated translation summary report\n(`translation_report.csv`).\n\n### Steps\n\n1.  **Stage Input Files to Cloud Storage**: Upload the raw SQL files,\n    configuration files (`*.config.yaml`), and any metadata file from the local\n    workspace to a Cloud Storage input folder:\n\n    ```bash\n    gcloud storage cp input\u002F*.sql gs:\u002F\u002Fmy-bucket\u002Fmigration\u002Finput\u002F\n    gcloud storage cp *.config.yaml gs:\u002F\u002Fmy-bucket\u002Fmigration\u002Finput\u002F\n    ```\n\n    *Note: Do not pass configuration file paths in tool parameters if those\n    files are already located inside `sourceBaseUri`.*\n\n    Use new, empty Cloud Storage input and output folders for each run (e.g.\n    with a timestamp suffix). Stage only files from the local workspace or\n    generated in this run. Never reuse or copy inputs, DDL, or outputs that are\n    already in a bucket from earlier runs: they may come from different inputs\n    or settings.\n\n2.  **Initiate Batch Translation**:\n\n    -   **Translating SQL Queries (`translate_batch_queries`)**: Call\n        `translate_batch_queries` with `projectNumber`, `location`,\n        `sourceDialect`, `targetDialect`, `sourceBaseUri`, and `targetBaseUri`.\n    -   **Translating Metadata Zip Files (`translate_metadata`)**: To aid batch\n        translation by generating target BigQuery DDL schema definitions from an\n        extracted database metadata zip file (`metadata.zip` from Teradata,\n        Oracle, etc.), call `translate_metadata` specifying `sourceBaseUri`\n        (Cloud Storage URI to `metadata.zip`) and `targetBaseUri` (destination\n        Cloud Storage folder).\n\n3.  **Poll Completion (`fetch_batch_translation`)**: Poll using the returned\n    workflow ID until `translation.state` is `SUCCEEDED` or `FAILED`, at the\n    interval given in the BigQuery Migration Service (BQMS) MCP tool\n    descriptions.\n\n4.  **Retrieve & Inspect Outputs**: Download the generated files from\n    `translation.target_base_uri`:\n\n    ```bash\n    gcloud storage cp -r gs:\u002F\u002Fmy-bucket\u002Fmigration\u002Foutput\u002F .\u002Flocal_output\u002F\n    ```\n\n    Locate and inspect `report\u002Ftranslation_report.csv` to review all warnings,\n    errors, and line-level diagnostics. Then scan the generated `.sql` files for\n    `ERROR_TYPE(...)` and inline error comments, which the report can miss, and\n    dry-run the generated SQL when a BigQuery project is available (handle `Not\n    found` errors as in the interactive workflow). Check the output for the\n    patterns in the source dialect's gotchas reference, if one exists. Resolve\n    or clearly report every remaining issue; do not describe the output as clean\n    until this check passes.\n\n5.  **Iterate Until Clean**: Resolve the issues found in step 4 as described in\n    [Resolving Translation Issues](#resolving-translation-issues), and re-run\n    from step 1 with the changed inputs.\n\n6.  **Post-processing (Final Step Only)**: Only after resolving every compiler\n    error that re-translation can fix, execute any application-level\n    post-processing (e.g. AST re-injection) to restore host source files.\n    [effect_correctness.md](references\u002Feffect_correctness.md) lists the errors\n    that may remain when re-injecting embedded SQL.\n\n## Resolving Translation Issues\n\nBoth workflows resolve issues the same way:\n\n-   Identify the **Effect** (`CORRECTNESS`, `COMPLETENESS`, `COMPATIBILITY`) of\n    each issue, and resolve them in order of compiler phase dependencies:\n    `CORRECTNESS` (parse errors) first, then `COMPLETENESS` (missing objects),\n    then `COMPATIBILITY` (unsupported features).\n-   **MUST Read the Reference Guide** for each effect in\n    [Troubleshooting by Error Effect](#troubleshooting-by-error-effect) BEFORE\n    applying fixes, and follow its resolution workflow.\n-   Fixes can preprocess the input (e.g. prepend DDL) or post-process the\n    BigQuery Migration Service (BQMS) output (e.g. a rewrite that a dialect\n    gotcha calls for). Run BigQuery Migration Service (BQMS) on the preprocessed\n    input rather than translating it yourself.\n-   Keep the source system's dialect for every re-translation. Another dialect\n    may accept the same SQL but translate it with different semantics (e.g.\n    return types, numeric types, or identifier case), so don't switch dialects\n    to get cleaner output.\n-   Rewrites of the BigQuery Migration Service (BQMS) output, including\n    optimizations the user asks for, must return the same rows as the source\n    query. For example, a filter that runs after a row limit (`TOP`, `LIMIT`)\n    can't be merged into the query before the limit.\n-   Wait for each re-translation to finish, record its translation ID, error\n    counts, and any pre- or post-processing in the tracker, and compare the\n    counts with the previous iteration. Repeat until no errors remain or all\n    options are exhausted.\n-   Report the final SQL from the tracked iteration, the pre- and\n    post-processing you applied, and any errors that remain.\n\n## Reference Lookup Index\n\nUse these reference guides when troubleshooting errors or authoring\nconfiguration files:\n\n### Troubleshooting by Error Effect\n\nEffect          | Common Causes                                                                              | Reference Guide\n:-------------- | :----------------------------------------------------------------------------------------- | :--------------\n`CORRECTNESS`   | Syntax errors, unescaped literals, application script wrappers, `NoSuchFunction`.          | [effect_correctness.md](references\u002Feffect_correctness.md)\n`COMPLETENESS`  | Missing tables, views, columns (`RelationNotFound`, `AttributeNotFound`), DDL suggestions. | [effect_completeness.md](references\u002Feffect_completeness.md)\n`COMPATIBILITY` | Functions or features without direct GoogleSQL mapping.                                    | [effect_compatibility.md](references\u002Feffect_compatibility.md)\n\n### Configuration & Setup Guides\n\nTask                    | Description                                                                                                                                                                                                                                                              | Reference Guide\n:---------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :--------------\n**YAML Configurations** | Database\u002Fschema redirection, name mapping, table partitioning and clustering injection, optimizer transformations, statement rewriters, and environment settings. Schemas in `assets\u002Ftranslation_config_schemas\u002F` and examples in `assets\u002Ftranslation_config_examples\u002F`. | [translation_yaml_config.md](references\u002Ftranslation_yaml_config.md)\n**MCP Server Setup**    | Configuring the remote BigQuery Migration Service (BQMS) MCP server, OAuth scopes, and IAM roles.                                                                                                                                                                        | [mcp_config.md](references\u002Fmcp_config.md)\n\n### Dialect-Specific Gotchas\n\nDialect       | Key Considerations                                                    | Reference Guide\n:------------ | :-------------------------------------------------------------------- | :--------------\n**Teradata**  | SET\u002FMULTISET tables, `SAMPLE` clause, primary index mapping.          | [teradata_gotchas.md](references\u002Fteradata_gotchas.md)\n**Oracle**    | PL\u002FSQL procedures, `ROWNUM` emulation, outer join `(+)`, sequences.   | [oracle_gotchas.md](references\u002Foracle_gotchas.md)\n**Snowflake** | Dynamic templates, `USE` statements, metadata merging, lateral joins. | [snowflake_gotchas.md](references\u002Fsnowflake_gotchas.md)\n",{"name":5,"metadata":56,"description":7},{"version":57,"category":58,"publisher":9},"1.0.2","BigDataAndAnalytics","main","bb9b3f464aae37af360d079c1d863524955b0363","skills\u002Fcloud\u002Fbigquery-migration-sql-translator",2005,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills","https:\u002F\u002Fgithub.com\u002Fgoogle","https:\u002F\u002Fopensource.google\u002F","Google ❤️ Open Source","2026-11-14 01:51:35",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add google\u002Fskills --skill bigquery-migration-sql-translator",{"tool":74,"command":75},"bunx","bunx skills add google\u002Fskills --skill bigquery-migration-sql-translator",{"tool":77,"command":78},"pnpm","pnpm dlx skills add google\u002Fskills --skill bigquery-migration-sql-translator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002FSKILL.md",true,[82,88,94,98,102,106,110,114,118,122,126,130,134,138,142,146,150,154,158,162,166,170,174,178,182,188,192,196,200,204,208,212,216],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"assets\u002Fpython_embedded_sql_migrator_template.py","SCRIPT","脚本",42785,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Fpython_embedded_sql_migrator_template.py",{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":93},"assets\u002Ftranslation_config_examples\u002Fenvironment_example.yaml","ASSET","资产文件",167,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_examples\u002Fenvironment_example.yaml",{"path":95,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":96,"sourceHtmlUrl":97},"assets\u002Ftranslation_config_examples\u002Fexperimental_input_formats_example.yaml",213,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_examples\u002Fexperimental_input_formats_example.yaml",{"path":99,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":100,"sourceHtmlUrl":101},"assets\u002Ftranslation_config_examples\u002Fexperimental_metadata_example.yaml",147,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_examples\u002Fexperimental_metadata_example.yaml",{"path":103,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":104,"sourceHtmlUrl":105},"assets\u002Ftranslation_config_examples\u002Fexperimental_object_rewriter_example.yaml",1541,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_examples\u002Fexperimental_object_rewriter_example.yaml",{"path":107,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":108,"sourceHtmlUrl":109},"assets\u002Ftranslation_config_examples\u002Fexperimental_optimizer_example.yaml",348,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_examples\u002Fexperimental_optimizer_example.yaml",{"path":111,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":112,"sourceHtmlUrl":113},"assets\u002Ftranslation_config_examples\u002Fexperimental_statement_rewriter_example.yaml",400,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_examples\u002Fexperimental_statement_rewriter_example.yaml",{"path":115,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":116,"sourceHtmlUrl":117},"assets\u002Ftranslation_config_examples\u002Finput_formats_example.yaml",200,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_examples\u002Finput_formats_example.yaml",{"path":119,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":120,"sourceHtmlUrl":121},"assets\u002Ftranslation_config_examples\u002Fmetadata_example.yaml",168,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_examples\u002Fmetadata_example.yaml",{"path":123,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":124,"sourceHtmlUrl":125},"assets\u002Ftranslation_config_examples\u002Fobject_rewriter_example.yaml",673,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_examples\u002Fobject_rewriter_example.yaml",{"path":127,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":128,"sourceHtmlUrl":129},"assets\u002Ftranslation_config_examples\u002Foptimizer_example.yaml",335,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_examples\u002Foptimizer_example.yaml",{"path":131,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":132,"sourceHtmlUrl":133},"assets\u002Ftranslation_config_examples\u002Fstatement_rewriter_example.yaml",387,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_examples\u002Fstatement_rewriter_example.yaml",{"path":135,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":136,"sourceHtmlUrl":137},"assets\u002Ftranslation_config_schemas\u002Fenvironment.json",498,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_schemas\u002Fenvironment.json",{"path":139,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":140,"sourceHtmlUrl":141},"assets\u002Ftranslation_config_schemas\u002Fexperimental_input_formats.json",976,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_schemas\u002Fexperimental_input_formats.json",{"path":143,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":144,"sourceHtmlUrl":145},"assets\u002Ftranslation_config_schemas\u002Fexperimental_metadata.json",629,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_schemas\u002Fexperimental_metadata.json",{"path":147,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":148,"sourceHtmlUrl":149},"assets\u002Ftranslation_config_schemas\u002Fexperimental_object_rewriter.json",19961,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_schemas\u002Fexperimental_object_rewriter.json",{"path":151,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":152,"sourceHtmlUrl":153},"assets\u002Ftranslation_config_schemas\u002Fexperimental_optimizer.json",635,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_schemas\u002Fexperimental_optimizer.json",{"path":155,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":156,"sourceHtmlUrl":157},"assets\u002Ftranslation_config_schemas\u002Fexperimental_statement_rewriter.json",1292,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_schemas\u002Fexperimental_statement_rewriter.json",{"path":159,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":160,"sourceHtmlUrl":161},"assets\u002Ftranslation_config_schemas\u002Finput_formats.json",963,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_schemas\u002Finput_formats.json",{"path":163,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":164,"sourceHtmlUrl":165},"assets\u002Ftranslation_config_schemas\u002Fmetadata.json",876,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_schemas\u002Fmetadata.json",{"path":167,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":168,"sourceHtmlUrl":169},"assets\u002Ftranslation_config_schemas\u002Fobject_rewriter.json",9376,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_schemas\u002Fobject_rewriter.json",{"path":171,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":172,"sourceHtmlUrl":173},"assets\u002Ftranslation_config_schemas\u002Foptimizer.json",622,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_schemas\u002Foptimizer.json",{"path":175,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":176,"sourceHtmlUrl":177},"assets\u002Ftranslation_config_schemas\u002Fstatement_rewriter.json",1279,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_schemas\u002Fstatement_rewriter.json",{"path":179,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":180,"sourceHtmlUrl":181},"assets\u002Ftranslation_config_schemas\u002Ftranspiler_config_spec.json",39803,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Fassets\u002Ftranslation_config_schemas\u002Ftranspiler_config_spec.json",{"path":183,"resourceType":184,"resourceTypeDesc":185,"sizeBytes":186,"sourceHtmlUrl":187},"references\u002Fattribution.md","REFERENCE","参考文档",1951,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Freferences\u002Fattribution.md",{"path":189,"resourceType":184,"resourceTypeDesc":185,"sizeBytes":190,"sourceHtmlUrl":191},"references\u002Feffect_compatibility.md",2346,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Freferences\u002Feffect_compatibility.md",{"path":193,"resourceType":184,"resourceTypeDesc":185,"sizeBytes":194,"sourceHtmlUrl":195},"references\u002Feffect_completeness.md",5225,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Freferences\u002Feffect_completeness.md",{"path":197,"resourceType":184,"resourceTypeDesc":185,"sizeBytes":198,"sourceHtmlUrl":199},"references\u002Feffect_correctness.md",8819,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Freferences\u002Feffect_correctness.md",{"path":201,"resourceType":184,"resourceTypeDesc":185,"sizeBytes":202,"sourceHtmlUrl":203},"references\u002Fmcp_config.md",10246,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Freferences\u002Fmcp_config.md",{"path":205,"resourceType":184,"resourceTypeDesc":185,"sizeBytes":206,"sourceHtmlUrl":207},"references\u002Foracle_gotchas.md",3223,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Freferences\u002Foracle_gotchas.md",{"path":209,"resourceType":184,"resourceTypeDesc":185,"sizeBytes":210,"sourceHtmlUrl":211},"references\u002Fsnowflake_gotchas.md",7591,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Freferences\u002Fsnowflake_gotchas.md",{"path":213,"resourceType":184,"resourceTypeDesc":185,"sizeBytes":214,"sourceHtmlUrl":215},"references\u002Fteradata_gotchas.md",2474,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Freferences\u002Fteradata_gotchas.md",{"path":217,"resourceType":184,"resourceTypeDesc":185,"sizeBytes":218,"sourceHtmlUrl":219},"references\u002Ftranslation_yaml_config.md",12629,"https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fbigquery-migration-sql-translator\u002Freferences\u002Ftranslation_yaml_config.md",[221,255,282,309,336,360],{"skillNo":222,"name":223,"nameZh":6,"description":224,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":225,"categories":226,"keywords":231,"publishedAt":51},"01M6998S2EZKD3GEJ7F943RZTE","sign-in-with-google-web","Implement, configure, and secure Sign In With Google (SiwG) using Google Identity Services (GIS \u002F `https:\u002F\u002Faccounts.google.com\u002Fgsi\u002Fclient`) across web architectures. Use when creating Google sign-in buttons, implementing Google One Tap with FedCM, integrating GIS in React\u002FNext.js\u002FAngular\u002FHTML, verifying ID tokens on backend runtimes (Python\u002FNode.js\u002FGo\u002FJava), enforcing Google Workspace domain restrictions (`hd`), securing client-side ID tokens via WebCrypto nonces or encrypted IndexedDB, embedding in cross-origin iframes via the Intermediate Iframe API (`https:\u002F\u002Faccounts.google.com\u002Fgsi\u002Fintermediate`), configuring Content Security Policy (CSP), COOP, and Permissions Policy (`identity-credentials-get`) headers, or handling sign-out and revocation. Don't use for legacy Google Sign-In (`gapi.auth2`), Google Cloud IAM service accounts, or Android\u002FiOS native Credential Manager.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fidentity\u002Fsign-in-with-google-web\u002FSKILL.md",[227,230],{"categoryNo":228,"categoryName":229,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000009","前端开发",{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[9,232,233,234,235,236,237,238,239,240,241,242,243,244,245,246,247,248,249,250,251,252,253,254],"sign in with google web","sign","with","web","android","go","security","google workspace","google cloud","implement","policy","python","implementing","react","iam","permissions","buttons","secure","manager","identity","architectures","domain","runtimes",{"skillNo":256,"name":257,"nameZh":6,"description":258,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":259,"categories":260,"keywords":266,"publishedAt":51},"01M6998PHPDCAD684VW5WRG83D","dpop-adoption","Implement and debug OAuth 2.0 DPoP (RFC 9449) refresh token sender-constraining for WebCrypto, Node.js ES6, and browser runtimes integrating with Google's OAuth platform. Use when configuring non-extractable asymmetric key pairs (P-256), generating DPoP Proof JWTs for authorization code exchange and token refresh, or handling 400 use_dpop_nonce challenge retry loops at oauth2.googleapis.com\u002Ftoken. Don't use for unconstrained OAuth 2.0 flows (where refresh tokens are not bound to a client key pair), or for Google Cloud IAM \u002F service account authentication.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fidentity\u002Fdpop-adoption\u002FSKILL.md",[261,262,263],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":264,"categoryName":265,"taxonomyType":29,"taxonomyTypeDesc":30},"01JBSEEDCAT000000000000030","开发工程师",[267,268,9,240,269,270,271,272,273,274,246,275,276,277,278,279,280,251,254,281,38],"dpop adoption","adoption","es6","retry","authentication","flows","challenge","code","browser","loops","at","node","token","pair","platform",{"skillNo":283,"name":284,"nameZh":6,"description":285,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":286,"categories":287,"keywords":294,"publishedAt":51},"01M6998M72TC73EEAQH4XC7EXW","retrieving-developer-knowledge","Searches, retrieves, and synthesizes official Google developer documentation across Google Cloud, AI\u002FGemini, Android, Chrome, Web, Flutter, Go, Firebase, and other Google developer platforms. Integrates with the Developer Knowledge MCP server (search_documents, get_documents, answer_query) or the Developer Knowledge REST API fallback. Use when searching for gcloud CLI commands, API syntax, IAM permissions, official documentation, architectural comparisons, or product choice overviews. Don't use for local filesystem lookups or non-Google documentation.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Fretrieving-developer-knowledge\u002FSKILL.md",[288,289,292,293],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":290,"categoryName":291,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":264,"categoryName":265,"taxonomyType":29,"taxonomyTypeDesc":30},[295,296,297,45,240,49,298,299,300,301,302,303,304,38,305,306,307,246,308,247],"retrieving developer knowledge","knowledge","developer","official","developer documentation","get","search","local","choice","documents","query","api","across","documentation",{"skillNo":310,"name":311,"nameZh":6,"description":312,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":313,"categories":314,"keywords":315,"publishedAt":51},"01M6998J2CZEXS9BES9S3WWFKC","migrate-to-rust","Clones, analyzes, plans, and migrates legacy codebases (C++, Fortran, Java, Python, C, Shell) from a GitHub URL or local directory to a modern, high-performance, deterministic, 100% Safe Rust architecture, tracking live telemetry across every task bucket, test failure\u002Ffix cycle, and Profile-Guided Optimization (PGO) stage, and producing a first-person AI storytelling report and interactive HTML infographic. Use when migrating a GitHub repository or local codebase to Rust, porting legacy C++, Fortran, Python, or Java workloads to memory-safe Rust, designing Struct-of-Arrays (SoA) or SIMD Rust architectures, or optimizing Rust ports with LLVM PGO. Don't use for unrelated non-Rust refactoring or single-line syntax questions.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Fmigrate-to-rust\u002FSKILL.md",[],[316,317,318,319,320,321,322,323,243,324,325,326,327,328,329,302,330,331,332,38,333,334,307,335],"migrate to rust","rust","migrate","github","memory","performance","directory","safe","ports","llvm","soa","cycle","porting","fix","arrays","infographic","high-performance","URL","architecture","unrelated",{"skillNo":337,"name":338,"nameZh":6,"description":339,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":340,"categories":341,"keywords":345,"publishedAt":51},"01M6998GCC3K29WZ82KXMB9E02","finding-google-skills","Google platform decision and setup guidance, loaded on demand from Google's skill catalog. Use when a developer is choosing or setting up part of their stack, such as where to run a service, a database, storage, messaging, authentication, analytics, ads, or AI model serving, and a Google product is a reasonable candidate - whether or not a vendor is named - or when a request names a Google product or API. Brings in the matching Google skill so the answer can weigh Google options, their trade-offs, and when they are not the right fit. Skip when the stack is already settled on another provider and no Google product is named, or the task involves no platform choice.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopers\u002Ffinding-google-skills\u002FSKILL.md",[342,343,344],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":264,"categoryName":265,"taxonomyType":29,"taxonomyTypeDesc":30},[9,346,347,348,349,281,350,351,352,353,354,271,355,356,357,303,358,48,38,359,306],"finding google skills","storage","as","messaging","model","trade-offs","provider","answer","fit","catalog","up","decision","use","candidate",{"skillNo":361,"name":362,"nameZh":6,"description":363,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":364,"categories":365,"keywords":368,"publishedAt":51},"01M6998DWNHTH0BS6W1CY8ZXMP","workload-manager-basics","Use this skill to manage Google Cloud Workload Manager evaluations, rules, scanned resources, and validation results by using public client libraries and the REST API. Use when you need to inspect workload best-practice rules, create and run evaluations for Google Cloud general best practices, SAP, SQL Server, or custom organizational rules, review violations, export results to BigQuery, or automate Workload Manager through client libraries because no service-specific public CLI or MCP server is available. Don't use for general Google Compute Engine instance management, VPC configuration, or standard IAM auditing.","https:\u002F\u002Fgithub.com\u002Fgoogle\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fcloud\u002Fworkload-manager-basics\u002FSKILL.md",[366,367],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},[369,370,250,371,9,45,372,240,49,373,374,375,376,38,377,306,246,378,379,37,380],"workload manager basics","workload","basics","cli","review","vpc","resources","inspect","you","create","libraries","run"]