knowledge-catalog
Installation
SKILL.md
Knowledge Catalog repository
Instructions
- Route by component, not name. This exact repository contains tools, agent samples, and examples around Google Cloud Knowledge Catalog/Dataplex. It is not a standalone database implementation, and its own README says the repository is not an official Google product.
- Identify the path: OKF
reference-agentenrichment, mdcode'skcmdsemantic-model workflow, or a particular sample. Consultreferences/upstream.mdandreferences/source.jsonfor the pinned entry points before advising. - Separate local transformation from cloud operations. The mdcode semantic emitter is a pure IR-to-resource mapping; deployment orchestration reads/writes catalog entries and links.
initprovisions destination scaffolding;pushis a cloud write/reconcile operation. Do not describe a code-generation dry-run as a deployment or assumepushprovisions entry group/types. - Keep scope and version explicit. Use pinned source evidence as a snapshot, then inspect the user's checkout and current CLI help for drift. Record destination project, location, entry group, model scope, and feature flags before explaining a push.
- Gate external effects individually. Approval is required before installing packages, downloading/cloning sources, changing credentials/config, logging in or authorizing Google Cloud, reading private documents, accessing cloud projects, creating cloud resources, writing catalog entries/links, destructive reconciliation, public service activation, or paid uploads. A local dry-run is not authorization to apply.
- Troubleshoot with evidence. Compare source/model validation, destination type availability, IAM permission and entry-group scope, preflight snapshot, apply result, and reconciliation separately. Do not retry a possibly completed write without reading destination state first.
- Link the pinned evidence, source manifest, evals, and parent preflight helper. That helper hashes only listed source files; it cannot prove HEAD, dependency state, cloud configuration, or runtime behavior.
Examples
- "Explain why
kcmd pushfailed for my semantic model." → Inspect model scope, required custom types, destination permissions and preflight result before suggesting an apply. - "Is knowledge-catalog a Google database product?" → Clarify the repo's sample/tool nature and explicit non-official-product disclaimer.
- "Set up a new independent vector database." → Route to database/platform selection, not this repository-specific skill.