[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7CVBZXSDDBBESVT6EWSDG4M":3,"skill-same:01M7CVBZXSDDBBESVT6EWSDG4M":56},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":14,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M7CVBZXSDDBBESVT6EWSDG4M","gcp-pipeline-resource-provisioning",null,"Automates declarative resource creation and provisioning for data pipelines, supporting BigQuery, Dataform, Dataproc, BigQuery Data Transfer Service (DTS), and other resources. It manages environment-specific configurations (dev, staging, prod) through a deployment.yaml file.\nUse when:\n- Modifying or creating deployment.yaml for deployment settings.\n- Resolving environment-specific variables (e.g., Project IDs, Regions) for deployment.\n- Provisioning supported infrastructure like BigQuery datasets\u002Ftables, Dataform resources, or DTS resources via deployment.yaml.\nDo not use when:\n- Resources already exist.\n- Managing resources not supported by `gcloud beta orchestration-pipelines resource-types list`.\n- Managing general cloud infrastructure (VMs, networks, Kubernetes, IAM policies), which are better suited for Terraform.\n- Infrastructure spans multiple cloud providers (AWS, Azure, etc.).\n- Already uses Terraform for the target resources.","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\u002Fdevops-cloud\u002Fgcp-pipeline-resource-provisioning\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gcp-pipeline-resource-provisioning\ndescription: |\n  Automates declarative resource creation and provisioning for data pipelines, supporting BigQuery, Dataform, Dataproc, BigQuery Data Transfer Service (DTS), and other resources. It manages environment-specific configurations (dev, staging, prod) through a deployment.yaml file.\n  Use when:\n  - Modifying or creating deployment.yaml for deployment settings.\n  - Resolving environment-specific variables (e.g., Project IDs, Regions) for deployment.\n  - Provisioning supported infrastructure like BigQuery datasets\u002Ftables, Dataform resources, or DTS resources via deployment.yaml.\n  Do not use when:\n  - Resources already exist.\n  - Managing resources not supported by `gcloud beta orchestration-pipelines resource-types list`.\n  - Managing general cloud infrastructure (VMs, networks, Kubernetes, IAM policies), which are better suited for Terraform.\n  - Infrastructure spans multiple cloud providers (AWS, Azure, etc.).\n  - Already uses Terraform for the target resources.\nlicense: Apache-2.0\nmetadata:\n  version: v1\n  publisher: google\n---\n\n## How to use this skill\n\nCreate or update existing `deployment.yaml` file and deploy resources. All\nconfiguration files MUST be maintained together in the repository root.\n\n### Mandatory labels\n\n> [!IMPORTANT]\n>\n> Whenever you generate resource definitions in `deployment.yaml`, you **MUST**\n> directly populate the `datacloud` label under `definition.labels` for every\n> resource to track the source of creation. Determine the value based on your\n> current IDE environment:\n>\n> -   For Antigravity, set `datacloud: \"antigravity\"`\n> -   For VS Code, set `datacloud: \"vscode\"`\n> -   For any other environment, set `datacloud: \"other\"`\n>\n> Do not use a variable substitution for this label; hardcode the appropriate\n> string value directly into each resource definition (e.g., replacing\n> `__REQUIRED_LABEL__` placeholders).\n>\n> **Special rule for BigQuery DTS Ingestion:** Whenever you generate a\n> `bigquerydatatransfer.transferConfig` in `deployment.yaml`, you **MUST** also\n> explicitly define its target destination `bigquery.dataset` in the same file\n> and apply the `datacloud` label to it. You must do this even if the dataset\n> already exists, to ensure the destination dataset's labels are patched and\n> updated.\n\n### Step 1: Supported Resource Types\n\nThe framework supports deploying various GCP resources. To see the comprehensive\nlist of supported resource types, run the following command:\n\n```\ngcloud beta orchestration-pipelines resource-types list\n```\n\nRefer to: references\u002Fgcp-pipeline-resource-provisioning_spec.md to understand\nthe template for `deployment.yaml`.\n\n### Step 2: Discover Environment Parameters\n\nBefore generating configurations, discover the actual values for the target\nproject, region, environment, and commit SHA.\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 ID**:\n\n    ```bash\n    gcloud config get project\n    ```\n\n2.  **Project Number**:\n\n    ```bash\n    gcloud projects describe $(gcloud config get project) --format=\"value(projectNumber)\"\n    ```\n\n3.  **Region**:\n\n    ```bash\n    gcloud config get-value compute\u002Fregion\n    ```\n\n4.  **Commit SHA**:\n\n    ```bash\n    git rev-parse HEAD\n    ```\n\n5.  **Environment Name**: If initialization is needed, you MUST ask the user for\n    the environment name. If the user does not provide it, use **dev** as the\n    default.\n\n> [!TIP]\n>\n> Use these commands to replace placeholders like `YOUR_PROJECT_ID` with actual\n> values. Always remove associated comments that start with TODO once replaced.\n\n### Step 3: Generate or update deployment.yaml\n\nCreate or update `deployment.yaml` in the repository root. This file maps\nsupported environments (**dev**, **stage**, **prod**) to their specific\nconfigurations and resources.\n\n> [!TIP]\n>\n> **Use the Reference Spec**: The agent can use the\n> **`references\u002Fgcp_pipeline_resource_provisioning_spec.md`** file as a\n> template. It includes sample definitions for select supported resource types.\n> Copy and adapt the required resource blocks into the `deployment.yaml`. Use\n> `gcloud beta orchestration-pipelines resource-types list` when needed.\n\n> [!IMPORTANT]\n>\n> **Handling Secrets & Privacy (CRITICAL)**: NEVER hardcode plain-text secrets\n> in `deployment.yaml`.\n>\n> -   **Sensitive Data (Secrets):** Sensitive information such as passwords, API\n>     keys, and other sensitive information MUST be stored in Secret Manager and\n>     declared in the `secrets:` block of `deployment.yaml`.\n> -   **Non-Sensitive Data (Variables):** General configuration (e.g., dataset\n>     names, table IDs, regions) could be declared in the `variables:` block.\n> -   **Substitution via `{{ VAR }}`:** Both `variables:` and `secrets:` MUST be\n>     used as `{{ VARIABLE_NAME }}` substitutions in resource definitions.\n> -   **No Creation**: The agent MUST NOT use the framework to *create* new\n>     secrets. If `gcloud` indicates the secret does not exist, the agent MUST\n>     ask the user to create it manually and then re-verify.\n> -   **Reference Only Policy**: The agent's role is strictly limited to\n>     *referencing* existing secrets. The agent MUST NEVER read, print, or\n>     inspect the values of secrets.\n> -   **Safe Deployment**: The actual value injection happens during deployment\n>     execution. The agent only provides the reference.\n> -   **Manual Secret Management**: Advise the user to manage secret payloads\n>     and versions manually.\n\n### Step 4: Validation\n\nThe agent MUST validate the `deployment.yaml` before generating the deployment\nscript. This ensures the configuration is syntactically correct and all\nvariables are resolvable.\n\n```\ngcloud beta orchestration-pipelines validate --environment=\u003CENV_NAME>\n```\n\n### Step 5: Deployment\n\nRun the following command to deploy the resources to the target environment.\n\n```\ngcloud beta orchestration-pipelines deploy --environment=\u003CENV_NAME> --local\n```\n\n> [!NOTE]\n>\n> If a new transfer is being created, make sure to NOT remove the DTS transfer\n> resource from `deployment.yaml` after it completes the run.\n\n## Definition of Done\n\n-   `deployment.yaml` exists in the repository root with actual discovered\n    values (no placeholders) and correct resource definitions.\n-   The agent runs the deployment command to perform the deployment, and it\n    executes successfully (exit code 0).\n","## How to use this skill\n\nCreate or update existing `deployment.yaml` file and deploy resources. All\nconfiguration files MUST be maintained together in the repository root.\n\n### Mandatory labels\n\n> [!IMPORTANT]\n>\n> Whenever you generate resource definitions in `deployment.yaml`, you **MUST**\n> directly populate the `datacloud` label under `definition.labels` for every\n> resource to track the source of creation. Determine the value based on your\n> current IDE environment:\n>\n> -   For Antigravity, set `datacloud: \"antigravity\"`\n> -   For VS Code, set `datacloud: \"vscode\"`\n> -   For any other environment, set `datacloud: \"other\"`\n>\n> Do not use a variable substitution for this label; hardcode the appropriate\n> string value directly into each resource definition (e.g., replacing\n> `__REQUIRED_LABEL__` placeholders).\n>\n> **Special rule for BigQuery DTS Ingestion:** Whenever you generate a\n> `bigquerydatatransfer.transferConfig` in `deployment.yaml`, you **MUST** also\n> explicitly define its target destination `bigquery.dataset` in the same file\n> and apply the `datacloud` label to it. You must do this even if the dataset\n> already exists, to ensure the destination dataset's labels are patched and\n> updated.\n\n### Step 1: Supported Resource Types\n\nThe framework supports deploying various GCP resources. To see the comprehensive\nlist of supported resource types, run the following command:\n\n```\ngcloud beta orchestration-pipelines resource-types list\n```\n\nRefer to: references\u002Fgcp-pipeline-resource-provisioning_spec.md to understand\nthe template for `deployment.yaml`.\n\n### Step 2: Discover Environment Parameters\n\nBefore generating configurations, discover the actual values for the target\nproject, region, environment, and commit SHA.\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 ID**:\n\n    ```bash\n    gcloud config get project\n    ```\n\n2.  **Project Number**:\n\n    ```bash\n    gcloud projects describe $(gcloud config get project) --format=\"value(projectNumber)\"\n    ```\n\n3.  **Region**:\n\n    ```bash\n    gcloud config get-value compute\u002Fregion\n    ```\n\n4.  **Commit SHA**:\n\n    ```bash\n    git rev-parse HEAD\n    ```\n\n5.  **Environment Name**: If initialization is needed, you MUST ask the user for\n    the environment name. If the user does not provide it, use **dev** as the\n    default.\n\n> [!TIP]\n>\n> Use these commands to replace placeholders like `YOUR_PROJECT_ID` with actual\n> values. Always remove associated comments that start with TODO once replaced.\n\n### Step 3: Generate or update deployment.yaml\n\nCreate or update `deployment.yaml` in the repository root. This file maps\nsupported environments (**dev**, **stage**, **prod**) to their specific\nconfigurations and resources.\n\n> [!TIP]\n>\n> **Use the Reference Spec**: The agent can use the\n> **`references\u002Fgcp_pipeline_resource_provisioning_spec.md`** file as a\n> template. It includes sample definitions for select supported resource types.\n> Copy and adapt the required resource blocks into the `deployment.yaml`. Use\n> `gcloud beta orchestration-pipelines resource-types list` when needed.\n\n> [!IMPORTANT]\n>\n> **Handling Secrets & Privacy (CRITICAL)**: NEVER hardcode plain-text secrets\n> in `deployment.yaml`.\n>\n> -   **Sensitive Data (Secrets):** Sensitive information such as passwords, API\n>     keys, and other sensitive information MUST be stored in Secret Manager and\n>     declared in the `secrets:` block of `deployment.yaml`.\n> -   **Non-Sensitive Data (Variables):** General configuration (e.g., dataset\n>     names, table IDs, regions) could be declared in the `variables:` block.\n> -   **Substitution via `{{ VAR }}`:** Both `variables:` and `secrets:` MUST be\n>     used as `{{ VARIABLE_NAME }}` substitutions in resource definitions.\n> -   **No Creation**: The agent MUST NOT use the framework to *create* new\n>     secrets. If `gcloud` indicates the secret does not exist, the agent MUST\n>     ask the user to create it manually and then re-verify.\n> -   **Reference Only Policy**: The agent's role is strictly limited to\n>     *referencing* existing secrets. The agent MUST NEVER read, print, or\n>     inspect the values of secrets.\n> -   **Safe Deployment**: The actual value injection happens during deployment\n>     execution. The agent only provides the reference.\n> -   **Manual Secret Management**: Advise the user to manage secret payloads\n>     and versions manually.\n\n### Step 4: Validation\n\nThe agent MUST validate the `deployment.yaml` before generating the deployment\nscript. This ensures the configuration is syntactically correct and all\nvariables are resolvable.\n\n```\ngcloud beta orchestration-pipelines validate --environment=\u003CENV_NAME>\n```\n\n### Step 5: Deployment\n\nRun the following command to deploy the resources to the target environment.\n\n```\ngcloud beta orchestration-pipelines deploy --environment=\u003CENV_NAME> --local\n```\n\n> [!NOTE]\n>\n> If a new transfer is being created, make sure to NOT remove the DTS transfer\n> resource from `deployment.yaml` after it completes the run.\n\n## Definition of Done\n\n-   `deployment.yaml` exists in the repository root with actual discovered\n    values (no placeholders) and correct resource definitions.\n-   The agent runs the deployment command to perform the deployment, and it\n    executes successfully (exit code 0).\n",{"name":5,"license":15,"metadata":24,"description":27},{"version":25,"publisher":26},"v1","google","Automates declarative resource creation and provisioning for data pipelines, supporting BigQuery, Dataform, Dataproc, BigQuery Data Transfer Service (DTS), and other resources. It manages environment-specific configurations (dev, staging, prod) through a deployment.yaml file.\nUse when:\n- Modifying or creating deployment.yaml for deployment settings.\n- Resolving environment-specific variables (e.g., Project IDs, Regions) for deployment.\n- Provisioning supported infrastructure like BigQuery datasets\u002Ftables, Dataform resources, or DTS resources via deployment.yaml.\nDo not use when:\n- Resources already exist.\n- Managing resources not supported by `gcloud beta orchestration-pipelines resource-types list`.\n- Managing general cloud infrastructure (VMs, networks, Kubernetes, IAM policies), which are better suited for Terraform.\n- Infrastructure spans multiple cloud providers (AWS, Azure, etc.).\n- Already uses Terraform for the target resources.\n","main","a73152352c0612252131e5cf84e91312a6cf17dc","devops-cloud\u002Fgcp-pipeline-resource-provisioning","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":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add Henrique1601\u002FSkiilsToIAs --skill gcp-pipeline-resource-provisioning",{"tool":42,"command":43},"bunx","bunx skills add Henrique1601\u002FSkiilsToIAs --skill gcp-pipeline-resource-provisioning",{"tool":45,"command":46},"pnpm","pnpm dlx skills add Henrique1601\u002FSkiilsToIAs --skill gcp-pipeline-resource-provisioning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fdevops-cloud\u002Fgcp-pipeline-resource-provisioning\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"references\u002Fgcp_pipeline_resource_provisioning_spec.md","REFERENCE","参考文档",3362,"https:\u002F\u002Fgithub.com\u002FHenrique1601\u002FSkiilsToIAs\u002Fblob\u002Fmain\u002Fdevops-cloud\u002Fgcp-pipeline-resource-provisioning\u002Freferences\u002Fgcp_pipeline_resource_provisioning_spec.md",[57,65,72,79,86,93],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"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":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"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":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"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":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"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":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"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":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":61,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"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",[],[]]