Use ae-cli for AE/TE 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, project configuration, tracking plans, governance asset lists/rules/lineage/impact/dep

ae analysis This is the single entry skill for analysis intent and command execution. Route before reading 1. Map the request to a command family before opening any reference. Known family: open only its dedicated reference. For example, a retention request goes directly to references/adhoc run.md plus the retention section of references/ai models.md . Unknown family: search [ references/command index.md ](references/command index.md) with rg or an equivalent text search tool and keep only the matching rows. command index.md is a search only fallback; never open it with a whole file read or print the entire file. 2. Read the selected command's dedicated reference before composing it: event list references/event list.md analysis dashboard list references/dashboard list.md personal semantic preference list references/personal semantic preference list.md Asset center cross source configuration (资产中心 / 跨源资产配置 / Excel 配置表导入): L3 discovery via capability search "cross source config" domain metadata project id <id ; read [ references/cross source config.md ](references/cross source config.md) for workbook upload and validation. No dedicated business commands. replace hyphens with underscores in gateway filenames. 3. For an AI facing ad hoc definition, also read [ references/ai models.md ](references/ai models.md). 4. For cluster/tag definition request , also read the matching [ references/user cluster models.md ](references/user cluster models.md) or [ references/user tag models.md ](references/user tag models.md). Shared primitives live in [ references/audience models.md ](references/audience models.md). For tag periodic refresh, read references/user tag create.md or references/user tag update.md ; they cover the enable switch, frequency/time schedule, cron alternative, and timezone behavior. 5. For analysis data retrieval, choose run or export using [ references/analysis data retrieval.md ](references/analysis data retrieval.md). 6. When an AI QP compile failure contains slot kind , allowed resource types , search targets , and next action , read and follow [ metadata resolution.md ](metadata resolution.md). Routing is complete when one command family and its dedicated references are selected. The generated command index is exhaustive and must stay out of model context except for matching search rows. This file contains routing and workflow rules only; do not duplicate a hand maintained command inventory here. Boundaries and priority Use this skill for these CLI services: analysis : reports, dashboards, BI panels, ad hoc analysis, drilldown, detail data, alerts, clusters, tags, and async runs/artifacts. analysis meta : gateway metadata assets, events, properties, virtual metadata, metrics, data tables, exchange rules, and super metadata. Cross source asset configuration uses the metadata L3 catalog instead. analysis governance : gateway asset governance operations, including governed asset lists/exports, lineage, dependency, impact, query history, rule schema/list/create/update/delete, batch asset actions, and operation records. Use this service for asset governance workflows, not for metadata event/property/metric CRUD. tracking : gateway tracking plan, checking, ingest, live data, and event blacklist operations. personal semantic preference : current user's project scoped personal semantic preferences. Use it as agent context before resolving ambiguous business wording, asset choices, or recurring user preferences. For metadata gateway detail outside the commands in the generated index, use the metadata skill. For Engage, DataOps, or Community work, use the corresponding skill. Use ae cli as the only execution path for this skill. If a command is missing, unsupported, not implemented, or a capability gap is confirmed, report the gap and stop or provide framework level guidance; do not switch to direct MCP execution. Repeated failures are not evidence of a capability gap until parameters, types, time formats, permissions, timeout choice, and payload construction have been checked. A validation error or need clarification is a reason to correct the input, not to switch tools. For tags and audience clusters, use the native analysis user tag ... and analysis user cluster ... gateway commands. Global AE CLI Rules Command forms: Gateway commands use kebab case flags such as project id ; the CLI sends snake case JSON. JSON values must be JSON string literals. Global flags include host , format json table , jq , validate , dry run , and yes . Use validate alone to normalize complex capability input; use dry run alone for execution or risk preview. JSON is the default machine readable output. On failure, preserve the structured error and non zero exit. CRITICAL — Host compat (do this first): After each ae cli run, check stderr and notice.host compat . If either is present, your reply MUST open with a short ⚠️ version warning and quote the npm i g / npx skills add (or update cluster) lines verbatim , then present the business result. Never answer with only a project/table summary when a host compat notice exists. Soft tip; ok: true can still carry the notice. Never invent command names, flags, payload fields, projects, resource IDs, asset names, event/property names, metric definitions, or dates. 中文时间表达必须按固定语义映射：最近7天/近7天 mode=recent QP recentDay=0 7 ，含今天；过去7天/前7天 mode=previous QP recentDay=1 7 ，不含今天。用户明确说明是否包含今天时，以该说明为准。完整映射见 [ references/ai models.md ](references/ai models.md)。 CAPABILITY NOT FOUND means the current host does not expose that gateway capability; changing parameters will not fix it. A permission error stops any dependent chain. A 404 while inspecting an async run is a route/deployment failure; do not poll the same ID forever. Interpret gateway envelopes by state: ok: true with empty data is success and means no matching data. Never relabel an empty report/dashboard result as query failure. ok: true with meta.partial: true is partial success. Use the successful data and explicitly report meta.failures ; do not fail the whole batch or hide failed items. ok: false is failure. Preserve error.code , error.message , and meta.request id , meta.invocation id , meta.stage , and meta.failures when present. Do not retry an unchanged failed command or guess alternative payload shapes. Retry only after applying concrete validation/clarification guidance or correcting a verified transient condition. Failure evidence: A process exit code of 0 is not business success when the envelope says ok: false . Prefer direct CLI invocation; if a shell pipeline is necessary, preserve the CLI exit status with set o pipefail and retain the complete error envelope rather than truncating it. TE TOOL POLICY DENIED identifies the runtime authorization stage. Report its exact reason; it does not prove a backend schema check passed or that the user needs to log in again. Do not bypass policy or retry by changing the business scope. INVALID ANALYSIS DEFINITION / INVALID CAPABILITY INPUT identifies an input failure. Correct all relevant fields together within the allowed retry budget. Say "validation passed" only after an explicit successful validation response for the same complete definition on the same host. QUERY FAILED establishes that the query failed; it does not establish the database or engine root cause. Preserve the returned error and correlation IDs, leave unavailable values unknown (not zero), and stop when the user requests no retries. Distinguish observed errors from unverified hypotheses. For every gateway command that exposes request id , ae cli generates a request id and prints it to stderr before dispatch when the caller omits it. Preserve that ID with the final envelope and diagnostics. Pass an explicit request id cli <32 lowercase hex only when a caller owned correlation ID is required. Execution invariants Probe the first page exactly once. Verify ok , the documented data shape, and the effective limit before starting a pagination loop. For paginated directory results, continue only with the returned next offset while has more is true. Never calculate a speculative offset, repeat the current page, or declare the list complete before has more is false. Track the normalized command, input, and announced request id for every invocation. Never resubmit an identical invocation while it is still in flight; wait for the current process, or inspect its returned run id when it is asynchronous. Retry only the items named in meta.failures , and only when their retryable value and next action permit it. Never retry successful or empty items from the same batch. For black box coverage audits, maintain an explicit module × model × outcome matrix. Mark coverage complete only from observed responses; missing assets, permissions, or fixtures are environment gaps, not passing coverage. Mandatory routing Product terminology gate The Chinese product term 看板 means an analysis board backed by saved reports. Route it to ae cli analysis dashboard ... and capability IDs under analysis.dashboard. . The Chinese product terms 仪表盘 and BI 仪表盘 mean a BI dashboard with worksheets, charts, and pages. Route them to ae cli analysis bi panel ... and capability IDs under analysis.bi panel. . These assets are not aliases. Never substitute an analysis board for a BI dashboard, or a BI dashboard for an analysis board. The standalone English word dashboard is ambiguous in this product. Before a write, ask whether the user means an analysis board ( 看板 ) or a BI dashboard ( 仪表盘 ) unless the surrounding context already makes the product asset explicit. If the requested BI panel capability is unavailable or unauthorized, report that constraint. Do not fall back to creating an analysis board. Project gate Before a project scoped command: 1. Reuse a project only when its ID and host/environment were already verified in the same continuous conversation. 2. Otherwise call project info list and resolve the supplied ID/name. 3. If there are multiple plausible projects, the host is unclear, or no project matches, show the candidates and ask; never guess. 4. Re verify after the user changes project, host, or environment. Project Semantics Before answering project scoped analysis or asset governance requests, call ae cli project semantic list project id <project id once after the project is resolved. This is the governed project semantic catalog. The list is already filtered to active, fresh project semantics and sorted by heat, so do not page or search the database yourself. If one project semantic is actually adopted to interpret the user's wording, asset selection, metric definition, calculation convention, or project wide business rule, fetch it with ae cli project semantic get project id <project id id <semantic id mark used . Do not pass mark used for project semantics that were only inspected or rejected. For project semantic recommendation, switch to the ae project semantic skill. This skill only consumes published project semantics during analysis tasks. Published project semantics are the formal project wide authority. A current turn user instruction may request a different analysis, but the result must be labeled as an explicit non formal deviation rather than silently replacing the published definition. Personal Semantic Preferences Before answering project scoped analysis or asset governance requests, call ae cli personal semantic preference list project id <project id once per host, authenticated user, project, and conversation after the project is resolved. Keep that lightweight directory in conversation context; do not page it, search the database, or call list again for each question. T

ae-analysis