[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7883MNH09CM62PRB6MJJTKV":3,"skill-same:01M7883MNH09CM62PRB6MJJTKV":59},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":32,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M7883MNH09CM62PRB6MJJTKV","gcloud",null,"Interacts with Google Cloud services using the gcloud CLI safely and efficiently. Covers command validation, data reduction, safety guardrails with a denylist, and workflows for discovery and investigation. You MUST read this skill before invoking any gcloud command. Use when managing cloud resources, querying configurations, or troubleshooting issues via gcloud. Don't use when writing or debugging Google Cloud client library code or raw REST\u002FgRPC API interactions.","Solizardking\u002Fskillhub-main","Solizardking","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F108096810?v=4","01M786KDB10AYV042N0F9BD5B5","Clawd","01M786NYYXSZK1D05WM8JQPC48",0,"MIT","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Fgoogle\u002Fcloud\u002Fgcloud\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: gcloud\nmetadata:\n  category: DevOps\ndescription: >-\n  Interacts with Google Cloud services using the gcloud CLI safely and\n  efficiently. Covers command validation, data reduction, safety guardrails with\n  a denylist, and workflows for discovery and investigation. You MUST read this\n  skill before invoking any gcloud command. Use when managing cloud resources,\n  querying configurations, or troubleshooting issues via gcloud. Don't use when\n  writing or debugging Google Cloud client library code or raw REST\u002FgRPC API\n  interactions.\n---\n\n# gcloud CLI Skill for AI Agents\n\nThis document provides essential guidelines and best practices for AI agents\ninteracting with the Google Cloud SDK (`gcloud` CLI). Following these rules is\ncritical to avoid hallucinated commands, flags, flag values, and positional\nargument syntax, prevent destructive actions, and minimize context window usage.\n\n## Getting Started\n\n### 1. Installation\n\nIf the `gcloud` executable is missing, refer to the official\n[Google Cloud CLI Installation Guide](https:\u002F\u002Fdocs.cloud.google.com\u002Fsdk\u002Fdocs\u002Finstall-sdk.md.txt)\nto install it on your platform (Linux, macOS, Windows, etc.).\n\n### 2. Authorization\n\nAuthenticate the CLI with Google Cloud. Choose the flow that matches your\nrunning environment:\n\n*   **User Account (Interactive)**: Run `gcloud auth login`. Follow the browser\n    prompts to sign in.\n*   **User Account (Headless Flow)**: If operating on a terminal without a web\n    browser (e.g. containers, remote SSH), append the `--no-browser` flag:\n    `gcloud auth login --no-browser`. Copy the URL, sign in on another machine,\n    and return the authentication code.\n*   **Application Default Credentials (ADC)**: To authenticate code calls from\n    local applications or SDK libraries, set up ADC via `gcloud auth\n    application-default login` (append `--no-browser` for headless\n    environments).\n*   **Service Account (Best for Detached\u002FHeadless Automation)**: Authenticate\n    directly using a JSON key file. Ideal for fully automated, background tasks\n    and pipelines: `gcloud auth activate-service-account\n    --key-file=path\u002Fto\u002Fkey.json`. Note that some organizations may restrict\n    access to JSON key files for security reasons.\n*   **Service Account Impersonation (Preferred for Local Pair-Programming\n    Agents)**: Leverage the human developer's existing user credentials to\n    assume a service account identity. Best for local development assistants to\n    avoid insecure private keys on human workstations: `gcloud config set\n    auth\u002Fimpersonate_service_account SERVICE_ACCT_EMAIL`\n\n*Separation of Privilege (Critical)*: Both service account approaches ensure the\nagent's permissions remain strictly distinct from the human user's wide access\nlimits (enforcing least privilege), and ensure actions are properly audited\nunder the agent's focused identity. *(Impersonation requires\n`roles\u002Fiam.serviceAccountTokenCreator`)*.\n\nFor more detailed strategies and authentication types (such as Workload Identity\nFederation), see\n[Authorizing the gcloud CLI](https:\u002F\u002Fdocs.cloud.google.com\u002Fsdk\u002Fdocs\u002Fauthorizing.md.txt).\n\n## Core Principles\n\n### 1. Explicit Command Validation (Mandatory)\n\nYour internal knowledge of `gcloud` may be stale or prone to hallucination\n(e.g., hallucinating commands, flags, flag values, or positional argument\nsyntax). You are **FORBIDDEN** from executing commands until you have validated\nthe exact syntax at the leaf level.\n\n*   **Action**: Always call `gcloud help \u003Ccommand>` for the *exact* command you\n    intend to run (e.g., `gcloud help compute instances create`).\n*   **Verify**: Ensure the command, flags, flag values, and positional argument\n    syntax are valid for that specific leaf command before attempting execution.\n    Validation is not transitive from parent groups.\n\n### 2. Data Reduction Strategies\n\nTo save context window space and reduce latency, always minimize the volume of\ndata returned by `gcloud`.\n\n*   **Projection**: Use `--format=json(key1, key2, ...)` to select only the\n    specific fields needed for your task. To understand the advanced projection\n    and formatting syntax, refer to `gcloud topic projections` and `gcloud topic\n    formats`.\n\n*   **Limiting**: Use `--limit=N` to cap the number of resources returned.\n\n*   **Filtering**: Use `--filter` to narrow down results server-side. Prioritize\n    `:` for pattern matching and never quote the right side of the colon. Treat\n    the entire filter flag as a singular string without quoting or escaping\n    characters. To study the filter expression syntax, refer to `gcloud topic\n    filters`.\n\n*   **Schema Discovery**: Unconstrained resource lists can quickly exhaust your\n    context window with redundant data. To prevent this, discover a resource's\n    schema before executing queries. If you are unsure of the JSON key path for\n    projecting fields (`--format`) or filtering (`--filter`), run the targeted\n    resource's list command (if supported) with a single-item limit:\n\n    ```bash\n    gcloud \u003CGROUP> \u003CRESOURCE> list --limit=1 --format=json\n    ```\n\n    Examine this single instance's JSON structure to safely identify the correct\n    schema keys before requesting full or filtered datasets.\n\n### 3. Execution Constraints\n\n*   **Single Commands**: Execute a single `gcloud` command at a time. No command\n    chaining or sequencing.\n*   **No Shell Operators**: Do not use command substitution (`$(...)`), pipes\n    (`|`), or redirection (`>`, `>>`, `\u003C`). This is to increase command safety\n    and ensure commands are more easily understandable and reviewable by users.\n*   **No Interactivity**: Do not run interactive commands or commands requiring\n    a TTY (e.g., `gcloud interactive`). You must enforce non-interactive mode by\n    appending `--quiet` (or `-q`) to your commands. This ensures that defaults\n    are used or errors are raised if input is required.\n\n### 4. Project and Location Scoping (Critical)\n\nTo ensure commands are deterministic, non-interactive, and target the correct\nenvironment, you must explicitly manage project and location scoping.\n\n*   **Explicit Project Target**: Do not rely on active configuration defaults.\n    Always append `--project=\u003CPROJECT_ID>` to all resource-manipulating and\n    querying commands (unless running pure local config commands). This avoids\n    accidental execution against the wrong project.\n\n*   **Prevent Location Prompts**: Many Google Cloud resources are regional or\n    zonal. If you omit the location flag (e.g., `--region`, `--zone`, or\n    `--location`), `gcloud` will trigger an interactive prompt to select a\n    zone\u002Fregion. This violates the **No Interactivity** rule. Always provide\n    explicit location flags if the command requires them.\n\n*   **Location Discovery**: If you do not know the correct region, zone, or\n    location for a service, run discovery commands first (remembering to limit\n    results if there are many):\n\n    *   **Compute Engine (VMs, Networks)**:\n\n        *   `gcloud compute regions list --project=\u003CPROJECT_ID>`\n        *   `gcloud compute zones list --project=\u003CPROJECT_ID>`\n\n    *   **Other Services (Standard API Style)**: Many GCP services utilize a\n        unified `locations list` command:\n\n        *   `gcloud \u003CGROUP> locations list --project=\u003CPROJECT_ID>`\n        *   *Examples*: `gcloud artifacts locations list`, `gcloud kms locations\n            list`, `gcloud secrets locations list`.\n\n## Safety & Guardrails\n\n> [!CAUTION] **Destructive actions (delete, update, remove) MUST be explicitly\n> authorized by the user.** Never invoke them autonomously unless explicitly\n> instructed to do so in the context of a safe, pre-approved workflow.\n\n### Prohibited Operations (Denylist)\n\nYou are **strictly prohibited** from executing the following commands\nautonomously. These require explicit human-in-the-loop authorization:\n\n*   **Any IAM policy, role, or binding modification** (Security): Risk of\n    privilege escalation, administrative lockout, service disruption, or\n    unauthorized data exposure.\n*   **No Proactive API Enabling**: Assume necessary APIs are enabled. To prevent\n    unexpected resource provisioning or billing charges, do not proactively try\n    to enable APIs. User approval is required to enable any API.\n*   **`gcloud * delete`** (Destructive): Irreversible resource destruction\n    (e.g., project deletion) or data wiping.\n*   **`gcloud billing *`** (Financial): Risk of service disruption or unbounded\n    costs.\n*   **`gcloud organizations *`** (Governance): Org-level changes affect security\n    posture for all users.\n*   **`gcloud kms *`** (Encryption): Risk of permanently locking data.\n*   **`gcloud infra-manager deployments apply`** (Destructive): Autonomous IaC\n    execution can destroy managed resources.\n\n### Execution Guidelines\n\n*   **Dry Run (Mandatory)**: You MUST invoke a command with `--dry-run` (or\n    equivalent) first if it exists, before executing the actual command, to\n    preview changes.\n\n*   **Long Running Operations**: For commands that support it, the `--async`\n    flag is highly recommended for long-running operations to avoid blocking the\n    agentic flow. Note that not every command has an `--async` flag. For\n    commands that return an operation ID (whether via `--async` or by default),\n    you are responsible for polling for completion if the operation status is\n    needed for the next step.\n\n## Structured Workflows\n\n### Discovery Workflow\n\nWhen asked to perform a task on a service you are not familiar with:\n\n1.  You MUST invoke help on a command (e.g., `gcloud help \u003CCOMMAND>`) before\n    invoking it.\n2.  If you do not know the exact command, traverse the command tree by invoking\n    help on a command group (e.g., `gcloud help compute`) to discover available\n    subcommands and groups.\n3.  **Schema Discovery**: If you need to filter or project fields from a list\n    command, but do not know the exact JSON keys, first run `gcloud \u003CGROUP>\n    \u003CRESOURCE> list --limit=1 --format=json` to safely discover the schema.\n    **Never** run a raw `list` command without scoping constraints (like\n    `--limit=1`), as unconstrained results will pollute and exhaust your context\n    window.\n4.  Execute with data reduction flags.\n\n## Quick Reference \u002F Cheat Sheet\n\nTask               | Command Template\n------------------ | ----------------------------------------------------------\nDiscover Schema    | `gcloud \u003CGROUP> \u003CRESOURCE> list --limit=1 --format=json`\nFiltered List      | `gcloud \u003CGROUP> \u003CRESOURCE> list --filter=\"status:RUNNING\"`\nSpecific Columns   | `gcloud \u003CGROUP> \u003CRESOURCE> list --format=\"json(name, id)\"`\nLearn Filters      | `gcloud topic filters`\nLearn Formats      | `gcloud topic formats`\nLearn Projections  | `gcloud topic projections`\nAsynchronous Op    | `gcloud \u003CCOMMAND> --async`\nCheck Operation    | `gcloud operations describe \u003COPERATION_ID>`\nCommon commands    | `gcloud cheat-sheet`\nList Regions (GCE) | `gcloud compute regions list --project=\u003CPROJECT_ID>`\nList Zones (GCE)   | `gcloud compute zones list --project=\u003CPROJECT_ID>`\nList Locations     | `gcloud \u003CGROUP> locations list --project=\u003CPROJECT_ID>`\n\nRefer to the\n[gcloud CLI Scripting Guide](https:\u002F\u002Fdocs.cloud.google.com\u002Fsdk\u002Fdocs\u002Fscripting-gcloud.md.txt)\nfor guidance on using the gcloud CLI in automation.\n","# gcloud CLI Skill for AI Agents\n\nThis document provides essential guidelines and best practices for AI agents\ninteracting with the Google Cloud SDK (`gcloud` CLI). Following these rules is\ncritical to avoid hallucinated commands, flags, flag values, and positional\nargument syntax, prevent destructive actions, and minimize context window usage.\n\n## Getting Started\n\n### 1. Installation\n\nIf the `gcloud` executable is missing, refer to the official\n[Google Cloud CLI Installation Guide](https:\u002F\u002Fdocs.cloud.google.com\u002Fsdk\u002Fdocs\u002Finstall-sdk.md.txt)\nto install it on your platform (Linux, macOS, Windows, etc.).\n\n### 2. Authorization\n\nAuthenticate the CLI with Google Cloud. Choose the flow that matches your\nrunning environment:\n\n*   **User Account (Interactive)**: Run `gcloud auth login`. Follow the browser\n    prompts to sign in.\n*   **User Account (Headless Flow)**: If operating on a terminal without a web\n    browser (e.g. containers, remote SSH), append the `--no-browser` flag:\n    `gcloud auth login --no-browser`. Copy the URL, sign in on another machine,\n    and return the authentication code.\n*   **Application Default Credentials (ADC)**: To authenticate code calls from\n    local applications or SDK libraries, set up ADC via `gcloud auth\n    application-default login` (append `--no-browser` for headless\n    environments).\n*   **Service Account (Best for Detached\u002FHeadless Automation)**: Authenticate\n    directly using a JSON key file. Ideal for fully automated, background tasks\n    and pipelines: `gcloud auth activate-service-account\n    --key-file=path\u002Fto\u002Fkey.json`. Note that some organizations may restrict\n    access to JSON key files for security reasons.\n*   **Service Account Impersonation (Preferred for Local Pair-Programming\n    Agents)**: Leverage the human developer's existing user credentials to\n    assume a service account identity. Best for local development assistants to\n    avoid insecure private keys on human workstations: `gcloud config set\n    auth\u002Fimpersonate_service_account SERVICE_ACCT_EMAIL`\n\n*Separation of Privilege (Critical)*: Both service account approaches ensure the\nagent's permissions remain strictly distinct from the human user's wide access\nlimits (enforcing least privilege), and ensure actions are properly audited\nunder the agent's focused identity. *(Impersonation requires\n`roles\u002Fiam.serviceAccountTokenCreator`)*.\n\nFor more detailed strategies and authentication types (such as Workload Identity\nFederation), see\n[Authorizing the gcloud CLI](https:\u002F\u002Fdocs.cloud.google.com\u002Fsdk\u002Fdocs\u002Fauthorizing.md.txt).\n\n## Core Principles\n\n### 1. Explicit Command Validation (Mandatory)\n\nYour internal knowledge of `gcloud` may be stale or prone to hallucination\n(e.g., hallucinating commands, flags, flag values, or positional argument\nsyntax). You are **FORBIDDEN** from executing commands until you have validated\nthe exact syntax at the leaf level.\n\n*   **Action**: Always call `gcloud help \u003Ccommand>` for the *exact* command you\n    intend to run (e.g., `gcloud help compute instances create`).\n*   **Verify**: Ensure the command, flags, flag values, and positional argument\n    syntax are valid for that specific leaf command before attempting execution.\n    Validation is not transitive from parent groups.\n\n### 2. Data Reduction Strategies\n\nTo save context window space and reduce latency, always minimize the volume of\ndata returned by `gcloud`.\n\n*   **Projection**: Use `--format=json(key1, key2, ...)` to select only the\n    specific fields needed for your task. To understand the advanced projection\n    and formatting syntax, refer to `gcloud topic projections` and `gcloud topic\n    formats`.\n\n*   **Limiting**: Use `--limit=N` to cap the number of resources returned.\n\n*   **Filtering**: Use `--filter` to narrow down results server-side. Prioritize\n    `:` for pattern matching and never quote the right side of the colon. Treat\n    the entire filter flag as a singular string without quoting or escaping\n    characters. To study the filter expression syntax, refer to `gcloud topic\n    filters`.\n\n*   **Schema Discovery**: Unconstrained resource lists can quickly exhaust your\n    context window with redundant data. To prevent this, discover a resource's\n    schema before executing queries. If you are unsure of the JSON key path for\n    projecting fields (`--format`) or filtering (`--filter`), run the targeted\n    resource's list command (if supported) with a single-item limit:\n\n    ```bash\n    gcloud \u003CGROUP> \u003CRESOURCE> list --limit=1 --format=json\n    ```\n\n    Examine this single instance's JSON structure to safely identify the correct\n    schema keys before requesting full or filtered datasets.\n\n### 3. Execution Constraints\n\n*   **Single Commands**: Execute a single `gcloud` command at a time. No command\n    chaining or sequencing.\n*   **No Shell Operators**: Do not use command substitution (`$(...)`), pipes\n    (`|`), or redirection (`>`, `>>`, `\u003C`). This is to increase command safety\n    and ensure commands are more easily understandable and reviewable by users.\n*   **No Interactivity**: Do not run interactive commands or commands requiring\n    a TTY (e.g., `gcloud interactive`). You must enforce non-interactive mode by\n    appending `--quiet` (or `-q`) to your commands. This ensures that defaults\n    are used or errors are raised if input is required.\n\n### 4. Project and Location Scoping (Critical)\n\nTo ensure commands are deterministic, non-interactive, and target the correct\nenvironment, you must explicitly manage project and location scoping.\n\n*   **Explicit Project Target**: Do not rely on active configuration defaults.\n    Always append `--project=\u003CPROJECT_ID>` to all resource-manipulating and\n    querying commands (unless running pure local config commands). This avoids\n    accidental execution against the wrong project.\n\n*   **Prevent Location Prompts**: Many Google Cloud resources are regional or\n    zonal. If you omit the location flag (e.g., `--region`, `--zone`, or\n    `--location`), `gcloud` will trigger an interactive prompt to select a\n    zone\u002Fregion. This violates the **No Interactivity** rule. Always provide\n    explicit location flags if the command requires them.\n\n*   **Location Discovery**: If you do not know the correct region, zone, or\n    location for a service, run discovery commands first (remembering to limit\n    results if there are many):\n\n    *   **Compute Engine (VMs, Networks)**:\n\n        *   `gcloud compute regions list --project=\u003CPROJECT_ID>`\n        *   `gcloud compute zones list --project=\u003CPROJECT_ID>`\n\n    *   **Other Services (Standard API Style)**: Many GCP services utilize a\n        unified `locations list` command:\n\n        *   `gcloud \u003CGROUP> locations list --project=\u003CPROJECT_ID>`\n        *   *Examples*: `gcloud artifacts locations list`, `gcloud kms locations\n            list`, `gcloud secrets locations list`.\n\n## Safety & Guardrails\n\n> [!CAUTION] **Destructive actions (delete, update, remove) MUST be explicitly\n> authorized by the user.** Never invoke them autonomously unless explicitly\n> instructed to do so in the context of a safe, pre-approved workflow.\n\n### Prohibited Operations (Denylist)\n\nYou are **strictly prohibited** from executing the following commands\nautonomously. These require explicit human-in-the-loop authorization:\n\n*   **Any IAM policy, role, or binding modification** (Security): Risk of\n    privilege escalation, administrative lockout, service disruption, or\n    unauthorized data exposure.\n*   **No Proactive API Enabling**: Assume necessary APIs are enabled. To prevent\n    unexpected resource provisioning or billing charges, do not proactively try\n    to enable APIs. User approval is required to enable any API.\n*   **`gcloud * delete`** (Destructive): Irreversible resource destruction\n    (e.g., project deletion) or data wiping.\n*   **`gcloud billing *`** (Financial): Risk of service disruption or unbounded\n    costs.\n*   **`gcloud organizations *`** (Governance): Org-level changes affect security\n    posture for all users.\n*   **`gcloud kms *`** (Encryption): Risk of permanently locking data.\n*   **`gcloud infra-manager deployments apply`** (Destructive): Autonomous IaC\n    execution can destroy managed resources.\n\n### Execution Guidelines\n\n*   **Dry Run (Mandatory)**: You MUST invoke a command with `--dry-run` (or\n    equivalent) first if it exists, before executing the actual command, to\n    preview changes.\n\n*   **Long Running Operations**: For commands that support it, the `--async`\n    flag is highly recommended for long-running operations to avoid blocking the\n    agentic flow. Note that not every command has an `--async` flag. For\n    commands that return an operation ID (whether via `--async` or by default),\n    you are responsible for polling for completion if the operation status is\n    needed for the next step.\n\n## Structured Workflows\n\n### Discovery Workflow\n\nWhen asked to perform a task on a service you are not familiar with:\n\n1.  You MUST invoke help on a command (e.g., `gcloud help \u003CCOMMAND>`) before\n    invoking it.\n2.  If you do not know the exact command, traverse the command tree by invoking\n    help on a command group (e.g., `gcloud help compute`) to discover available\n    subcommands and groups.\n3.  **Schema Discovery**: If you need to filter or project fields from a list\n    command, but do not know the exact JSON keys, first run `gcloud \u003CGROUP>\n    \u003CRESOURCE> list --limit=1 --format=json` to safely discover the schema.\n    **Never** run a raw `list` command without scoping constraints (like\n    `--limit=1`), as unconstrained results will pollute and exhaust your context\n    window.\n4.  Execute with data reduction flags.\n\n## Quick Reference \u002F Cheat Sheet\n\nTask               | Command Template\n------------------ | ----------------------------------------------------------\nDiscover Schema    | `gcloud \u003CGROUP> \u003CRESOURCE> list --limit=1 --format=json`\nFiltered List      | `gcloud \u003CGROUP> \u003CRESOURCE> list --filter=\"status:RUNNING\"`\nSpecific Columns   | `gcloud \u003CGROUP> \u003CRESOURCE> list --format=\"json(name, id)\"`\nLearn Filters      | `gcloud topic filters`\nLearn Formats      | `gcloud topic formats`\nLearn Projections  | `gcloud topic projections`\nAsynchronous Op    | `gcloud \u003CCOMMAND> --async`\nCheck Operation    | `gcloud operations describe \u003COPERATION_ID>`\nCommon commands    | `gcloud cheat-sheet`\nList Regions (GCE) | `gcloud compute regions list --project=\u003CPROJECT_ID>`\nList Zones (GCE)   | `gcloud compute zones list --project=\u003CPROJECT_ID>`\nList Locations     | `gcloud \u003CGROUP> locations list --project=\u003CPROJECT_ID>`\n\nRefer to the\n[gcloud CLI Scripting Guide](https:\u002F\u002Fdocs.cloud.google.com\u002Fsdk\u002Fdocs\u002Fscripting-gcloud.md.txt)\nfor guidance on using the gcloud CLI in automation.\n",{"name":5,"metadata":24,"description":7},{"category":25},"DevOps","main","be3de0244dc1a57e323d8160787ebb40fb64930e","public\u002Fapi\u002Fskills\u002Fgoogle\u002Fcloud\u002Fgcloud","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main","https:\u002F\u002Fskills.x402.wtf","https:\u002F\u002Fgithub.com\u002FSolizardking","https:\u002F\u002Fmusebook.trade","Got a mile high and never came down","2026-10-08 23:20:13",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add Solizardking\u002Fskillhub-main --skill gcloud",{"tool":41,"command":42},"bunx","bunx skills add Solizardking\u002Fskillhub-main --skill gcloud",{"tool":44,"command":45},"pnpm","pnpm dlx skills add Solizardking\u002Fskillhub-main --skill gcloud","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Fgoogle\u002Fcloud\u002Fgcloud\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"metadata.json","REFERENCE","参考文档",633,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Fgoogle\u002Fcloud\u002Fgcloud\u002Fmetadata.json",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"verification.json",1321,"https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fpublic\u002Fapi\u002Fskills\u002Fgoogle\u002Fcloud\u002Fgcloud\u002Fverification.json",[60,67,74,81,88,96],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M78E0TGCAMNPS207BA3G07S7","zkrouter","Self-hosted OpenAI-compatible LLM router — smart tier-based routing, ZK-stamped routing decisions, mode overrides, free OpenRouter at install via the Birth bot. Save 60-80% on inference costs by routing to the cheapest capable model across 12+ OpenRouter models.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzkrouter\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M78E0R1Z8BDT6EDTHY17MTNB","zk","For custom ZK Solana programs and privacy-preserving applications to prevent double spending. Guide to integrate rent-free nullifier PDAs for double-spend prevention.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzk\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M78E0P3ZTZ1YWF8MD5MM23QE","zk-omni-messaging","Zero-knowledge omnichain messaging between Robinhood Chain and Solana using CheshireZkOmniMessenger (msgType 4) with nullifier anti-replay and the zk-omni-relayer service.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzk-omni-messaging\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M78E0JXZ2PNB1896VXAGDBWD","zerion-wallet-data","Use when the user asks to check a wallet's portfolio, token balances, DeFi positions, PnL, transaction history, or NFTs. Provides interpreted on-chain data across 40+ EVM chains and Solana via x402 pay-per-request or API key — no raw RPC decoding needed.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fzerion-wallet-data\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M78E0G14FH9GRRTQYMKD5E59","youtube-clipper","YouTube 视频智能剪辑工具。下载视频和字幕，AI 分析生成精细章节（几分钟级别）， 用户选择片段后自动剪辑、翻译字幕为中英双语、烧录字幕到视频，并生成总结文案。 使用场景：当用户需要剪辑 YouTube 视频、生成短视频片段、制作双语字幕版本时。 关键词：视频剪辑、YouTube、字幕翻译、双语字幕、视频下载、clip video","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube-clipper\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":19},"01M78E0C2ZYA99CFFDNB7ZMK5S","yield-optimization","Multi-chain yield optimization via yield.xyz (StakeKit). Discover 2,988+ yield opportunities across 75+ blockchains, build deposit\u002Fwithdrawal transactions with shell scripts, and sign them with a MoonPay wallet. Use when the user wants to earn yield, find the best lending or staking rate, enter\u002Fexit a position, or check portfolio balances.","https:\u002F\u002Fgithub.com\u002FSolizardking\u002Fskillhub-main\u002Fblob\u002Fmain\u002Fskills\u002Fyield-optimization\u002FSKILL.md",[],[]]