@thinkingai/ae-cli 6.0.31 → 6.1.4

package/skills/ae-analysis/references/drilldown_user_events_run.md

@@ -1,8 +1,8 @@
 # analysis drilldown-user-events run
 
-Query event sequence details for one user after `analysis drilldown-users run`.
+Query event sequence details for one user after a user-subject `analysis drilldown-entities run`.
 
-Use this only after `analysis drilldown-users run` returns a `drilldown_context_id`.
+Use this only when `analysis drilldown-entities run` returns `subject.type=user`, a `drilldown_context_id`, and the user-event follow-up action. Custom entities do not have event sequences.
 
 Do not pass raw QP.
 
@@ -19,15 +19,15 @@ ae-cli analysis drilldown-user-events run \
 
 ## Input
 
-- `--drilldown-context-id`: returned by `analysis drilldown-users run`.
-- `--user-id`: user id returned by `analysis drilldown-users run`.
-- `--properties`: optional backend property request object array. Omit this in normal agent calls and use the default returned columns. Do not pass string-name arrays such as `["event_time"]`.
+- `--drilldown-context-id`: returned by the same user-subject `analysis drilldown-entities run`.
+- `--user-id`: canonical `user_id` from one item in that same response. Never substitute `entity_value`, `#distinct_id`, account ID, or another identity field.
+- `--properties`: optional exact event-property projection. Omit it to use the default event columns. If present, each item uses backend keys `columnName` and `tableType`, for example `[{"columnName":"<event_property_name>","tableType":"event"}]`. `#user_id`, account ID, visitor ID, event name, and event time remain present; unrelated event properties must not be returned. `#user_id` is an internal association key, so Agents should normally display account ID and visitor ID to customers. Do not pass numeric table-type codes, string-name arrays, or snake_case nested keys.
 - `--sort-order`: `asc` or `desc`.
 - `--event-name-filter`, `--time-filter`, `--time-filter-before-nums`, `--time-filter-after-nums`: optional event sequence filters.
 
 Do not use raw QP, `query_context_id`, or guessed user IDs for this command.
 
-The `drilldown_context_id` must come from a `drilldown-users` target that includes date context, such as `drilldown_date` or `target_dates`. A context created from `include_total` alone can list users, but may fail event-sequence lookup with `TARGET_DATES_REQUIRED`.
+Do not call this command merely because an entity row looks like a user. The explicit subject and follow-up context are the authority.
 
 ## Output
 

package/skills/ae-analysis/references/entity_detail_export.md

@@ -26,6 +26,8 @@ Do not pass `--limit`; async export rejects inline limits. Use `--artifact-forma
 
 Export does not accept `--limit` or `--offset`; backend batching is internal.
 
+For `entity="user"`, every artifact row includes `#user_id`, `#account_id`, and `#distinct_id` plus requested user properties. For a custom entity, omit `properties`; the artifact contains only the entity value column and rejects additional properties. When presenting user artifacts, Agents should display account ID and visitor ID instead of exposing internal `#user_id` as the only visible identity.
+
 Output:
 
 Returns an async descriptor with opaque `run_id` / `artifact_id`, lifecycle status, expiration, and effective timeout/deadline fields. JSONL artifacts start with metadata and schema lines; CSV artifacts start directly with the header and contain only valid CSV records.

package/skills/ae-analysis/references/entity_detail_run.md

@@ -9,7 +9,7 @@ Use this command for the first small entity detail preview that fits inline. It
 ```bash
 ae-cli analysis entity-detail run \
   --project-id <project_id> \
-  --definition '{"entity":"user","cohort":{"relation":"and","items":[{"field":{"name":"level","type":"user_property"},"operator":"gte","values":[1]}]},"properties":["#user_id",{"name":"country","type":"user_property"}],"sort":[{"field":"#user_id","order":"asc"}]}' \
+  --definition '{"entity":"user","cohort":{"relation":"and","items":[{"field":{"name":"level","type":"user_property"},"operator":"gte","values":[1]}]},"properties":[{"name":"country","type":"user_property"}],"sort":[{"field":"#user_id","order":"asc"}]}' \
   --limit 100
 ```
 
@@ -24,6 +24,13 @@ Input:
 
 `entity` may be `"user"` for the default user entity or `{ "id": 123 }` in multi-entity projects.
 
