discovering-gcp-data-assets

Searches Dataplex Universal Catalog and retrieves schema metadata for Google Cloud data assets.

Updated Aug 11, 2026
One-click install
npx skills add https://github.com/Yashyasik/zexca-api --skill discovering-gcp-data-assets-yashyasik
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: discovering-gcp-data-assets
Source: https://github.com/Yashyasik/zexca-api/tree/main/.gemini/skills/discovering-gcp-data-assets
Command: npx skills add https://github.com/Yashyasik/zexca-api --skill discovering-gcp-data-assets-yashyasik

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Locating the right data asset in Google Cloud is difficult when you only have a keyword or business topic, and retrieving schema or governance metadata requires knowing exact resource identifiers. This Skill uses Dataplex search and context lookup to find BigQuery, Spanner, BigLake, and Cloud Storage assets and return their full metadata. ## Core Features & Use Cases - Semantic and Keyword Search: Find data assets by natural language intent (e.g., "Q4 product sales data") or precise technical queries (e.g., name:order_v2, system=bigquery). - Schema and Metadata Lookup: Retrieve detailed schema, business context, and governance metadata via the Dataplex Lookup Context command using full entry names. - Public Dataset Handling: Directly inspect bigquery-public-data assets with the bq CLI when Dataplex lookup is unavailable. - Use Case: A data analyst knows a table contains sales data but not its name. The Skill searches Dataplex semantically, resolves the full entry name, and returns the table's schema and column descriptions. ## Quick Start Find the BigQuery table containing customer order data in my GCP project and show me its schema.

Frequently Asked Questions about discovering-gcp-data-assets

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I find a BigQuery table when I only know the topic?▼

Use Dataplex semantic search with a natural language query describing the data, such as "Q4 product sales data". The search returns full entry names, which you then pass to the context lookup command to retrieve the table's schema and metadata.

How to search Dataplex for GCP data assets with gcloud?▼

Run `gcloud dataplex entries search "<QUERY>" --project="<PROJECT_ID>" --limit=50`, adding `--semantic-search` for natural language queries. The `--project` flag is mandatory and is used for attribution, not to restrict search scope.

What is the difference between Dataplex semantic and keyword search?▼

Semantic search interprets natural language intent and handles synonyms and plurals automatically, requiring uppercase AND/OR operators. Keyword search matches exact technical strings, is case-insensitive for operators, and requires singular terms and `=` for fields like system, type, and location.

Why does Dataplex context lookup fail with NOT_FOUND?▼

Lookup fails if you pass a short table ID instead of the full entry name starting with `projects/`, or if the asset's project has not synchronized metadata with the Universal Catalog. For public datasets like bigquery-public-data, fall back to direct inspection with the `bq` CLI.

What permissions are required for Dataplex asset search?▼

The project passed via `--project` must have the Dataplex API enabled, and the user must hold the dataplex.entries.get IAM permission. Without these, searches fail with PERMISSION_DENIED errors.

When should I use bq CLI instead of Dataplex search?▼

Use the `bq` CLI directly for assets in the bigquery-public-data project, since Dataplex lookup fails there. It is also the recommended fallback when an asset is not indexed in the Universal Catalog and you already know its exact project, dataset, and table IDs.