[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ASK4MP3D0SYBMMSXEGMJA0":3,"skill-same:01M7ASK4MP3D0SYBMMSXEGMJA0":55},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M7ASK4MP3D0SYBMMSXEGMJA0","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.","saski\u002Farnesto","saski","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F140356?v=4","01M7ASBDSNXTRYDYB4K1PEA1RV","01M7ASBDTAKBDAAV99S1GE7HK6",6,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\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":14,"metadata":23,"description":26},{"version":24,"publisher":25},"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","3c24fc2c035029b08c7326774bee3fef8fb95566",".agents\u002Fskills\u002Fgcp-pipeline-resource-provisioning",0,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto","https:\u002F\u002Fgithub.com\u002Fsaski","http:\u002F\u002Fsaski.com","2026-11-12 20:09:16",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add saski\u002Farnesto --skill gcp-pipeline-resource-provisioning",{"tool":41,"command":42},"bunx","bunx skills add saski\u002Farnesto --skill gcp-pipeline-resource-provisioning",{"tool":44,"command":45},"pnpm","pnpm dlx skills add saski\u002Farnesto --skill gcp-pipeline-resource-provisioning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgcp-pipeline-resource-provisioning\u002FSKILL.md",true,[49],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"references\u002Fgcp_pipeline_resource_provisioning_spec.md","REFERENCE","参考文档",3362,"https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fgcp-pipeline-resource-provisioning\u002Freferences\u002Fgcp_pipeline_resource_provisioning_spec.md",[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":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M7AT7F5FSHNAMFMF01N0QA1X","visualize","Use \u002Fvisualize for creating compact charts, diagrams, or other visuals inline as part of the conversation itself. It chooses among Markdown tables, Mermaid, inline HTML, and other supported in-transcript forms. Use Canvas for durable artifacts outside the transcript that users may revisit, refine, or share.","Unlicense","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fvisualize\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":18},"01M7AT79MHSAR3JDDMP7DGERM9","update-cursor-settings","Modify Cursor\u002FVSCode user settings in settings.json. Use when you want to change editor settings, preferences, configuration, themes, font size, tab size, format on save, auto save, keybindings, or any settings.json values.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cursor-settings\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":18},"01M7AT73WF3Y22E0FKYAMCCJES","update-cli-config","View and modify Cursor CLI configuration settings in ~\u002F.cursor\u002Fcli-config.json. Use when the user wants to change CLI settings, configure permissions, switch approval mode, enable vim mode, toggle display options, configure sandbox, or manage any CLI preferences.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fupdate-cli-config\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":18},"01M7AT6F3FBP85AJJ5BJNR8B5W","statusline","Configure a custom status line in the CLI. Use when the user mentions status line, statusline, statusLine, CLI status bar, prompt footer customization, or wants to add session context above the prompt.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fstatusline\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":18},"01M7AT6D24QFS5XRAFN8S5XJ7W","split-to-prs","Split current work into small reviewable PRs. Use when the user asks to split a chat, set of changes, branch, or PR.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fsplit-to-prs\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":60,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":18},"01M7AT69FYFN84XZKW452JV5DF","shell","Runs the rest of a \u002Fshell request as a literal shell command. Use only when the user explicitly invokes \u002Fshell and wants the following text executed directly in the terminal.","https:\u002F\u002Fgithub.com\u002Fsaski\u002Farnesto\u002Fblob\u002Fmain\u002F.cursor\u002Fskills-cursor\u002Fshell\u002FSKILL.md",[],[]]