+Property and identity rules depend on the entity:
+
+- `entity="user"` resolves to the `#user_id` user entity. `properties` may contain user properties. Every row always contains `#user_id`, `#account_id`, and `#distinct_id` plus the requested properties.
+- A custom entity (`{"id":123}` whose entity column is not `#user_id`) returns only its entity value column. Do not provide `properties`; doing so returns `CUSTOM_ENTITY_PROPERTIES_UNSUPPORTED`.
+
+`#user_id` is an internal association key and is normally not meaningful to customers. In user-facing output, Agents should show account ID and visitor ID by default; retain `#user_id` for machine linkage or explicit troubleshooting.
+
 `cohort` is AI-facing for simple entity-set filters and uses the same filter item shape as report/detail filters:
 
 ```json

package/skills/ae-analysis/references/event_detail_export.md

@@ -26,6 +26,8 @@ Do not pass `--limit`; async export rejects inline limits. Use `--artifact-forma
 
 Export does not accept `--limit` or `--offset`; backend batching is internal.
 
+`definition.properties` uses the same exact projection as `event-detail run`. The artifact may include required system event columns, but it must not expand to every visible event property.
+
 Output:
 
 Returns an async descriptor with opaque `run_id` / `artifact_id`, lifecycle status, expiration, and effective timeout/deadline fields. JSONL artifacts start with metadata and schema lines; CSV artifacts start directly with the header and contain only valid CSV records.

package/skills/ae-analysis/references/event_detail_run.md

@@ -51,6 +51,8 @@ Use `{"mode":"relative","relative_date_range":"0-7"}` for recent-day queries.
 
 Do not pass raw QP, `eventView`, `taFilters`, `columnName`, or `tableType`.
 
+When `definition.properties` is present, it is an exact projection: required system event columns remain, requested properties are appended, and unrelated properties must not be returned.
+
 Do not use this command for full, unknown-size, or later-page detail retrieval. Use `analysis event-detail export` and check its artifact metadata for `truncated`.
 
 Output:

package/skills/ae-analysis/references/event_list.md

@@ -1,6 +1,6 @@
 # analysis-meta event list
 
-Use when the user needs to list project super events.
+Use when the user needs to list project super events, search event metadata, page results, project fields, or filter to authenticated events.
 
 Do not use it for raw tracked events, event counts, or one full definition; it lists project super-event metadata.
 
@@ -8,12 +8,15 @@ Command:
 
 ```bash
 ae-cli analysis-meta event list --project-id <project_id>
+ae-cli analysis-meta event list --project-id <project_id> --query login --fields '["event_name","event_desc","authentication_status"]' --limit 20 --offset 0 --authenticated-only
 ae-cli analysis-meta event list --dry-run
 ```
 
 Capability id: `metadata.event.list`.
 
-Input sends `project_id`.
+Input sends `project_id`, `query`, `fields`, `limit`, `offset`, and `authenticated_only`.
+
+Use snake_case projection fields: `event_id`, `event_name`, `event_desc`, `remark`, `event_tag`, `authentication_status`. Do not send legacy camelCase field names.
 
 Output `data.events[]` contains project super-event metadata records.
 
@@ -21,3 +24,8 @@ Output `data.events[]` contains project super-event metadata records.
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
+| `--query` / `-q` | No | Optional keyword filter. Fuzzy match is applied to `event_name`, `event_desc`, and `remark`. |
+| `--fields` / `-f` | No | Optional JSON array of snake_case fields to return. |
+| `--limit` / `-l` | No | Optional page size. When omitted, existing full-list behavior is preserved. Maximum: 50. |
+| `--offset` / `-o` | No | Optional zero-based page offset. |
+| `--authenticated-only` | No | When true, return only authenticated events and include `authentication_status` when projected. |

package/skills/ae-analysis/references/list_entities.md

@@ -39,4 +39,4 @@ ae-cli analysis_meta +list_entities --dry-run
 - If the result is empty, first confirm the project ID/keyword, then try loosening the filter conditions.
 
 ## Recommended Chaining
-- +list_entities -> +create_virtual_property / +create_virtual_event
+- +list_entities -> analysis-meta virtual-property create / analysis-meta virtual-event create

package/skills/ae-analysis/references/metric_create.md

@@ -2,13 +2,14 @@
 
 Use when the user needs to create a metric from event or retention analysis configuration.
 
