Individual skill
managing-data-catalog
Writes and curates business metadata in an AWS data catalog: the Amazon SageMaker Catalog (Amazon DataZone), or the AWS Glue Data Catalog. Detects which catalog platform an account uses before writing. Triggers on: add a description to a table, document a dataset, write a README, set an owner, add column comments, tag with a glossary term, create a business glossary, create a metadata form, publish an asset, create a data product, run the data source crawl, delete a catalog asset, attach a conventions document to a table as a catalog skill asset, which assets in my project are missing descriptions or owners and what to fix first, which catalog does this account use and what can I do with it. Not for: inventorying or listing tables (use exploring-data-catalog), locating one table (use finding-data-lake-assets), counting gaps domain-wide with SQL over the exported metadata snapshot (use querying-aws-sagemaker-catalog), or granting or revoking access (use managing-data-asset-access)
plugins/aws-data-analytics/skills/managing-data-catalog/SKILL.md
Source commit 1761e96813ebcbd43ed81d19e837219033f0afe5
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 9, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 3,440
- Repository last updated
- Nov 8, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- data Derived category
- writing Derived category
- docs Derived category
- data-databases Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 17,948 bytesSKILL.mdcore · 17,948 bytesSKILL.mdcore · 17,948 bytesSKILL.mdcore · 17,948 bytesSKILL.mdcore · 17,948 bytesreferences/bulk-operations.mddoc · 1,949 bytesreferences/catalog-safety.mddoc · 6,530 bytesreferences/classifying-with-glossaries.mddoc · 6,986 bytesreferences/describing-assets.mddoc · 16,132 bytesreferences/generating-metadata.mddoc · 6,875 bytesreferences/importing-assets.mddoc · 2,989 bytesreferences/measuring-coverage.mddoc · 5,258 bytesreferences/metadata-forms.mddoc · 8,480 bytesreferences/platform-detection.mddoc · 8,697 bytesreferences/publication-lifecycle.mddoc · 12,987 bytesreferences/skill-assets.mddoc · 7,060 bytesreferences/troubleshooting.mddoc · 7,866 bytes
Read excerpt
# Manage Data Catalog
The write path for catalog business metadata. Take a dataset from catalogued
and undocumented to documented, classified and discoverable. And retire one
without breaking the catalog.
## Overview
You SHOULD execute commands through AWS MCP server tools when connected: they
give validation, sandboxed execution and audit logging, which matter more than
usual in a skill whose writes replace whole records. Fall back to the AWS CLI
when the MCP server is unavailable; every step here is expressed as CLI calls, so
it runs either way. You MUST explain each write before executing it.