Knowledge Catalog Discovery
ClineOfficialPublished by Cline
- Skill
- Tool integration
- Data and AI
- Apache-2.0
- Low risk
- Has scripts
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
The knowledge-catalog-discovery skill provides a set of tools to interact with a data catalog platform. It enables users to search for specific data assets like tables, datasets, or views, retrieve detailed metadata for individual entries, and explore available aspect types. By leveraging these scripts, users can programmatically navigate their data landscape, understand asset relationships, and perform targeted queries to manage data platform information efficiently.
What it does
- Searches for data assets using specific queries and filtering criteria.
- Retrieves detailed metadata for individual data entries.
- Fetches rich context and relationship information for multiple data assets.
- Searches for and identifies relevant aspect types within the catalog.
- Supports pagination and ordering for search results to optimize performance.
When to use it
- When you need to locate specific data assets within a large catalog.
- When you need to inspect the metadata or schema of a particular table or view.
- When you are mapping data lineage or relationships between different assets.
- When you need to identify which aspect types are available for data classification or tagging.
Advantages
- Simplifies complex catalog queries through a standardized interface.
- Provides granular control over metadata retrieval views.
- Supports efficient searching with logical operators and scoping.
- Automates the discovery process for data platform assets.
Usage examples
- “Find all tables related to customer data in the project 'analytics-prod'.”
- The agent uses search_entries with a query like 'type:table AND customer' and a scope set to the project ID to return a list of matching assets.
- “Get the full metadata for the table located at projects/my-proj/locations/us/entryGroups/main/entries/users.”
- The agent executes lookup_entry with the provided resource name and the view parameter set to 4 to retrieve all available aspects.
Install
Download the skill as a ZIP:
https://mp-staging.autogineer.com/agent-skills/cline/knowledge-catalog-discovery/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip knowledge-catalog-discovery.zip -d .agents/skills
Documentation by Cline
Usage
All scripts can be executed using Node.js. Replace <param_name> and <param_value> with actual values.
Bash:
node <skill_dir>/scripts/<script_name>.js '{"<param_name>": "<param_value>"}'
PowerShell:
node <skill_dir>/scripts/<script_name>.js '{\"<param_name>\": \"<param_value>\"}'
Note: The scripts automatically load the environment variables from various .env files. Do not ask the user to set vars unless skill executions fails due to env var absence.
Scripts
lookup_context
Retrieves rich metadata regarding one or more data assets along with their relationships.
Parameters
| Name | Type | Description | Required | Default |
|---|---|---|---|---|
| resources | array | Required. A list of up to 10 resource names. Resources may belong to different projects, but all must belong to the same location. | Yes |
lookup_entry
Retrieves a specific metadata regarding a data asset (e.g. table/dataset/view) from Catalog
Parameters
| Name | Type | Description | Required | Default |
|---|---|---|---|---|
| entry | string | Required. The resource name of the Entry in the following form: projects/{project}/locations/{location}/entryGroups/{entryGroup}/entries/{entry}. | Yes | |
| view | integer |
## Argument: view
**Type:** Integer
**Description:** Optional. Specifies the parts of the entry and its aspects to return.
**Possible Values:**
* 1 (BASIC): Returns entry without aspects.
* 2 (FULL): Return all required aspects and the keys of non-required aspects. (Default)
* 3 (CUSTOM): Return the entry and aspects requested in aspect_types field (at most 100 aspects). Always use this view when aspect_types is not empty.
* 4 (ALL): Return the entry and both required and optional aspects (at most 100 aspects)
| No | `2` |
| aspectTypes | array | Optional. Limits the aspects returned to the provided aspect types. It only works when used together with CUSTOM view. | No | [] |
search_aspect_types
Search aspect types relevant to the query.
Parameters
| Name | Type | Description | Required | Default |
|---|---|---|---|---|
| query | string | The query against which aspect type should be matched. | Yes | |
| pageSize | integer | Number of returned aspect types in the search page. | No | 5 |
| orderBy | string | Specifies the ordering of results. Supported values are: relevance, last_modified_timestamp, last_modified_timestamp asc | No | relevance |
search_entries
Searches for data assets (eg. table/dataset/view) in Catalog based on the provided search query.
Parameters
| Name | Type | Description | Required | Default |
|---|---|---|---|---|
| query | string | A query string for searching entries, following Dataplex search syntax. Supports logical operators (AND, OR, NOT) and grouping. For example, to find a table that might have been renamed, you could use 'type:table (name:books OR fiction)'. This can be more efficient than multiple separate calls.Warning: Performing broad searches without specific filters (e.g., type:table) can be slow and consume significant resources. When performing exploratory searches, always use the pageSize parameter to limit the number of results returned. | Yes | |
| scope | string | A scope limits the search space to a particular project or organization. It must be in the format: organizations/<org_id> or projects/<project_id> or projects/<project_number>. | No | `` |
| pageSize | integer | Number of results in the search page. | No | 5 |
| orderBy | string | Specifies the ordering of results. Supported values are: relevance, last_modified_timestamp, last_modified_timestamp asc | No | relevance |
Files
- ATTRIBUTION.mdAdded by AutoGineer860 B
- LICENSELicence file added by AutoGineer10.5 KiB
- SKILL.md4.0 KiB
- scripts/lookup_context.jsScript2.8 KiB
- scripts/lookup_entry.jsScript2.8 KiB
- scripts/search_aspect_types.jsScript2.8 KiB
- scripts/search_entries.jsScript2.8 KiB
ATTRIBUTION.md
Attribution
This folder is an unmodified copy of the Agent Skill "knowledge-catalog-discovery", distributed by AutoGineer (https://autogineer.com/agent-skills).
Commit: 26378461e978f2b4e2e6d67b57121b86b2a79ba5
Published by: Cline (https://github.com/cline)
Publisher: Cline (https://github.com/cline)
Licence: Apache License 2.0 (https://github.com/cline/skills/blob/26378461e978f2b4e2e6d67b57121b86b2a79ba5/LICENSE)
Licence evidence: repository licence LICENSE
Retrieved: 2026-11-07
The skill's own files are unmodified copies. AutoGineer is not affiliated with or endorsed by the author or the publisher.
Files added by AutoGineer
ATTRIBUTION.md: this file, written by AutoGineer
LICENSE: copied from LICENSE
Requirements and compatibility
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Needs Node.js
Security
What our scanner noticed· Low risk
- Scripts that your agent may run
This skill includes scripts that your agent may run. Read them before you use it.
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Cline
- Publisher
- Cline (Official)
- Source
- cline/skills · skills/knowledge-catalog-discovery · commit 2637846
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Cline.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download knowledge-catalog-discovery.zip