-Do not use it to query metric values. Use this gateway command for an exact metric definition; use `analysis_meta +create_metric` only when the gateway capability is unavailable.
+Do not use it to query metric values. Use this gateway command for an exact metric definition.
 
 Command:
 
 ```bash
-ae-cli analysis-meta metric create --project-id <project_id> --metric-name pay_amount --metric-desc 'Pay Amount' --metric-mode <mode> --metric-events '[...]' --metric-params '{}'
-ae-cli analysis-meta metric create --project-id <project_id> --metric-name pay_amount --metric-desc 'Pay Amount' --metric-mode <mode> --metric-events '[...]' --dry-run
+ae-cli analysis-meta metric create --project-id <project_id> --metric-name pay_amount --metric-desc 'Pay Amount' --model-type event --metric-events '[...]' --metric-params '{}'
+ae-cli analysis-meta metric create --project-id <project_id> --metric-name retained_users --metric-desc 'Retained Users' --model-type retention --metric-events '[...]' --metric-params '{}'
+ae-cli analysis-meta metric create --project-id <project_id> --metric-name pay_amount --metric-desc 'Pay Amount' --metric-mode 0 --metric-events '[...]' --dry-run
 ```
 
 Capability id: `metadata.metric.create`.
@@ -23,7 +24,15 @@ Output `data.metric` contains the created metric summary.
 | `--project-id` | Yes | Numeric project ID. |
 | `--metric-name` | Yes | Metric technical name. |
 | `--metric-desc` | Yes | Metric display name. |
-| `--metric-mode` | Yes | Metric model mode, for example `0` for event analysis. |
+| `--model-type` | No | Semantic metric model type: `event` or `retention`. Prefer this over `--metric-mode`. |
+| `--metric-mode` | No | Metric model mode, for example `0` for event analysis. Required only when `--model-type` is omitted. |
 | `--metric-events` | Yes | Metric event-analysis QP JSON array. |
 | `--metric-remark` | No | Metric remark. |
 | `--metric-params` | No | Metric params JSON object; common defaults it to `{}` when needed. |
+
+## Decision Rules
+
+- Pass exactly one semantic model selector when possible: prefer `--model-type event` or `--model-type retention`.
+- `--metric-mode` remains available for existing scripts; if both are provided, they must describe the same model.
+- For event metrics, `--metric-params` is usually a format config such as `{"format":"integer"}`.
+- For retention metrics, `--metric-params` should be the retention `eventView` configuration.

package/skills/ae-analysis/references/metric_delete.md

@@ -23,3 +23,10 @@ Output is a successful gateway envelope with no business data. Verify with `metr
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
 | `--metric-id` | Yes | Metric ID. |
+
+## Decision Rules
+- Use `analysis-meta metric list` first to confirm the metric ID before deleting.
+- This is a destructive operation; keep the confirmation prompt unless automation is explicitly required.
+
+## Recommended Chain
+- `analysis-meta metric list` -> `analysis-meta metric delete`

package/skills/ae-analysis/references/metric_get.md

@@ -3,6 +3,7 @@
 Use when the user needs to get metric definition, events, and params.
 
 Do not use it to query metric values or trends; it returns the saved metric definition only.
+Do not call it just to expand a saved metric before normal ad-hoc analysis. If the user asks to query a saved metric, pass the metric display/name/remark directly in `analysis adhoc run --definition`; the backend compiler resolves saved metrics internally.
 
 Command:
 
@@ -22,3 +23,8 @@ Output `data.metric` contains the saved metric definition, or no metric when the
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
 | `--metric-id` | Yes | Metric ID. |
+
+## Recommended Chaining
+
+- analysis-meta metric get -> analysis-meta metric update
+- For ad-hoc saved metric query: analysis adhoc run/export

package/skills/ae-analysis/references/metric_list.md

@@ -1,24 +1,37 @@
 # analysis-meta metric list
 
-Use when the user needs to list project metrics.
+Use when the user needs to list, search, page, or field-project project metrics.
 
 Do not use it to calculate metric values; use report/dashboard/ad-hoc data routing for result queries.
 
 Command:
 
 ```bash
+ae-cli analysis-meta metric list --project-id <project_id>
 ae-cli analysis-meta metric list --project-id <project_id> --ignore-authentication true
