thinkingaiagenticengine/ae-cli

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, count…

查看源码

使用方法

  1. 复制安装命令,在自己的智能体环境安装前先检查源码包。
  2. 从原始文档核对所需工具、凭据和支持的宿主。
  3. 说明输入材料与期望交付物,并对照来源检查输出。
npx skills add https://github.com/thinkingaiagenticengine/ae-cli --skill ae-analysis-global

开始前需了解

  • 安装不包含模型订阅、API 额度或访问文件的权限。
  • 仓库星数和安装量反映活跃情况,不等于独立质量或安全测试。
仓库原始内容

按源仓库内容呈现,保留标题、案例、代码、表格、链接以及原文引用的演示图片。

ae-analysis-global

This is a terminology and routing overlay for ae-analysis. Read the base command reference `../ae-analysis/references/query_cluster_list.md` before composing the inventory command. Server output, not a local CLI feature switch, is authoritative for whether global query is enabled and which routes the account may use.

Every command accepts --host <url> to override the active AE host. Host selection is independent of --cluster-query-scope: --host chooses the AE instance, while --cluster-query-scope / --slave-cluster-id choose a physical query route inside that instance.

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. (Also covered by ae-analysis Global Rules when both skills are loaded.)

Routing Rules

  • In this overlay, 查询集群 / 数据集群 / 部署集群 means physical multi-cluster routing for analysis queries. 用户分群 / 人群包 means user-membership assets under analysis user-cluster.
  • If the user asks for query-cluster inventory or cluster info, call ae-cli analysis query-cluster list --project-id <project_id>. Localized examples include "查询集群信息" and "有哪些数据集群".
  • Do not answer query-cluster inventory questions with ae-cli analysis user-cluster list unless the user explicitly asks for audience clusters, cohorts, segments, user membership, or cluster definitions.
  • If the user mentions country, region, server, shard, site, market, or deployment area semantics, call analysis query-cluster list before choosing query scope.
  • Match slave intent only against returned slave_clusters[].cluster_id, cluster_name, and cluster_desc.
  • Report-data, dashboard-report-data, and ad-hoc run/export expose --cluster-query-scope GLOBAL|SLAVE; SLAVE requires --slave-cluster-id.
  • Use GLOBAL only when the user clearly asks for all clusters/servers or cross-cluster aggregation and permissions.can_query_global=true.
  • If the user does not express global or slave-cluster intent, omit the flag. Report/ad-hoc then use current self; dashboard follows its saved configuration.
  • If a requested route is not allowed, explain permissions.allowed_cluster_query_params instead of silently falling back.
  • SQL and attribution ad-hoc analysis do not support GLOBAL; SQL report/dashboard data also reject effective GLOBAL. Use an allowed SLAVE or current-self route.

Response Wording

  • For analysis query-cluster list, call the result "查询集群" or "query clusters" and summarize current_cluster, slave_clusters, and permissions.allowed_cluster_query_params.
  • For analysis user-cluster list, call the result "audience clusters" or "user segments"; do not call those results query clusters.

Query-cluster command

  • ae-cli analysis query-cluster list --project-id <project_id>

按任务相关推荐

来自同一仓库

更多 Skills

全部 Skills
thinkingaiagenticengine
社区

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.

1小时安装量
2
GitHub Stars
23
最近更新
11月6日
thinkingaiagenticengine
社区

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,

1小时安装量
2
GitHub Stars
23
最近更新
11月6日
thinkingaiagenticengine
社区

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.

1小时安装量
2
GitHub Stars
23
最近更新
11月6日
thinkingaiagenticengine
社区

ae-capability

AE capability gateway discovery and generic invocation with ae-cli. Use when the user needs to list or search available capabilities, inspect an unknown capability schema/risk/auth contract, optionally validate complex input or dry-run before execute, or invoke a long-tail capability that has no curated ae-cli command. Always discover and inspect before composing input; never guess capability IDs or input fields. Prefer on-demand validate OR dry-run — do not stack both by default.

1小时安装量
2
GitHub Stars
23
最近更新
11月6日