Google Cloud Product Global Search

Problem

When engineers need to confirm Google Cloud product capabilities, the pain is usually not a lack of documentation, but messy product aliases, mixed Chinese and English naming, and scattered official entry points. For example, a user may say “cloud server,” “object storage,” “K8s,” or “MySQL,” and the skill first needs to map that phrasing to official products such as Compute Engine, Cloud Storage, GKE, or Cloud SQL before finding docs, API references, or specs. This skill is intended for login-free Google Cloud product queries, helping locate official information rather than operating cloud resources.

How It Works

The skill starts by extracting product name, product category, functional requirements, and use cases from the user request, such as website hosting, backup, load balancing, e-commerce, or finance. It then normalizes colloquial names using the built-in alias table, for example mapping Redis to Memorystore, Spanner to Cloud Spanner, and Pub/Sub to Cloud Pub/Sub. After matching, it records the target product’s Chinese name, English name, category, and product code, and uses those fields to locate official documentation or product pages. For engineers, this standardizes the workflow of “ambiguous product term → official product entity → official documentation entry point,” reducing trial and error across Console, product pages, and docs.

Boundaries

It is suitable for product selection, feature confirmation, API references, parameter lookup, and spec comparison. Keep in mind that it targets public documentation and product pages, so it usually does not include current account resources, live console state, or personalized settings behind login. For pricing, quotas, regional availability, or version limits, the latest official page information should be treated as authoritative.