+ae-cli analysis-meta metric list --project-id <project_id> --query pay
+ae-cli analysis-meta metric list --project-id <project_id> --query pay --fields '["metric_name","authentication_status"]' --limit 10 --offset 0 --authenticated-only true
 ae-cli analysis-meta metric list --dry-run
 ```
 
 Capability id: `metadata.metric.list`.
 
-Input sends `project_id`, `ignore_authentication`.
+Input sends `project_id`, `ignore_authentication`, `query`, `fields`, `limit`, `offset`, and `authenticated_only`.
 
-Output `data.metrics[]` contains project metric summaries and authentication decoration unless explicitly skipped.
+Output `data.metrics[]` contains project metric summaries. When `limit` or `offset` is present, output also includes `total`, `limit`, `offset`, and `has_more`.
 
 ## Parameters
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
 | `--ignore-authentication` | No | Whether to skip asset authentication status decoration. |
+| `--query` | No | Optional keyword filter. Fuzzy match on `metric_name`, `metric_desc`, and `metric_remark`. |
+| `--fields` | No | Optional result field projection JSON array. Supported fields: `metric_id`, `metric_name`, `metric_desc`, `metric_remark`, `metric_mode`, `authentication_status`, `open_id`, `creator`, `creator_login_name`, `update_open_id`, `update_creator`, `update_login_name`, `create_time`, `update_time`. |
+| `--limit` | No | Optional page size. Default: 20 when pagination is used, maximum: 50. |
+| `--offset` | No | Optional zero-based result offset. Default: 0. |
+| `--authenticated-only` | No | When true, return only authenticated metrics. |
+
+## Decision Rules
+- Do not call this just to prepare normal ad-hoc analysis. Pass saved metric wording directly in `analysis adhoc run/export --definition`; the backend compiler resolves saved metric names internally.
+- Use `--fields` to keep discovery responses compact.
+- Use `analysis-meta metric get` after this command when a full metric definition is needed.

package/skills/ae-analysis/references/metric_update.md

@@ -2,12 +2,16 @@
 
 Use when the user needs to update metric definition, name, and remark.
 
-Do not use it to query metric values. Use `analysis_meta +update_metric` only when the gateway capability is unavailable.
+Do not use it to query metric values.
+
+Before updating `--metric-events` / `--metric-params`, validate the event and property names with `analysis-meta event list` and `analysis-meta property list` in the same `project_id`.
 
 Command:
 
 ```bash
 ae-cli analysis-meta metric update --project-id <project_id> --metric-id <metric_id> --metric-desc 'New display name' --metric-remark 'New remark'
+ae-cli analysis-meta metric update --project-id <project_id> --metric-id <metric_id> --metric-name demo --metric-desc demo --model-type event --metric-events '[]'
+ae-cli analysis-meta metric update --project-id <project_id> --metric-id <metric_id> --metric-name demo --metric-desc demo --metric-remark demo --model-type retention --metric-events '[]' --metric-params '{}'
 ae-cli analysis-meta metric update --project-id <project_id> --metric-id <metric_id> --metric-desc 'New display name' --dry-run
 ```
 
@@ -26,5 +30,12 @@ Output `data.metric` contains the updated summary for a full-definition update c
 | `--metric-desc` | No | Metric display name. |
 | `--metric-remark` | No | Metric remark. |
 | `--metric-mode` | No | Metric model mode for a full-definition update. |
+| `--model-type` | No | Semantic metric model type: `event` or `retention`. Prefer this over `--metric-mode`. |
 | `--metric-events` | No | Metric event-analysis QP JSON array for a full-definition update. |
 | `--metric-params` | No | Metric params JSON object. |
+
+## Decision Rules
+- For full-definition updates, pass `--metric-name`, `--metric-desc`, one of `--model-type` / `--metric-mode`, and `--metric-events` together.
+- If both `--model-type` and `--metric-mode` are present, they must match: `event -> 0`, `retention -> 1`.
+- Use `analysis-meta metric get` before updating if the current definition needs to be preserved and edited.
+- This is an ordinary write operation; execute it without the high-risk confirmation flag.

package/skills/ae-analysis/references/project_access_detail_get.md

@@ -0,0 +1,23 @@
+# analysis project access-detail get
+
+Use when the user needs to get company project access details.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project access-detail get --company-id <company_id>
+ae-cli analysis project access-detail get --dry-run --company-id <company_id>
+```
+
+Capability id: `project.access_detail.get`.
+
+Input sends `company_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--company-id` | Yes | Company ID. |

