From alation
Manages data products: create/update/delete specs and versions, publish/unpublish to marketplaces, enrich catalog metadata with descriptions/tags/custom fields via Python CLI.
npx claudepluginhub alation/alation-plugins --plugin alationThis skill uses the workspace's default tool permissions.
Manage data products, publish to marketplaces, and enrich catalog metadata.
Mandates invoking relevant skills via tools before any response in coding sessions. Covers access, priorities, and adaptations for Claude Code, Copilot CLI, Gemini CLI.
Share bugs, ideas, or general feedback.
Manage data products, publish to marketplaces, and enrich catalog metadata.
| User Intent | CLI Command | When to Use |
|---|---|---|
| Create/update/delete data products | python -m cli product | Managing product specs and versions |
| Publish/unpublish to marketplace | python -m cli marketplace publish/unpublish | Making products discoverable |
| Manage marketplaces themselves | python -m cli marketplace | Creating or configuring marketplaces |
| Add descriptions/tags/custom fields | python -m cli enrich | Enriching metadata on any catalog object |
askexploreautomateconfigureKey distinction: curate manages data product definitions and metadata. ask runs queries against those products. "Create a data product" is curate. "Query a data product" is ask.
First, check what you already have. If a complete or near-complete spec is available (e.g. from bi product-spec, a user-provided JSON/YAML file, or a prior conversation step), use it as-is — do not discard its schema, record sets, or delivery systems. Only fall back to the empty-schema workflow when you are building a spec from scratch.
spec.json), then create the product:
python -m cli product create < spec.json
If the spec is in YAML (e.g. from bi product-spec), convert it to JSON before saving.Create product with minimal spec ("schema": []):
python -m cli product create < spec.json
See references/product-schema.md for the JSON schema.
Discover columns by querying the product (use the ask skill) or browsing the data source (use the explore skill).
Update spec with discovered schema:
python -m cli product update < updated_spec.json
Mark version ready:
python -m cli product update-version PRODUCT_ID VERSION_ID --status ready
Publish to marketplace:
python -m cli marketplace publish --marketplace EXTERNAL_MARKETPLACE_ID --product ID
python -m cli enrich list-fields — see available custom fieldspython -m cli enrich get-values --otype table --oid 123 — see current valuespython -m cli enrich set-field --otype table --oid 123 --field-id 456 --value "description text"table, schema, attribute (column), data (datasource)Mistake: Trying to publish a product whose version is still in "draft" status. Why it seems reasonable: the product exists, so it should be publishable. Instead: Check version status first. Mark it as "ready" before publishing.
Mistake: Setting deliverySystems.type to uppercase "SQL".
Why it seems reasonable: the dataAccess[].type field IS uppercase.
Instead: deliverySystems.type must be lowercase "sql". The dataAccess[].type must be uppercase "SQL". Yes, this is inconsistent — see references/product-schema.md.
After finishing curation, suggest next steps to the user — but don't proceed without their go-ahead unless their original request already implies it.