[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CSENPA57W63XJES9FJHY0W":3,"skill-same:01M7CSENPA57W63XJES9FJHY0W":55},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7CSENPA57W63XJES9FJHY0W","bigquery-data-transfer-service",null,"Discovers and inspects BigQuery Data Transfer Service (DTS) configurations. Use this to identify existing ingestion pipelines and extract datasource or transfer config metadata for data pipelines. Use when a user asks for ingestion scenarios while building or managing data pipelines or when a user asks to \"ingest\" or \"add\" data that may already be managed by a DTS transfer.","Henrique1601\u002FSkiilsToIAs","Henrique1601","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F92006691?v=4","01M7CRXVT0GVXVK80JT1GR687S","Henrique Bezerra Dos Santos","01M7CRXVTN5Y8TMWJ1MDSKCQ1T",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fbackend-database\u002Fbigquery-data-transfer-service\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: bigquery-data-transfer-service\ndescription: Discovers and inspects BigQuery Data Transfer Service (DTS) configurations.\n  Use this to identify existing ingestion pipelines and extract datasource or transfer\n  config metadata for data pipelines. Use when a user asks for ingestion scenarios\n  while building or managing data pipelines or when a user asks to \"ingest\" or \"add\"\n  data that may already be managed by a DTS transfer.\nlicense: Apache-2.0\nmetadata:\n  version: v1\n  publisher: google\n---\n\n# BigQuery Data Transfer Service (DTS)\n\n## Mandatory Guidelines\n\n> [!IMPORTANT]\n>\n> All new BigQuery Data Transfer Service (DTS) configurations **MUST** be\n> provisioned through the **gcp pipeline resource provisioning** framework,\n> which includes generating a `deployment.yaml`.\n>\n> -   **Do NOT** use imperative CLI commands (e.g., `bq mk` or `gcloud`) to\n>     create or update configurations.\n> -   CLI commands are permitted **only** for discovery (listing\u002Fshowing) and\n>     triggering manual runs.\n\nThis guide enables the discovery of existing ingestion resources and provides\nmetadata related to ingestion when needed.\n\n## Workflow\n\n### Step 0: Discover Environment Parameters\n\nBefore generating configurations, discover the actual values for the target\nproject and region.\n\n> [!TIP]\n>\n> If `deployment.yaml` already exists in the repository root, prioritize\n> extracting `project` and `region` from the target environment configuration\n> (e.g., `dev`).\n\n1.  **Project**: `gcloud config get project`\n2.  **Region**: `gcloud config get compute\u002Fregion`\n\n> [!TIP]\n>\n> Use these commands to replace placeholders like `\u003CPROJECT_ID>` with actual\n> values. Always remove associated comments that start with TODO once replaced.\n\n### Step 1: Check for Existing Transfers\n\nBefore assuming a new transfer is needed, check for existing ones in the target\nregion.\n\n1.  **List Transfers**:\n\n    ```bash\n    bq ls --transfer_config \\\n      --transfer_location=\u003CREGION> \\\n      --project_id=\u003CPROJECT_ID>\n    ```\n\n2.  **Analyze Existing Transfers**:\n\n    -   **Single Transfer Found**:\n\n        -   Check if the transfer has at least one successful run: `bq ls\n            --transfer_run --transfer_config=\u003CRESOURCE_NAME>`\n        -   If found: Use existing transfer config.\n        -   If not found: Confirm with user if it's ok to trigger the transfer\n            run.\n\n    -   **Multiple Transfers Found**:\n\n        -   Attempt to guess the correct one based on context.\n        -   Ask user to confirm.\n\n    -   **Disabled Transfers Found**:\n\n        -   Ask user if they want to enable it or create a new one.\n        -   To Enable: Instruct the user to update the transfer configuration\n            within their `deployment.yaml` file by setting the `disabled` field\n            to `false` for the specific transfer resource.\n\n    -   **No Transfers Found**: Proceed to create new if needed.\n\n### Step 2: Discover & Validate Parameters (New Transfers)\n\nIf creating a new transfer, discover the required parameters using the REST API\nand validate them with the user.\n\n> [!TIP]\n>\n> If `\u003CDATA_SOURCE_ID>` is unknown, run the discovery script without\n> `\u003CDATA_SOURCE_ID>` argument to list available source IDs (e.g.,\n> `google_cloud_storage`). It uses the derived project and location from Step 0.\n\n```bash\npython3 scripts\u002Fbigquery_dts.py --project_id=\u003CPROJECT_ID>\n```\n\n1.  **Run Discovery Script**: Use the `bigquery_dts.py` script to inspect Data\n    Source parameters via the REST API.\n\n    ```bash\n    # Passes the derived project and region to the script.\n    python3 scripts\u002Fbigquery_dts.py --project_id=\u003CPROJECT_ID> \u003CDATA_SOURCE_ID> \u003CREGION>\n    ```\n\n    > [!IMPORTANT]\n    >\n    > Run this command every time a new transfer is being planned.\n\n2.  > [!CAUTION]\n    >\n    > **Mandatory User Questionnaire (CRITICAL)**:\n\n    -   **Explicitly identify ALL specific parameters** returned by the\n        discovery script. **You MUST NOT generalize or vaguely summarize them.**\n    -   **OAuth Authorization (Google Data Sources)**: For Google ecosystem data\n        sources (Google Ads, Youtube, etc.), if the user is not using a service\n        account to configure the DTS transfer config (meaning the user is using\n        End User Credentials or EUC to configure the transfer config), then\n        generate an OAuth URI. Ask the user to visit this URL to authorize. Once\n        the user provides the versionInfo code, use the code as\n        `definition.versionInfo` in `deployment.yaml` and then you can proceed.\n    -   If any parameters are related to authentication, explicitly ask the user\n        to provide the Secret Manager Resource ID (e.g.,\n        projects\u002Fmy-project\u002Fsecrets\u002Fmy-secret) for these parameters\n    -   Present every required parameter to the user BEFORE generating config\n        files.\n    -   Ask for verification of assets\u002Ftables to be ingested.\n\n3.  **Wait for User Response**: You **MUST NOT** proceed until parameters are\n    confirmed.\n\n### Step 3: Extract Transfer Config Data\n\nRetrieve the configuration details for the selected transfer.\n\n```bash\nbq show --format=prettyjson --transfer_config \u003CRESOURCE_NAME>\n```\n\n### Step 4: Trigger and Verify Transfer\n\nAfter the transfer is deployed via the resource provisioning framework, you MUST\nensure there is at least a single successful run before proceeding with the rest\nof the tasks.\n\n1.  **Trigger a Manual Run**: If no successful runs or ongoing runs are found,\n    or the transfer was just created, trigger a manual run for the current time.\n\n    ```bash\n    bq mk --transfer_run \\\n      --transfer_config=\u003CRESOURCE_NAME> \\\n      --run_time=$(date -u +\"%Y-%m-%dT%H:%M:%SZ\")\n    ```\n\n2.  **Poll for Completion (5-Minute Rule)**: Attempt to check the status of the\n    run every 30-60 seconds for up to **5 minutes**.\n\n    ```bash\n    bq ls --format=prettyjson --transfer_run --transfer_config=\u003CRESOURCE_NAME>\n    ```\n\n    -   **Success**: If the run completes successfully, proceed with the rest of\n        the pipeline.\n    -   **Failure**: If the run fails, analyze the logs and ask the user for\n        help.\n    -   **Timeout (5 mins)**: If the run is still in progress after 5 minutes,\n        **STOP** and ask the user: \"The Data Transfer Service ingestion is still\n        in progress. Please provide 'proceed guidance' once the ingestion has\n        finished so that I can continue building the rest of the data pipeline\n        using the ingested schema and samples.\"\n\n3.  **Wait for User Guidance**: Do NOT proceed until the user confirms ingestion\n    is complete or provides guidance.\n\n4.  Once user confirms to proceed, start work on rest of the tasks.\n\n## Definition of Done\n\n-   A BigQuery DTS transfer configuration has been discovered or provisioned\n    declaratively (via **gcp pipeline resource provisioning** with a generated\n    `deployment.yaml`).\n-   Mandatory datasource parameters have been identified and confirmed with the\n    user.\n-   A manual transfer run has been triggered and monitored.\n-   The transfer run has completed successfully OR the user has provided\n    \"proceed guidance\" for a long-running transfer.\n","# BigQuery Data Transfer Service (DTS)\n\n## Mandatory Guidelines\n\n> [!IMPORTANT]\n>\n> All new BigQuery Data Transfer Service (DTS) configurations **MUST** be\n> provisioned through the **gcp pipeline resource provisioning** framework,\n> which includes generating a `deployment.yaml`.\n>\n> -   **Do NOT** use imperative CLI commands (e.g., `bq mk` or `gcloud`) to\n>     create or update configurations.\n> -   CLI commands are permitted **only** for discovery (listing\u002Fshowing) and\n>     triggering manual runs.\n\nThis guide enables the discovery of existing ingestion resources and provides\nmetadata related to ingestion when needed.\n\n## Workflow\n\n### Step 0: Discover Environment Parameters\n\nBefore generating configurations, discover the actual values for the target\nproject and region.\n\n> [!TIP]\n>\n> If `deployment.yaml` already exists in the repository root, prioritize\n> extracting `project` and `region` from the target environment configuration\n> (e.g., `dev`).\n\n1.  **Project**: `gcloud config get project`\n2.  **Region**: `gcloud config get compute\u002Fregion`\n\n> [!TIP]\n>\n> Use these commands to replace placeholders like `\u003CPROJECT_ID>` with actual\n> values. Always remove associated comments that start with TODO once replaced.\n\n### Step 1: Check for Existing Transfers\n\nBefore assuming a new transfer is needed, check for existing ones in the target\nregion.\n\n1.  **List Transfers**:\n\n    ```bash\n    bq ls --transfer_config \\\n      --transfer_location=\u003CREGION> \\\n      --project_id=\u003CPROJECT_ID>\n    ```\n\n2.  **Analyze Existing Transfers**:\n\n    -   **Single Transfer Found**:\n\n        -   Check if the transfer has at least one successful run: `bq ls\n            --transfer_run --transfer_config=\u003CRESOURCE_NAME>`\n        -   If found: Use existing transfer config.\n        -   If not found: Confirm with user if it's ok to trigger the transfer\n            run.\n\n    -   **Multiple Transfers Found**:\n\n        -   Attempt to guess the correct one based on context.\n        -   Ask user to confirm.\n\n    -   **Disabled Transfers Found**:\n\n        -   Ask user if they want to enable it or create a new one.\n        -   To Enable: Instruct the user to update the transfer configuration\n            within their `deployment.yaml` file by setting the `disabled` field\n            to `false` for the specific transfer resource.\n\n    -   **No Transfers Found**: Proceed to create new if needed.\n\n### Step 2: Discover & Validate Parameters (New Transfers)\n\nIf creating a new transfer, discover the required parameters using the REST API\nand validate them with the user.\n\n> [!TIP]\n>\n> If `\u003CDATA_SOURCE_ID>` is unknown, run the discovery script without\n> `\u003CDATA_SOURCE_ID>` argument to list available source IDs (e.g.,\n> `google_cloud_storage`). It uses the derived project and location from Step 0.\n\n```bash\npython3 scripts\u002Fbigquery_dts.py --project_id=\u003CPROJECT_ID>\n```\n\n1.  **Run Discovery Script**: Use the `bigquery_dts.py` script to inspect Data\n    Source parameters via the REST API.\n\n    ```bash\n    # Passes the derived project and region to the script.\n    python3 scripts\u002Fbigquery_dts.py --project_id=\u003CPROJECT_ID> \u003CDATA_SOURCE_ID> \u003CREGION>\n    ```\n\n    > [!IMPORTANT]\n    >\n    > Run this command every time a new transfer is being planned.\n\n2.  > [!CAUTION]\n    >\n    > **Mandatory User Questionnaire (CRITICAL)**:\n\n    -   **Explicitly identify ALL specific parameters** returned by the\n        discovery script. **You MUST NOT generalize or vaguely summarize them.**\n    -   **OAuth Authorization (Google Data Sources)**: For Google ecosystem data\n        sources (Google Ads, Youtube, etc.), if the user is not using a service\n        account to configure the DTS transfer config (meaning the user is using\n        End User Credentials or EUC to configure the transfer config), then\n        generate an OAuth URI. Ask the user to visit this URL to authorize. Once\n        the user provides the versionInfo code, use the code as\n        `definition.versionInfo` in `deployment.yaml` and then you can proceed.\n    -   If any parameters are related to authentication, explicitly ask the user\n        to provide the Secret Manager Resource ID (e.g.,\n        projects\u002Fmy-project\u002Fsecrets\u002Fmy-secret) for these parameters\n    -   Present every required parameter to the user BEFORE generating config\n        files.\n    -   Ask for verification of assets\u002Ftables to be ingested.\n\n3.  **Wait for User Response**: You **MUST NOT** proceed until parameters are\n    confirmed.\n\n### Step 3: Extract Transfer Config Data\n\nRetrieve the configuration details for the selected transfer.\n\n```bash\nbq show --format=prettyjson --transfer_config \u003CRESOURCE_NAME>\n```\n\n### Step 4: Trigger and Verify Transfer\n\nAfter the transfer is deployed via the resource provisioning framework, you MUST\nensure there is at least a single successful run before proceeding with the rest\nof the tasks.\n\n1.  **Trigger a Manual Run**: If no successful runs or ongoing runs are found,\n    or the transfer was just created, trigger a manual run for the current time.\n\n    ```bash\n    bq mk --transfer_run \\\n      --transfer_config=\u003CRESOURCE_NAME> \\\n      --run_time=$(date -u +\"%Y-%m-%dT%H:%M:%SZ\")\n    ```\n\n2.  **Poll for Completion (5-Minute Rule)**: Attempt to check the status of the\n    run every 30-60 seconds for up to **5 minutes**.\n\n    ```bash\n    bq ls --format=prettyjson --transfer_run --transfer_config=\u003CRESOURCE_NAME>\n    ```\n\n    -   **Success**: If the run completes successfully, proceed with the rest of\n        the pipeline.\n    -   **Failure**: If the run fails, analyze the logs and ask the user for\n        help.\n    -   **Timeout (5 mins)**: If the run is still in progress after 5 minutes,\n        **STOP** and ask the user: \"The Data Transfer Service ingestion is still\n        in progress. Please provide 'proceed guidance' once the ingestion has\n        finished so that I can continue building the rest of the data pipeline\n        using the ingested schema and samples.\"\n\n3.  **Wait for User Guidance**: Do NOT proceed until the user confirms ingestion\n    is complete or provides guidance.\n\n4.  Once user confirms to proceed, start work on rest of the tasks.\n\n## Definition of Done\n\n-   A BigQuery DTS transfer configuration has been discovered or provisioned\n    declaratively (via **gcp pipeline resource provisioning** with a generated\n    `deployment.yaml`).\n-   Mandatory datasource parameters have been identified and confirmed with the\n    user.\n-   A manual transfer run has been triggered and monitored.\n-   The transfer run has completed successfully OR the user has provided\n    \"proceed guidance\" for a long-running transfer.\n",{"name":5,"license":15,"metadata":24,"description":7},{"version":25,"publisher":26},"v1","google","main","a73152352c0612252131e5cf84e91312a6cf17dc","backend-database\u002Fbigquery-data-transfer-service","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs","https:\u002F\u002Fgithub.com\u002FHenrique1601","https:\u002F\u002Fbezerraportifolio.netlify.app\u002F","Full Stack Developer | React, Next.js, TypeScript, Node.js & IA | Construindo produtos digitais e soluções SaaS","2026-11-15 02:56:04",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill bigquery-data-transfer-service",{"tool":41,"command":42},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill bigquery-data-transfer-service",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill bigquery-data-transfer-service","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fbackend-database\u002Fbigquery-data-transfer-service\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"scripts\u002Fbigquery_dts.py","SCRIPT","脚本",4984,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fbackend-database\u002Fbigquery-data-transfer-service\u002Fscripts\u002Fbigquery_dts.py",[56,64,71,78,85,92],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M7E2ANBW9V6AVX5JXNCEAWF8","rag-architect-agent","Agente Arquiteto de RAG, Embeddings & Busca Vetorial. Especialista em design e implementação de pipelines de Retrieval-Augmented Generation de alta fidelidade: chunking semântico, modelagem pgvector no PostgreSQL (Neon\u002FSupabase), busca híbrida (cosseno + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","MIT","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fcustom-agents\u002Frag-architect-agent\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M7E29KKF8R02ZRGYE2MJM67G","rag-architecture-patterns","Padrões arquiteturais e implementação de pipelines RAG (Retrieval-Augmented Generation) de alta fidelidade para qualquer projeto ou sistema. Cobre chunking semântico, embeddings, busca híbrida (pgvector + BM25), reranking, validação via TypeSafe AI e filosofia Ponytail (anti-overengineering).","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fai-agents\u002Frag-architecture-patterns\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M7CWRA8E3BJ7CPY8N8EG28J1","skill-repair","Use this to fix and re-install agent skills that have failed installation.\nThis skill provides the necessary context and permissions to surgically update\nthe `manifest.json` after a fix has been applied.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fskill-repair\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M7CWR66FZP8FA47WVZ4Z2EXC","security-scan","Scan your Claude Code configuration (.claude\u002F directory) for security vulnerabilities, misconfigurations, and injection risks using AgentShield. Checks CLAUDE.md, settings.json, MCP servers, hooks, and agent definitions.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-scan\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7CWR0QPY58QPTR1P759TFNG","security-review","Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment\u002Fsensitive features. Provides comprehensive security checklist and patterns.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-review\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7CWQXCE40XWT4FZ3VWZFGDP","security-bounty-hunter","Hunt for exploitable, bounty-worthy security issues in repositories. Focuses on remotely reachable vulnerabilities that qualify for real reports instead of noisy local-only findings.","https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Futilities\u002Fsecurity-bounty-hunter\u002FSKILL.md",[],[]]