package/skills/ae-analysis/references/project_data_power_delete.md

@@ -0,0 +1,26 @@
+# analysis project data-power delete
+
+Use when the user needs to delete a data power and optionally migrate users to another data power.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project data-power delete --project-id <project_id> --data-power-id <data_power_id> --new-data-power-id <new_data_power_id>
+ae-cli analysis project data-power delete --dry-run --project-id <project_id> --data-power-id <data_power_id>
+```
+
+Capability id: `project.data_power.delete`.
+
+Input sends `project_id`, `data_power_id`, `new_data_power_id`, `yes`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+For execution, dry-run first, summarize the impact, then rerun the unchanged command with global `--yes` only after explicit user confirmation. The CLI sends `yes=true` after its own high-risk gate.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--data-power-id` | Yes | Data power ID to delete. |
+| `--new-data-power-id` | No | Optional replacement data power ID for affected users. |

package/skills/ae-analysis/references/project_data_power_get.md

@@ -0,0 +1,24 @@
+# analysis project data-power get
+
+Use when the user needs to get one data power detail.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project data-power get --project-id <project_id> --data-power-id <data_power_id>
+ae-cli analysis project data-power get --dry-run --project-id <project_id> --data-power-id <data_power_id>
+```
+
+Capability id: `project.data_power.get`.
+
+Input sends `project_id`, `data_power_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--data-power-id` | Yes | Data power ID. |

package/skills/ae-analysis/references/project_data_power_list.md

@@ -0,0 +1,23 @@
+# analysis project data-power list
+
+Use when the user needs to list project data powers.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project data-power list --project-id <project_id>
+ae-cli analysis project data-power list --dry-run --project-id <project_id>
+```
+
+Capability id: `project.data_power.list`.
+
+Input sends `project_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |

package/skills/ae-analysis/references/project_data_power_upsert.md

@@ -0,0 +1,24 @@
+# analysis project data-power upsert
+
+Use when the user needs to create or update a data power.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project data-power upsert --project-id <project_id> --payload <payload>
+ae-cli analysis project data-power upsert --dry-run --project-id <project_id> --payload <payload>
+```
+
+Capability id: `project.data_power.upsert`.
+
+Input sends `project_id`, `payload`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--payload` | Yes | Data power save payload matching DataPowerSaveRequestDTO in snake_case. |

package/skills/ae-analysis/references/project_entity_create.md

@@ -0,0 +1,27 @@
+# analysis project entity create
+
+Use when the user needs to create an analysis entity.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project entity create --project-id <project_id> --entity-name <entity_name> --column-name <column_name> --table-type <table_type> --order <order>
+ae-cli analysis project entity create --dry-run --project-id <project_id> --entity-name <entity_name> --column-name <column_name> --table-type <table_type>
+```
+
+Capability id: `project.entity.create`.
+
+Input sends `project_id`, `entity_name`, `column_name`, `table_type`, `order`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--entity-name` | Yes | Entity display name. |
+| `--column-name` | Yes | Property column name to bind. |
+| `--table-type` | Yes | Main table type: 0 for event property, 1 for user property. |
+| `--order` | No | Optional entity display order. |

package/skills/ae-analysis/references/project_entity_delete.md

@@ -0,0 +1,25 @@
+# analysis project entity delete
+
+Use when the user needs to delete an analysis entity.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project entity delete --project-id <project_id> --entity-id <entity_id>
+ae-cli analysis project entity delete --dry-run --project-id <project_id> --entity-id <entity_id>
+```
+
+Capability id: `project.entity.delete`.
+
+Input sends `project_id`, `entity_id`, `yes`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+For execution, dry-run first, summarize the impact, then rerun the unchanged command with global `--yes` only after explicit user confirmation. The CLI sends `yes=true` after its own high-risk gate.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--entity-id` | Yes | Analysis entity ID. |

package/skills/ae-analysis/references/project_entity_event_list.md

@@ -0,0 +1,24 @@
+# analysis project entity-event list
+
+Use when the user needs to list entity mappings for events.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project entity-event list --project-id <project_id> --event-names <event_names>
+ae-cli analysis project entity-event list --dry-run --project-id <project_id>
+```
+
+Capability id: `project.entity_event.list`.
+
+Input sends `project_id`, `event_names`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--event-names` | No | Optional event names JSON array to resolve entity mappings for. |

package/skills/ae-analysis/references/project_entity_get.md

@@ -0,0 +1,24 @@
+# analysis project entity get
+
+Use when the user needs to get one analysis entity.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project entity get --project-id <project_id> --entity-id <entity_id>
+ae-cli analysis project entity get --dry-run --project-id <project_id> --entity-id <entity_id>
+```
+
+Capability id: `project.entity.get`.
+
+Input sends `project_id`, `entity_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--entity-id` | Yes | Analysis entity ID. |

