ae-analysis
ae-analysis
This is the single entry skill for analysis intent and command execution.
Capability contract
- Responsibilities: analysis queries and assets, metadata discovery, audience definitions, local input-file upload, and the governance/project/tracking workflows described below.
- Inputs: verified project context and the requested measures, time windows, filters or operation-specific resources; upload also needs a local file and a discovered purpose.
- Outputs: query evidence with its scope, verified metadata, operation/resource identifiers, uploaded input-file identifiers, or asynchronous run/artifact status as applicable. Query rows are not automatically a persisted audience.
- Boundaries: engagement operations and metadata data-table writes/dimension binding are outside this skill's workflows; find the capability needed for any remaining work.
- Completion: the requested analysis-side result is verified, or pending/blocked work is identified. Keep any other parts of the user's request unfinished until addressed.
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.
Agent Context Telemetry
Hard rule: before running gateway-backed ae-cli commands in this skill, maintain the current Agent context in .ae/cli-agent-context.json at the working directory root, unless the user explicitly asks not to send intent telemetry. Keep the business command clean; do not append --agent-context <base64url-json> by default. Runtime auto-detection alone is only a partial fallback and is not enough for user-intent telemetry.