discovering-gcp-data-assets

Discovers and inspects Google Cloud data assets using Dataplex search and context lookup.

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

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 topic, and retrieving schema and governance metadata requires knowing the full Dataplex entry name. This Skill guides the AI through a structured discovery workflow so you can find BigQuery tables, Spanner databases, BigLake tables, and other GCP assets without knowing their exact IDs. ## Core Features & Use Cases - Semantic and Keyword Search: Uses Dataplex entry search with natural language queries or precise keyword filters (name, column, projectid, location, labels) to locate assets. - Context Lookup: Retrieves full schema, metadata, and business context for assets via the Dataplex lookup context command using full entry names. - Fallback Handling: Falls back to native tools like the bq CLI for public datasets or assets not indexed in the Dataplex Universal Catalog, with explicit stop rules to avoid search loops. - Use Case: You ask "find Q4 product sales data" and the Skill searches Dataplex semantically, resolves the full entry name, and returns the table's schema and governance metadata. ## Quick Start Ask the AI to find the BigQuery table containing customer order data in your GCP project and show 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 a keyword or topic?▼

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

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

Semantic search accepts natural language intent and handles synonyms and plurals automatically, using uppercase AND/OR operators and plural labels. Keyword search matches exact technical strings, is case-insensitive for operators, and requires singular keywords and singular label filters.

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 Dataplex Universal Catalog. Fall back to native tools like bq show for direct inspection.

Can I use Dataplex search for bigquery-public-data datasets?▼

No, Dataplex lookup context fails for assets in the bigquery-public-data project. Inspect those tables directly using the bq CLI or BigQuery MCP tools instead of running the search workflow.

What permissions are required to search Dataplex entries?▼

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

What should I do when Dataplex search returns no results?▼

Try at most three query variations, such as switching to singular keywords, adjusting parent or projectid filters, or using fully_qualified_name. If still unsuccessful, stop and ask the user for the project, dataset, or full entry name.