@thinkingai/ae-cli 6.0.20 → 6.0.24

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

@@ -34,6 +34,7 @@ ae-cli analysis_audience +build_tag_definition --dry-run
 | Parameter             | Required | Description                                                                                                                                                                       |
 | --------------------- | -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | `--project_id` / `-p` | Yes      | Project ID                                                                                                                                                                        |
+| `--authenticated_only` | No | Resolve only authenticated assets while building the definition. |
 | `--type`              | Yes      | Tag type. Supported values: `condition`, `metric`, `first_last`, `sql`                                                                                                            |
 | `--condition_values`  | No       | For type=condition: list of tag value definitions JSON array. Each item defines a segment label and its conditions. See `+get_tag_definition_schema` for the structure.            |
 | `--metric`            | No       | For type=metric: metric definition JSON. Fields: `eventName`, `analysis`, `quota` (property name), `recentDay`/`startTime`/`endTime`.                                             |
@@ -41,6 +42,7 @@ ae-cli analysis_audience +build_tag_definition --dry-run
 | `--sql`               | No       | For type=sql: SQL query returning two columns: `#user_id` and the tag value.                                                                                                      |
 
 ## Decision Rules
+- Use `--authenticated_only true` when the definition should only resolve authenticated events/properties/metrics/clusters/tags.
 
 - Determine `--type` first, then pass only the corresponding parameter.
 - For type=condition, `--condition_values` is effectively required.

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

