thinkingaiagenticengine/ae-cli

ae-metadata

AE metadata capability-gateway CLI: list, inspect, create, update, delete and download metadata data tables; bind an existing dimension table to a property or create and bind a CSV dimension table.

Vedi sorgente

Come usare

  1. Copia il comando e controlla il pacchetto prima di installarlo nel tuo ambiente agente.
  2. Controlla strumenti, credenziali e ambienti richiesti nel documento originale.
  3. Descrivi input e risultato desiderato; confronta l’output con le fonti.
npx skills add https://github.com/thinkingaiagenticengine/ae-cli --skill ae-metadata

Prima di iniziare

  • L’installazione non include abbonamenti, quote API o accesso ai file.
  • Stelle e installazioni indicano attività, non un test indipendente di qualità o sicurezza.
Documento Skill originale

Contenuto dal repository con titoli, esempi, codice, tabelle, link e immagini preservati.

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. 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

ParameterDescription
`--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> ....
--validateOptional: fix params only (/validate). Alone while iterating complex qp / payload — then run. Do not stack with --dry-run.
--dry-runOptional: confirm ready to run (/dry-run). Alone for risk/output preview. Do not stack with --validate.

Output and errors:

  • Built-in --jq receives the business payload before the outer {ok,data,meta} envelope. Use payload fields directly inside the CLI; use .data... only with external jq over saved final JSON.
  • 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

bash
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)

User commandCapability idReference
metadata data-table listmetadata.data_table.listmetadata_data_table_list.md
metadata data-table getmetadata.data_table.getmetadata_data_table_get.md
metadata data-table csv-writemetadata.data_table.csv_writemetadata_data_table_csv_write.md
metadata data-table sql-writemetadata.data_table.sql_writemetadata_data_table_sql_write.md
metadata data-table csv-deletemetadata.data_table.csv_deletemetadata_data_table_csv_delete.md
metadata data-table sql-deletemetadata.data_table.sql_deletemetadata_data_table_sql_delete.md
metadata data-table downloadmetadata.data_table.downloadmetadata_data_table_download.md
metadata data-table property-bindings-updatemetadata.data_table.property_bindings_updatemetadata_data_table_property_bindings_update.md
metadata property bind-existing-dimension-tablemetadata.property.bind_existing_dimension_tablemetadata_property_dimension_table_bind_existing.md
metadata property create-and-bind-csv-dimension-tablemetadata.property.create_and_bind_csv_dimension_tablemetadata_property_dimension_table_create_and_bind_csv.md

Quick Verification

bash
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
dallo stesso repository

Altri Skills

Tutti gli Skills
thinkingaiagenticengine
Community

ae-agent

AE Agent platform CLI for Agent, resource package import and export, notification, approval, archived conversation, model, MCP, Skill, attachment, and user-memory work. Use when managing these resources, browsing Agent markets, handling approval requests and tasks, restoring archived conversations, persisting user memory, or answering from user preferences, background, stable workflows, or historical conventions.

Installazioni / 1h
2
GitHub Stars
23
Aggiornato
6 nov
thinkingaiagenticengine
Community

ae-analysis

Use ae-cli for AE analysis-side data questions, asset operations, and asset governance: reports, analysis boards, BI dashboards, ad-hoc models, drilldown, detail data, alerts, clusters, tags, metrics, metadata discovery, project configuration, tracking plans, local input-file upload, governance asset lists/rules/lineage/impact/dependency, batch asset operations, projects, and resource links. Use when the user asks to review collected analysis questions or badcases, query data, explain a change,

Installazioni / 1h
2
GitHub Stars
23
Aggiornato
6 nov
thinkingaiagenticengine
Community

ae-analysis-global

Use when AE analysis requests mention query/current/service/deployment clusters, current cluster (当前集群), cluster info (集群信息/有哪些集群), global or multi-cluster data, all clusters/all servers, GLOBAL/SLAVE, query-cluster, clusterqueryscope, slaveclusterid, country/region/server/shard/site/market routing, or when cluster may mean query cluster rather than audience/user segment.

Installazioni / 1h
2
GitHub Stars
23
Aggiornato
6 nov
thinkingaiagenticengine
Community

ae-automation

Schedule AE platform automations: every day/week, daily reports, recurring reminders, monitoring, or repeat this task. Use ae-cli automation for persistent Agent/Agent Team tasks in the current space, instead of session-local CronCreate or /loop. Also manage schedules, runs, and results.

Installazioni / 1h
2
GitHub Stars
23
Aggiornato
6 nov