package/skills/ae-analysis/references/project_entity_list.md

@@ -0,0 +1,28 @@
+# analysis project entity list
+
+Use when the user needs to list analysis entities in a project.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project entity list --project-id <project_id> --query <query> --fields <fields> --limit <limit> --offset <offset> --event-name <event_name>
+ae-cli analysis project entity list --dry-run --project-id <project_id>
+```
+
+Capability id: `project.entity.list`.
+
+Input sends `project_id`, `query`, `fields`, `limit`, `offset`, `event_name`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--query` | No | Optional keyword filter. |
+| `--fields` | No | Optional snake_case fields to return. |
+| `--limit` | No | Optional page size. Default: 50, maximum: 200. |
+| `--offset` | No | Optional page offset. Default: 0. |
+| `--event-name` | No | Optional event name. When present, return entities related to the event. |

package/skills/ae-analysis/references/project_entity_update.md

@@ -0,0 +1,28 @@
+# analysis project entity update
+
+Use when the user needs to update an analysis entity.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project entity update --project-id <project_id> --entity-id <entity_id> --entity-name <entity_name> --column-name <column_name> --table-type <table_type> --order <order>
+ae-cli analysis project entity update --dry-run --project-id <project_id> --entity-id <entity_id> --entity-name <entity_name> --column-name <column_name> --table-type <table_type>
+```
+
+Capability id: `project.entity.update`.
+
+Input sends `project_id`, `entity_id`, `entity_name`, `column_name`, `table_type`, `order`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |
+| `--entity-id` | Yes | Analysis entity ID. |
+| `--entity-name` | Yes | Entity display name. |
+| `--column-name` | Yes | Property column name to bind. |
+| `--table-type` | Yes | Main table type: 0 for event property, 1 for user property. |
+| `--order` | No | Optional entity display order. |

package/skills/ae-analysis/references/project_function_list.md

@@ -0,0 +1,24 @@
+# analysis project function list
+
+Use when the user needs to list all project-level functions.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project function list --company-id <company_id> --project-id <project_id>
+ae-cli analysis project function list --dry-run 
+```
+
+Capability id: `project.function.list`.
+
+Input sends `company_id`, `project_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--company-id` | No | Company ID. |
+| `--project-id` | No | Project ID. |

package/skills/ae-analysis/references/project_info_get.md

@@ -0,0 +1,23 @@
+# analysis project info get
+
+Use when the user needs to get project configuration details.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project info get --project-id <project_id>
+ae-cli analysis project info get --dry-run --project-id <project_id>
+```
+
+Capability id: `project.info.get`.
+
+Input sends `project_id`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project-id` | Yes | Numeric project ID. |

package/skills/ae-analysis/references/project_info_list.md

@@ -0,0 +1,26 @@
+# analysis project info list
+
+Use when the user needs to list projects accessible to the current user.
+
+Do not use it for unrelated project-management actions or for fields not present in the common-service capability schema. Do not send camelCase aliases.
+
+Command:
+
+```bash
+ae-cli analysis project info list --query <query> --fields <fields> --limit <limit> --offset <offset>
+ae-cli analysis project info list --dry-run 
+```
+
+Capability id: `project.info.list`.
+
+Input sends `query`, `fields`, `limit`, `offset`. Payload keys, JSON arrays, and projection fields must follow the common-service snake_case input schema.
+
+Output uses the gateway envelope: success is `ok=true,data,meta`; failure is `ok=false,error`. Preserve `request_id` and `invocation_id` when present.
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--query` | No | Optional keyword filter. |
+| `--fields` | No | Optional snake_case fields to return. |
+| `--limit` | No | Optional page size. Default: 50, maximum: 200. |
+| `--offset` | No | Optional page offset. Default: 0. |