ae-metadata

CLI domain metadata routes to the analysis capability gateway (/api/cli/analysis/v1/...), using auth header cli-token.

Parallel to ae-analysis. Use this skill for gateway-backed metadata detail and data-table/dimension-table operations; use ae-analysis for metadata list/search, metrics, virtual create, and batch edit.

Global AE CLI Rules

Output and errors:

• Success: JSON envelope (default). May include optional _notice.host_compat.
• Failure: { "ok": false, "error": { "type", "message", "hint" } }, non-zero exit.
• CRITICAL — Host compat (do this first): After each ae-cli run, check stderr and _notice.host_compat. If either is present, open the user reply with a short ⚠️ version warning and quote the npm i -g / npx skills add (or update-cluster) lines verbatim, then present the business result. Soft tip; ok: true can still carry the notice.

Safety:

• Read-only commands can run directly after IDs/names are verified.
• Ordinary writes (data-table *-write, property-bindings-update, dimension-table bind/create) execute without --yes. Delete commands are high-risk-write: dry-run first, summarize impact, wait for explicit confirmation, then execute with --yes.
• Before any command, read the matching references/<name>.md (filename = command with spaces → underscores, e.g. metadata data-table list → metadata_data_table_list.md).
• Never invent project_id, event/property names, input_file_id, or data_table_id. Discover names via ae-analysis and data table IDs via metadata data-table list.
• metadata data-table download is an async artifact command: plain invocation submits, --wait waits, and --output <file> waits then streams atomically. Resume with analysis run wait; local interruption never cancels the remote run.

When to Use

Switch to ae-metadata when the user needs:

• Metadata data-table list/get/create/update/delete/download
• For local uploads, switch to ae-analysis and use analysis input-file upload with a discovered purpose.
• Bind an existing data table to a property, or create a CSV dimension table and bind it

Stay on ae-analysis for: metadata event/property detail, metadata event/property/metric list/search, metric CRUD, batch metadata, virtual create, project config, tracking plans.

Command Format

ae-cli metadata <resource> <action> [options]
ae-cli metadata property <dimension-table-action> [options]

• Commands and flags use kebab-case: data-table, dimension-table, --project-id, --data-table-id.
• Gateway input body fields remain snake_case (project_id, event_name, …); ae-cli maps flags automatically.

PROJECT_ID_GATE

Same rules as ae-analysis: reuse verified project context in one conversation; otherwise ae-cli project info list (or ae-analysis skill) to resolve project_id.

Commands (10)

Quick Verification

ae-cli metadata --help
ae-cli metadata data-table list --help
ae-cli metadata data-table list --project-id 1 --dry-run
ae-cli analysis input-file purpose list --project-id 1

Related Skills

• ae-analysis: analysis-meta event get / analysis-meta property get for detail, and analysis-meta event list / analysis-meta property list to discover names.