ae-metadata

AE/TE metadata capability-gateway CLI: metadata data-table management and property dimension-table binding. Metadata CLI routes through the analysis gateway. Input-file upload and event/property detail belong to ae-analysis.

By thinkingaiagenticengine · 474 installs

npx skills add thinkingaiagenticengine/ae-cli --skill ae-metadata

Source repository · Upstream listing

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. Data table get can include saved SQL definitions, parameters, and schedule configuration on supported servers; read its reference for availability and execution value limits. 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](references/collaboration.md). 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 Parameter Description format <json\ table Output format. Default JSON. jq <expr jq filter on JSON output. host <url Override active AE host, e.g. ae cli metadata data table list host <url ... . validate Optional: fix params only ( /validate ). Alone while iterating complex qp / payload — then run. Do not stack with dry run . dry run Optional: confirm ready to run ( /dry run ). Alone for risk/output preview. Do not stack with validate . 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. The member's natural day quota counts every Gateway capability execute call eligible for usage statistics (an identifiable user and statistics enabled), including metadata only reads, previews, table/binding writes, asset exports, and downloads that submit work. It does not depend on database engine or business purpose. Cache hits, repeated calls, reused runs, and failures within execute count, including schema errors, permission denials, and unknown capability IDs. Gateway capability discovery (list/inspect), validate/dry run, and separate run status/artifact download HTTP endpoints do not count; pagination and cancellation through capability execution do count. On QUERY DAILY LIMIT EXCEEDED (HTTP 429), wait until reset or contact an administrator; QUERY QUOTA UNAVAILABLE fails explicitly. Do not switch identities to bypass these errors. Omit download timeout seconds to use the server default; inspect the selected capability for its current policy. 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 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 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) User command Capability id Reference metadata data table list metadata.data table.list [metadata data table list.md](references/metadata data table list.md) metadata data table get metadata.data table.get [metadata data table get.md](references/metadata data table get.md) metadata data table csv write metadata.data table.csv write [metadata data table csv write.md](references/metadata data table csv write.md) metadata data table sql write metadata.data table.sql write [metadata data table sql write.md](references/metadata data table sql write.md) metadata data table csv delete metadata.data table.csv delete [metadata data table csv delete.md](references/metadata data table csv delete.md) metadata data table sql delete metadata.data table.sql delete [metadata data table sql delete.md](references/metadata data table sql delete.md) metadata data table download metadata.data table.download [metadata data table download.md](references/metadata data table download.md) metadata data table property bindings update metadata.data table.property bindings update [metadata data table property bindings update.md](references/metadata data table property bindings update.md) metadata property bind existing dimension table metadata.property.bind existing dimension table [metadata property dimension table bind existing.md](references/metadata property dimension table bind existing.md) metadata property create and bind csv dimension table metadata.property.create and bind csv dimension table [metadata property dimension table create and bind csv.md](references/metadata property dimension table create and bind csv.md) Quick Verification