@@ -0,0 +1,15 @@
+# analysis dashboard abnormal-get
+
+Use when the user needs abnormal dependency or import/export diagnostic information for one dashboard.
+
+Do not use for normal dashboard detail. Use `dashboard get`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard abnormal-get --project-id <project_id> --dashboard-id <dashboard_id>
+```
+
+Input sends `project_id` and `dashboard_id`.
+
+Output is the gateway envelope. `data` contains abnormal dependency information.

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

@@ -0,0 +1,15 @@
+# analysis dashboard copy
+
+Use when the user wants to copy a dashboard, optionally copying reports and targeting a project space or folder.
+
+Do not use to create a blank dashboard. Use `dashboard create`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard copy --project-id <project_id> --dashboard-id <source_dashboard_id> --dashboard-name <new_name> [--report-copy true] [--to-space-id <space_id>] [--to-folder-id <folder_id>] --yes
+```
+
+Input sends `project_id`, `dashboard_id`, `dashboard_name`, and optional `report_copy`, `to_space_id`, `to_folder_id`.
+
+Output is the gateway envelope. `data` contains the copied dashboard result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard create
+
+Use when the user explicitly wants to create a dashboard in personal space, a project space, or a folder.
+
+Do not use to copy an existing dashboard. Use `dashboard copy` for copy workflows.
+
+Command:
+
+```bash
+ae-cli analysis dashboard create --project-id <project_id> --dashboard-name <name> [--space-id <space_id>] [--folder-id <folder_id>] [--initial-report-id <report_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `dashboard_name`, and optional `space_id`, `folder_id`, `initial_report_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the created dashboard identity or backend create result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard-daily-report send
+
+Use when the user wants to send a dashboard daily report immediately.
+
+Do not use for configuration changes. Use `dashboard-daily-report update`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard-daily-report send --project-id <project_id> --dashboard-id <dashboard_id> [--need-csv 1] [--host-url <url>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `dashboard_id`, and optional `need_csv`, `host_url`, `payload`.
+
+Output is the gateway envelope. `data` contains the immediate send result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard-daily-report update
+
+Use when the user wants to update a dashboard daily report configuration.
+
+Do not use to send immediately. Use `dashboard-daily-report send`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard-daily-report update --project-id <project_id> --dashboard-id <dashboard_id> [--enable-send 1] [--send-time <time>] [--send-title <title>] [--send-content <content>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `dashboard_id`, and optional daily report fields or `payload`.
+
+Output is the gateway envelope. `data` contains the daily report configuration update result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard-definition export
+
+Use when the user wants to export dashboard definition JSON for selected dashboard folders or shared spaces.
+
+Do not use for dashboard report result data. Use `dashboard-report-data run` or `dashboard-report-data export`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard-definition export --project-id <project_id> [--dashboard-folder-ids '[...]'] [--shared-spaces '[...]'] [--export-file-name <name>] [--payload '{...}']
+```
+
+Input sends `project_id` and optional `dashboard_folder_ids`, `shared_spaces`, `export_file_name`, `payload`.
+
+Output is the gateway envelope. `data` contains exported definition data or an export descriptor.

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

@@ -0,0 +1,15 @@
+# analysis dashboard-definition import
+
+Use when the user wants to validate or import dashboard definition JSON. Use `--validate-only true` for pre-checks such as name conflict, reference relation, and importable state.
+
+Do not use a separate pre-check command; validation is part of this import command.
+
+Command:
+
+```bash
+ae-cli analysis dashboard-definition import --project-id <project_id> --definition '{...}' [--validate-only true] [--dashboard-name-conflict-policy <policy>] [--space-dashboard-policy <policy>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `definition`, and optional validation/import policies and `payload`.
+
+Output is the gateway envelope. `data` contains validation findings or import result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard delete
+
+Use when the user explicitly wants to delete one or more dashboards.
+
+Do not use for soft archival or hiding unless the gateway contract defines that behavior.
+
+Command:
+
+```bash
+ae-cli analysis dashboard delete --project-id <project_id> --dashboard-ids '[1001,1002]' --yes
+```
+
+Input sends `project_id` and `dashboard_ids`.
+
+Output is the gateway envelope. `data` contains the delete result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard freeze
+
+Use when the user wants to freeze or unfreeze one or more dashboards.
+
+Do not use for dashboard lock/version operations; those are intentionally not CLI-enabled.
+
+Command:
+
+```bash
+ae-cli analysis dashboard freeze --project-id <project_id> --dashboard-ids '[1001,1002]' [--freeze true] --yes
+```
+
+Input sends `project_id`, `dashboard_ids`, and optional `freeze`.
+
+Output is the gateway envelope. `data` contains the freeze or unfreeze result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard get
+
+Use when the user needs one dashboard detail, including basic metadata such as creator and create/update time, settings, reports, notes, and sharing information.
+
+Do not use to query report result data. Use `dashboard-report-data run` or `dashboard-report-data export`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard get --project-id <project_id> --dashboard-id <dashboard_id> [--use-cache true]
+```
+
+Input sends `project_id`, `dashboard_id`, and optional `use_cache`.
+
+Output is the gateway envelope. `data` contains the dashboard detail returned by the capability gateway.

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

@@ -0,0 +1,15 @@
+# analysis dashboard handover
+
+Use when the user explicitly wants to transfer one or more dashboards to another project user.
+
+Do not use to share dashboards without ownership transfer. Use `dashboard share`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard handover --project-id <project_id> --dashboard-ids '[1001,1002]' --to-user-id <user_id> --yes
+```
+
+Input sends `project_id`, `dashboard_ids`, and `to_user_id`.
+
+Output is the gateway envelope. `data` contains the handover result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard list
+
+Use when the user needs to find dashboards they can access, with optional keyword, owner, permission, favorite, or projection filters supported by the gateway payload.
+
+Do not use for dashboard report data. Use `dashboard-report-data run` or `dashboard-report-data export` instead.
+
+Command:
+
+```bash
+ae-cli analysis dashboard list --project-id <project_id> [--query <keyword>] [--fields '["id","name"]'] [--limit 20] [--offset 0]
+```
+
+Input uses `project_id` plus optional `query`, `fields`, `limit`, `offset`. Use `--payload` only when the dedicated gateway contract requires extra snake_case filters.
+
+Output is the gateway envelope. `data` contains dashboard summaries and paging metadata when returned by the gateway.

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

@@ -0,0 +1,15 @@
+# analysis dashboard-report-data export
+
+Use for dashboard report data queries that may be large or long-running.
+
+Do not use when the user needs a tiny immediate preview. Use `dashboard-report-data run` with a small `--limit`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard-report-data export --project-id <project_id> --dashboard-id <dashboard_id> [--report-ids '[1,2]'] [--filters '{...}'] [--start-time <time>] [--end-time <time>] [--artifact-format jsonl]
+```
+
+Input sends `project_id`, `dashboard_id`, and optional `report_ids`, `filters`, `start_time`, `end_time`, `use_cache`, `request_id`, `timeout_seconds`, `format`. Use CLI flag `--artifact-format` for the gateway `format` input; `--format` is the CLI output formatter.
+
+Output is the gateway envelope. `data` contains an async export descriptor such as `run_id`, `artifact_id`, status fields, inspect path, and download path.

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

@@ -0,0 +1,15 @@
+# analysis dashboard-report-data run
+
+Use for bounded inline dashboard report data queries when the expected result is small enough for immediate JSON output.
+
+Do not use for large or long-running result sets. Use `dashboard-report-data export`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard-report-data run --project-id <project_id> --dashboard-id <dashboard_id> [--report-ids '[1,2]'] [--filters '{...}'] [--start-time <time>] [--end-time <time>] [--limit 100] [--timeout-seconds 60]
+```
+
+Input sends `project_id`, `dashboard_id`, and optional `report_ids`, `filters`, `start_time`, `end_time`, `use_cache`, `request_id`, `timeout_seconds`, `limit`.
+
+Output is the gateway envelope. `data` contains bounded inline report data.

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

@@ -0,0 +1,15 @@
+# analysis dashboard share
+
+Use when the user explicitly wants to add, remove, or batch modify dashboard sharing.
+
+Do not use to read sharing only. Use `dashboard share-info`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard share --project-id <project_id> --dashboard-id <dashboard_id> [--member-authorities '{...}'] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `dashboard_id`, and either `member_authorities` or a backend-compatible snake_case `payload`.
+
+Output is the gateway envelope. `data` contains the share update result.

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

@@ -0,0 +1,15 @@
+# analysis dashboard share-info
+
+Use when the user needs to inspect a dashboard's current sharing configuration.
+
+Do not use to modify sharing. Use `dashboard share`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard share-info --project-id <project_id> --dashboard-id <dashboard_id>
+```
+
+Input sends `project_id` and `dashboard_id`.
+
+Output is the gateway envelope. `data` contains dashboard sharing members and permissions.

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

@@ -0,0 +1,15 @@
+# analysis dashboard task-status
+
+Use when the user needs scheduled task status for a dashboard.
+
+Do not use to update daily report configuration. Use `dashboard-daily-report update`.
+
+Command:
+
+```bash
+ae-cli analysis dashboard task-status --project-id <project_id> --dashboard-id <dashboard_id>
+```
+
+Input sends `project_id` and `dashboard_id`.
+
+Output is the gateway envelope. `data` contains scheduled task status.

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

@@ -0,0 +1,16 @@
+# analysis dashboard update
+
+Use when the user wants to update dashboard settings in batch or upsert a dashboard note.
+
+Do not use for moving/copying dashboards. Use `dashboard copy`, `dashboard handover`, or the relevant project-space/folder command.
+
+Command:
+
+```bash
+ae-cli analysis dashboard update --project-id <project_id> --operation settings --dashboard-ids '[1001,1002]' [--zone-offset 8] [--payload '{...}'] --yes
+ae-cli analysis dashboard update --project-id <project_id> --operation note-upsert --dashboard-id <dashboard_id> [--note-id <note_id>] [--note-title <title>] [--description <text>] --yes
+```
+
+Input sends `project_id`, `operation`, optional dashboard identifiers, setting fields (including `zone_offset` as hours, e.g. `8` for UTC+8), note fields, and optional `payload`.
+
+Output is the gateway envelope. `data` contains the update result.

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

@@ -0,0 +1,15 @@
+# analysis favorite add
+
+Use when the user wants to favorite one dashboard, BI panel, or folder.
+
+Do not use for sharing or moving assets.
+
+Command:
+
+```bash
+ae-cli analysis favorite add --project-id <project_id> [--asset-id <id>] [--asset-type dashboard|bi_panel|folder] [--space-id <space_id>] [--id <backend_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id` and asset identity fields or backend-compatible `payload`.
+
+Output is the gateway envelope. `data` contains the favorite result.

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

@@ -0,0 +1,15 @@
+# analysis favorite remove
+
+Use when the user wants to remove favorite from one dashboard, BI panel, or folder.
+
+Do not use to delete the asset itself.
+
+Command:
+
+```bash
+ae-cli analysis favorite remove --project-id <project_id> [--asset-id <id>] [--asset-type dashboard|bi_panel|folder] [--space-id <space_id>] [--id <backend_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id` and asset identity fields or backend-compatible `payload`.
+
+Output is the gateway envelope. `data` contains the remove-favorite result.

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

@@ -0,0 +1,15 @@
+# analysis folder create
+
+Use when the user explicitly wants to create a folder in personal space or a project space.
+
+Do not use to create a project space. Use `project-space create`.
+
+Command:
+
+```bash
+ae-cli analysis folder create --project-id <project_id> --folder-name <name> [--space-id <space_id>] [--parent-folder-id <folder_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `folder_name`, and optional `space_id`, `parent_folder_id`, `payload`.
+
+Output is the gateway envelope. `data` contains the created folder result.

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

@@ -0,0 +1,15 @@
+# analysis folder delete
+
+Use when the user explicitly wants to delete one or more folders.
+
+Do not use for deleting dashboards or BI panels inside a folder. Use the asset delete command.
+
+Command:
+
+```bash
+ae-cli analysis folder delete --project-id <project_id> [--folder-id <folder_id>] [--folder-ids '[1,2]'] [--space-id <space_id>] --yes
+```
+
+Input sends `project_id`, either `folder_id` or `folder_ids`, and optional `space_id`.
+
+Output is the gateway envelope. `data` contains the delete result.

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

@@ -0,0 +1,15 @@
+# analysis folder members
+
+Use when the user needs to inspect folder members.
+
+Do not use to modify members. Use `folder share`.
+
+Command:
+
+```bash
+ae-cli analysis folder members --project-id <project_id> --folder-id <folder_id>
+```
+
+Input sends `project_id` and `folder_id`.
+
+Output is the gateway envelope. `data` contains folder members.

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

@@ -0,0 +1,15 @@
+# analysis folder share
+
+Use when the user wants to add, remove, or batch modify folder sharing members.
+
+Do not use to inspect members only. Use `folder members`.
+
+Command:
+
+```bash
+ae-cli analysis folder share --project-id <project_id> --folder-id <folder_id> [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `folder_id`, and backend-compatible snake_case `payload`.
+
+Output is the gateway envelope. `data` contains the share update result.

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

@@ -28,11 +28,13 @@ ae-cli analysis_audience +list_clusters --dry-run
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
 | `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against clusterName, displayName, and remarks; if omitted, all clusters are returned. |
-| `--fields` | No | Optional return field list (JSON array). Supported fields: `id`, `clusterName`, `displayName`, `clusterType`, `progress`, `usersNum`, `refreshStatus`, `remarks`. Default fields when omitted: `id`, `clusterName`, `displayName`, `remarks`, `clusterType`, `progress`, `usersNum`. Invalid fields will fail with `INVALID_FIELDS`. |
+| `--fields` | No | Optional return field list (JSON array). Supported fields: `id`, `clusterName`, `displayName`, `clusterType`, `progress`, `usersNum`, `refreshStatus`, `remarks`, `authenticationStatus`. Default fields when omitted: `id`, `clusterName`, `displayName`, `remarks`, `clusterType`, `progress`, `usersNum`, `authenticationStatus`. Invalid fields will fail with `INVALID_FIELDS`. |
 | `--limit` | No | Optional page size. Default: 20, max: 50. |
 | `--offset` | No | Optional page offset. Default: 0. |
+| `--authenticated_only` | No | When true, return only authenticated clusters. |
 
 ## Decision Rules
+- Use `--authenticated_only true` only when the user explicitly asks for authenticated assets. `authenticationStatus` is `1` for authenticated and `0` for unauthenticated.
 - For the first execution, it is recommended to pass only the required parameters (`--project_id`) and add optional parameters after confirming the path works.
 - When troubleshooting across projects, first confirm whether `--project_id` matches the current permissions and target environment.
 

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

@@ -27,10 +27,13 @@ ae-cli analysis_meta +list_events --dry-run
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
 | `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against eventName, eventDesc, and remark; if omitted, all events are returned. |
-| `--fields` / `-f` | No | Optional fields to return (JSON array). Supported fields: `eventId`, `eventName`, `eventDesc`, `remark`, `eventTag`. Default fields when omitted: `eventId`, `eventName`, `eventDesc`, `remark`. |
-| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 10000. |
+| `--fields` / `-f` | No | Optional fields to return (JSON array). Supported fields: `eventId`, `eventName`, `eventDesc`, `remark`, `eventTag`, `authenticationStatus`. Default fields when omitted: `eventId`, `eventName`, `eventDesc`, `remark`, `authenticationStatus`. |
+| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 50. |
 | `--offset` / `-o` | No | Optional page offset. Default: 0. |
+| `--authenticated_only` | No | When true, return only authenticated events. |
+
 ## Decision Rules
+- Use `--authenticated_only true` only when the user explicitly asks for authenticated assets. `authenticationStatus` is `1` for authenticated and `0` for unauthenticated.
 - For the first run, pass only the required parameter (`--project_id`) to confirm the path works, then add optional parameters.
 - For builder-supported ad-hoc analysis, pass the user's event wording to the builder instead of pre-querying event metadata.
 - For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.

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

@@ -29,11 +29,13 @@ ae-cli analysis_meta +list_metrics --dry-run
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
 | `--query` / `-q` | No | Optional keyword filter. Fuzzy match on metricName, metricDesc, metricRemark. |
-| `--fields` | No | Optional fields to return. Supported: metricId, metricName, metricDesc, metricRemark, metricMode, openId, creator, creatorLoginName, updateOpenId, updateCreator, updateLoginName, createTime, updateTime. Default fields when omitted: metricId, metricName, metricDesc, metricRemark, metricMode. Invalid fields cause INVALID_FIELDS error. |
-| `--limit` | No | Optional limit. Default: 20, maximum: 10000. |
+| `--fields` | No | Optional fields to return. Supported: metricId, metricName, metricDesc, metricRemark, metricMode, authenticationStatus, openId, creator, creatorLoginName, updateOpenId, updateCreator, updateLoginName, createTime, updateTime. Default fields when omitted: metricId, metricName, metricDesc, metricRemark, metricMode, authenticationStatus. Invalid fields cause INVALID_FIELDS error. |
+| `--limit` | No | Optional limit. Default: 20, maximum: 50. |
 | `--offset` | No | Optional offset. Default: 0. |
+| `--authenticated_only` | No | When true, return only authenticated metrics. |
 
 ## Decision Rules
+- Use `--authenticated_only true` only when the user explicitly asks for authenticated assets. `authenticationStatus` is `1` for authenticated and `0` for unauthenticated.
 - First run should only pass the required parameter (`--project_id`), and add optional parameters only after the path is confirmed to work.
 - For pagination, use `--limit` and `--offset` together. Default limit is 20.
 - Use `--fields` to select specific columns for lighter response payloads.

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

@@ -27,12 +27,14 @@ ae-cli analysis_meta +list_properties --dry-run
 | `--scope` | No | Optional property scope. event means event properties, user means user properties. If omitted, all scopes are queried. |
 | `--event_name` | No | Optional event name. If provided, only event properties available for that event are returned. |
 | `--query` / `-q` | No | Optional keyword filter. Fuzzy match is applied to propName, propDesc, and remark; if omitted, all matched properties are returned. |
-| `--fields` / `-f` | No | Optional fields to return (JSON array). Supported fields: `propId`, `propName`, `propDesc`, `remark`, `selectType`, `tableType`, `subTableType`. Default fields when omitted: `propId`, `propName`, `propDesc`, `remark`, `selectType`, `tableType`. |
-| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 10000. |
+| `--fields` / `-f` | No | Optional fields to return (JSON array). Supported fields: `propId`, `propName`, `propDesc`, `remark`, `selectType`, `tableType`, `subTableType`, `authenticationStatus`. Default fields when omitted: `propId`, `propName`, `propDesc`, `remark`, `selectType`, `tableType`, `authenticationStatus`. |
+| `--limit` / `-l` | No | Optional page size. Default: 20, maximum: 50. |
 | `--offset` / `-o` | No | Optional page offset. Default: 0. |
+| `--authenticated_only` | No | When true, return only authenticated properties. |
 
 
 ## Decision Rules
+- Use `--authenticated_only true` only when the user explicitly asks for authenticated assets. `authenticationStatus` is `1` for authenticated and `0` for unauthenticated.
 - For the first run, pass only the required parameter (`--project_id`) to confirm the path works, then add optional parameters.
 - For builder-supported ad-hoc analysis, pass the user's property wording to the builder instead of pre-querying property metadata.
 - For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.

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

@@ -26,11 +26,13 @@ ae-cli analysis_audience +list_tags --dry-run
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
 | `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against tag names, display names, and remarks; if omitted, all tags are returned. |
-| `--fields` | No | Optional return field list (JSON array). Supported fields: `id`, `clusterName`, `displayName`, `clusterType`, `subConditionTabType`, `progress`, `usersNum`, `remarks`. Default fields when omitted: `id`, `clusterName`, `displayName`, `remarks`, `clusterType`, `subConditionTabType`, `progress`, `usersNum`. Invalid fields will fail with `INVALID_FIELDS`. |
+| `--fields` | No | Optional return field list (JSON array). Supported fields: `id`, `clusterName`, `displayName`, `clusterType`, `subConditionTabType`, `progress`, `usersNum`, `remarks`, `authenticationStatus`. Default fields when omitted: `id`, `clusterName`, `displayName`, `remarks`, `clusterType`, `subConditionTabType`, `progress`, `usersNum`, `authenticationStatus`. Invalid fields will fail with `INVALID_FIELDS`. |
 | `--limit` | No | Optional page size. Default: 20, max: 50. |
 | `--offset` | No | Optional page offset. Default: 0. |
+| `--authenticated_only` | No | When true, return only authenticated tags. |
 
 ## Decision Rules
+- Use `--authenticated_only true` only when the user explicitly asks for authenticated assets. `authenticationStatus` is `1` for authenticated and `0` for unauthenticated.
 - For the first execution, it is recommended to pass only the required parameters (`--project_id`) and add optional parameters after confirming the path works.
 - When troubleshooting across projects, first confirm whether `--project_id` matches the current permissions and target environment.
 

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

@@ -0,0 +1,15 @@
+# analysis project-space create
+
+Use when the user explicitly wants to create a project space.
+
+Do not use to create folders inside a space. Use `folder create`.
+
+Command:
+
+```bash
+ae-cli analysis project-space create --project-id <project_id> [--space-name <name>] [--space-desc <text>] [--avatar-type <type>] [--color-key <key>] [--avatar <value>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id` plus optional space metadata and `payload`.
+
+Output is the gateway envelope. `data` contains the created project-space result.

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

@@ -0,0 +1,15 @@
+# analysis project-space delete
+
+Use when the user explicitly wants to delete one or more project spaces.
+
+Do not use for removing dashboard or folder membership. Use the matching resource command.
+
+Command:
+
+```bash
+ae-cli analysis project-space delete --project-id <project_id> [--space-id <space_id>] [--space-ids '[1,2]'] --yes
+```
+
+Input sends `project_id` and either `space_id` or `space_ids`.
+
+Output is the gateway envelope. `data` contains the delete result.

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

@@ -0,0 +1,18 @@
+# analysis project-space get
+
+Use when the user needs one project space detail or name.
+
+Do not use to list all spaces. Use `project-space list`.
+
+Command:
+
+```bash
+ae-cli analysis project-space get --project-id <project_id> --space-id <space_id> [--fields '["spaceId","spaceName"]']
+```
+
+Input sends `project_id`, `space_id`, and optional `fields`.
+
+Supported fields are `spaceId`, `spaceName`, `spaceDesc`, `avatarType`, `colorKey`, `avatar`,
+`allAuthUserAuthority`, `createTime`, `updateTime`, and `owner`.
+
+Output is the gateway envelope. `data` contains project-space detail with snake_case field names.

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

@@ -0,0 +1,15 @@
+# analysis project-space list
+
+Use when the user needs project spaces they can access.
+
+Do not use for project lookup or project ID verification. Use `analysis_common +list_projects`.
+
+Command:
+
+```bash
+ae-cli analysis project-space list --project-id <project_id> [--query <keyword>] [--fields '["id","name"]'] [--limit 20] [--offset 0]
+```
+
+Input sends `project_id` and optional `query`, `fields`, `limit`, `offset`.
+
+Output is the gateway envelope. `data` contains project-space summaries.

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

@@ -0,0 +1,15 @@
+# analysis project-space members
+
+Use when the user needs to inspect project-space members.
+
+Do not use to modify members. Use `project-space share`.
+
+Command:
+
+```bash
+ae-cli analysis project-space members --project-id <project_id> --space-id <space_id>
+```
+
+Input sends `project_id` and `space_id`.
+
+Output is the gateway envelope. `data` contains project-space members.

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

@@ -0,0 +1,15 @@
+# analysis project-space share
+
+Use when the user wants to add, remove, or batch modify project-space sharing members.
+
+Do not use to inspect members only. Use `project-space members`.
+
+Command:
+
+```bash
+ae-cli analysis project-space share --project-id <project_id> --space-id <space_id> [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `space_id`, and backend-compatible snake_case `payload`.
+
+Output is the gateway envelope. `data` contains the share update result.

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

@@ -0,0 +1,15 @@
+# analysis public-link create
+
+Use when the user explicitly wants to generate a public link for a dashboard or BI panel.
+
+Do not use for internal resource URLs. Use `analysis_common +get_resource_url` when applicable.
+
+Command:
+
+```bash
+ae-cli analysis public-link create --project-id <project_id> --resource-type dashboard --resource-id <id> --effective-at "2026-07-08 00:00:00" --expires-at "2026-08-08 00:00:00" [--access-controls '{...}'] [--remark <text>] [--company-id <company_id>] [--payload '{...}'] --yes
+```
+
+Input sends `project_id`, `resource_type`, `resource_id`, `effective_at`, `expires_at`, and optional public-link fields.
+
+Output is the gateway envelope. `data` contains the generated public-link result.