ae-metadata

ae-metadata

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

Use this skill for gateway-backed data-table and property dimension-table operations.

Capability contract

• Responsibilities: data-table management and dimension-table bindings through the commands below.
• Inputs: verified project, table/property identifiers and operation-specific parameters; local CSV workflows need a valid uploaded input-file identifier and purpose.
• Outputs: table/binding operation results, resource identifiers, or download run/artifact status. A submitted asynchronous download is not yet a completed file.
• Boundaries: local input-file upload, event/property detail and discovery, metric CRUD, virtual metadata, batch metadata, project configuration and tracking plans are separate capabilities.
• Completion: the requested table or binding result is verified, or pending/blocked work and its remaining requirements are reported.

Cross-skill collaboration

When remaining work is outside this skill's scope, or a necessary prerequisite needs another capability, follow the collaboration protocol. Choose from the skills available in this run by capability, preserve verified context, and continue the remaining task. Reuse this protocol if already loaded.

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. Reuse verified names or discover a metadata lookup capability; find 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

Use this skill when the user needs:

• Metadata data-table list/get/create/update/delete/download
• For local uploads, first obtain an input-file identifier through an available upload capability with the required purpose, then continue the table operation.
• Bind an existing data table to a property, or create a CSV dimension table and bind it

For out-of-scope work, discover an available capability using the collaboration protocol.

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.

PROJECTIDGATE

Reuse verified project context in one conversation; otherwise discover a project lookup capability to resolve project_id. Ask the user only when the returned projects leave a real ambiguity.

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