@thinkingai/ae-cli 6.0.30 → 6.0.32

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

@@ -0,0 +1,25 @@
+# analysis project member import
+
+Use when the user needs to import members and roles from another 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 member import --project-id <project_id> --source-project-id <source_project_id>
+ae-cli analysis project member import --dry-run --project-id <project_id> --source-project-id <source_project_id>
+```
+
+Capability id: `project.member.import`.
+
+Input sends `project_id`, `source_project_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. |
+| `--source-project-id` | Yes | Project ID to import members from. |

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

@@ -0,0 +1,23 @@
+# analysis project member list
+
+Use when the user needs to list project members.
+
+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 member list --project-id <project_id>
+ae-cli analysis project member list --dry-run --project-id <project_id>
+```
+
+Capability id: `project.member.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_member_receiver_list.md

@@ -0,0 +1,23 @@
+# analysis project member-receiver list
+
+Use when the user needs to list project member handover receivers.
+
+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 member-receiver list --project-id <project_id>
+ae-cli analysis project member-receiver list --dry-run --project-id <project_id>
+```
+
+Capability id: `project.member_receiver.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_member_remove.md

@@ -0,0 +1,26 @@
+# analysis project member remove
+
+Use when the user needs to remove a project member and optionally hand over assets.
+
+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 member remove --project-id <project_id> --payload <payload> --from-open-id <from_open_id>
+ae-cli analysis project member remove --dry-run --project-id <project_id> --payload <payload> --from-open-id <from_open_id>
+```
+
+Capability id: `project.member.remove`.
+
+Input sends `project_id`, `payload`, `from_open_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. |
+| `--payload` | Yes | Remove member payload matching RemoveProjMemberReq in snake_case. |
+| `--from-open-id` | Yes | Open ID of the member to remove. |

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

@@ -0,0 +1,25 @@
+# analysis project member update
+
+Use when the user needs to update one project member.
+
+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 member update --project-id <project_id> --payload <payload> --target-user-id <target_user_id>
+ae-cli analysis project member update --dry-run --project-id <project_id> --payload <payload> --target-user-id <target_user_id>
+```
+
+Capability id: `project.member.update`.
+
+Input sends `project_id`, `payload`, `target_user_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. |
+| `--payload` | Yes | Member edit payload matching ProjMemberEditReq in snake_case. |
+| `--target-user-id` | Yes | Target user ID. |

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

@@ -0,0 +1,27 @@
+# analysis project owner update
+
+Use when the user needs to update project owner.
+
+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 owner update --project-id <project_id> --company-id <company_id> --owner-user-id <owner_user_id> --project-name <project_name> --project-remark <project_remark>
+ae-cli analysis project owner update --dry-run --project-id <project_id> --company-id <company_id>
+```
+
+Capability id: `project.owner.update`.
+
+Input sends `project_id`, `company_id`, `owner_user_id`, `project_name`, `project_remark`. 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. |
+| `--company-id` | Yes | Company ID. |
+| `--owner-user-id` | No | New owner user ID. Omit to only downgrade existing owner. |
+| `--project-name` | No | Optional project name update. |
+| `--project-remark` | No | Optional project remark update. |

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

@@ -0,0 +1,24 @@
+# analysis project permission-binding list
+
+Use when the user needs to list project role and data-power bindings for company-level permission management.
+
+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 permission-binding list --company-id <company_id> --project-ids <project_ids>
+ae-cli analysis project permission-binding list --dry-run --company-id <company_id> --project-ids <project_ids>
+```
+
+Capability id: `project.permission_binding.list`.
+
+Input sends `company_id`, `project_ids`. 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. |
+| `--project-ids` | Yes | Project IDs JSON array. |

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

@@ -0,0 +1,25 @@
+# analysis project receive-status update
+
+Use when the user needs to update project data receive status.
+
+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 receive-status update --project-id <project_id> --receive-status <receive_status>
+ae-cli analysis project receive-status update --dry-run --project-id <project_id> --receive-status <receive_status>
+```
+
+Capability id: `project.receive_status.update`.
+
+Input sends `project_id`, `receive_status`, `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. |
+| `--receive-status` | Yes | Receive status: NORMAL or STOP_RECEIVE. |

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

@@ -0,0 +1,25 @@
+# analysis project role delete
+
+Use when the user needs to delete a role and optionally migrate users to another role.
+
+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 role delete --role-name <role_name> --new-role-name <new_role_name>
+ae-cli analysis project role delete --dry-run --role-name <role_name>
+```
+
+Capability id: `project.role.delete`.
+
+Input sends `role_name`, `new_role_name`, `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 |
+|---|---|---|
+| `--role-name` | Yes | Role name to delete. |
+| `--new-role-name` | No | Role name to migrate users to before deletion. |

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

@@ -0,0 +1,27 @@
+# analysis project role-function list
+
+Use when the user needs to list functions granted to one or more roles.
+
+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 role-function list --company-id <company_id> --project-id <project_id> --role-name <role_name> --role-names <role_names> --show-system-func <show_system_func>
+ae-cli analysis project role-function list --dry-run 
+```
+
+Capability id: `project.role_function.list`.
+
+Input sends `company_id`, `project_id`, `role_name`, `role_names`, `show_system_func`. 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. |
+| `--role-name` | No | Single role name. |
+| `--role-names` | No | Role names JSON array. When omitted, all role functions are returned. |
+| `--show-system-func` | No | Whether to include system functions. Default false. |

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

@@ -0,0 +1,23 @@
+# analysis project role get
+
+Use when the user needs to get one role by role name.
+
+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 role get --role-name <role_name>
+ae-cli analysis project role get --dry-run --role-name <role_name>
+```
+
+Capability id: `project.role.get`.
+
+Input sends `role_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 |
+|---|---|---|
+| `--role-name` | Yes | Role name. |

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

@@ -0,0 +1,25 @@
+# analysis project role list
+
+Use when the user needs to list project-visible roles.
+
+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 role list --company-id <company_id> --project-id <project_id> --visible-only <visible_only>
+ae-cli analysis project role list --dry-run 
+```
+
+Capability id: `project.role.list`.
+
+Input sends `company_id`, `project_id`, `visible_only`. 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. Required when project_id is absent. |
+| `--project-id` | No | Project ID. Required when company_id is absent. |
+| `--visible-only` | No | When true, list roles visible to the current user. |

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

@@ -0,0 +1,24 @@
+# analysis project role upsert
+
+Use when the user needs to create or update a project role.
+
+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 role upsert --project-id <project_id> --payload <payload>
+ae-cli analysis project role upsert --dry-run --project-id <project_id> --payload <payload>
+```
+
+Capability id: `project.role.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 | Role save payload matching RoleSaveRequestDTO in snake_case. |

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

@@ -0,0 +1,23 @@
+# analysis project role-user list
+
+Use when the user needs to list users bound to a role.
+
+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 role-user list --role-name <role_name>
+ae-cli analysis project role-user list --dry-run --role-name <role_name>
+```
+
+Capability id: `project.role_user.list`.
+
+Input sends `role_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 |
+|---|---|---|
+| `--role-name` | Yes | Role name. |

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

@@ -4,15 +4,14 @@ Use when the user explicitly wants to create a project space.
 
 Do not use to create folders inside a space. Use `analysis.folder.create` via capability run.
 
-This capability has no curated `ae-cli analysis` command. Read [`ae-capability`](../../ae-capability/SKILL.md), then:
+This capability has no curated `ae-cli analysis` command. Read [`ae-capability`](../../ae-capability/SKILL.md) (on-demand validate/dry-run table), then:
 
 ```bash
 ae-cli capability inspect analysis.project_space.create
-ae-cli capability dry-run analysis.project_space.create --input '{"project_id":1,"space_name":"lds-test-071301","avatar_type":1}'
 ae-cli capability run analysis.project_space.create --input '{"project_id":1,"space_name":"lds-test-071301","avatar_type":1}'
 ```
 
-`risk=write` — no chat confirmation required after dry-run succeeds.
+`risk=write` — no chat confirmation required.
 
 Input uses snake_case JSON. Common fields:
 

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

@@ -7,9 +7,11 @@ Do not use for project lookup or project ID verification. Use `analysis_common +
 Command:
 
 ```bash
-ae-cli analysis project-space list --project-id <project_id> [--query <keyword>] [--fields '["id","name"]'] [--limit 20] [--offset 0]
+ae-cli analysis project-space list --project-id <project_id> [--query <keyword>] [--fields '["id","name"]'] [--limit 50] [--offset 0]
 ```
 
 Input sends `project_id` and optional `query`, `fields`, `limit`, `offset`.
 
+When `has_more=true`, continue only with the returned `next_offset`; do not calculate the next page locally.
+
 Output is the gateway envelope. `data` contains project-space summaries.

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

@@ -4,15 +4,14 @@ Use when the user wants to modify project-space sharing members.
 
 Do not use to inspect members only. Use `analysis.project_space.members` via `capability search/inspect/run`; see [`analysis_gateway_assets.md`](analysis_gateway_assets.md) L3 members section.
 
-This capability has no curated `ae-cli analysis` command. Read [`ae-capability`](../../ae-capability/SKILL.md), then:
+This capability has no curated `ae-cli analysis` command. Read [`ae-capability`](../../ae-capability/SKILL.md) (on-demand validate/dry-run table), then:
 
 ```bash
 ae-cli capability inspect analysis.project_space.share
-ae-cli capability dry-run analysis.project_space.share --input '{"project_id":1,"space_id":10,"payload":{...}}'
 ae-cli capability run analysis.project_space.share --input '{"project_id":1,"space_id":10,"payload":{...}}'
 ```
 
-`risk=write` — no chat confirmation required after dry-run succeeds.
+`risk=write` — no chat confirmation required. Compose nested `payload` from the inspect `input_schema`.
 
 Input uses snake_case JSON. Common fields:
 

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

@@ -0,0 +1,23 @@
+# analysis project timezone get
+
+Use when the user needs to get project time zone configuration.
+
+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 timezone get --project-id <project_id>
+ae-cli analysis project timezone get --dry-run --project-id <project_id>
+```
+
+Capability id: `project.timezone.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_timezone_overview.md

@@ -0,0 +1,23 @@
+# analysis project timezone overview
+
+Use when the user needs to get project time zone overview.
+
+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 timezone overview --project-id <project_id>
+ae-cli analysis project timezone overview --dry-run --project-id <project_id>
+```
+
+Capability id: `project.timezone.overview`.
+
+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_timezone_update.md

@@ -0,0 +1,25 @@
+# analysis project timezone update
+
+Use when the user needs to update one project time zone configuration item.
+
+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 timezone update --project-id <project_id> --payload <payload> --item <item>
+ae-cli analysis project timezone update --dry-run --project-id <project_id> --payload <payload> --item <item>
+```
+
+Capability id: `project.timezone.update`.
+
+Input sends `project_id`, `payload`, `item`. 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 | Timezone update payload. Shape depends on item. |
+| `--item` | Yes | Timezone item: timezone_toggle, zone_offset, user_timezone, project_timezone_display. |

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

@@ -0,0 +1,24 @@
+# analysis project user-id-items update
+
+Use when the user needs to update project virtual user ID item configuration.
+
+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 user-id-items update --project-id <project_id> --payload <payload>
+ae-cli analysis project user-id-items update --dry-run --project-id <project_id> --payload <payload>
+```
+
+Capability id: `project.user_id_items.update`.
+
+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 | Virtual user ID item configuration payload, matching VirtualUserIdConfigSaveRequestDTO in snake_case. |

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

@@ -2,7 +2,7 @@
 
 Use when the user needs to list property metadata change logs.
 
-Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+Do not use it for the current property definition or historical data values; use `property get` or an analysis query.
 
 Command:
 
@@ -15,7 +15,7 @@ Capability id: `metadata.property.changelog_list`.
 
 Input sends `project_id`, `table_type`, `prop_name`.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output `data.changelogs[]` contains metadata change records for the property.
 
 ## Parameters
 | Parameter | Required | Description |

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

@@ -2,12 +2,12 @@
 
 Use when the user needs to create event or user properties and optionally associate events.
 
-Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+Do not use it for virtual properties or description-only updates. Choose `table-type event|user` first because the two payload variants differ.
 
 Command:
 
 ```bash
-ae-cli analysis-meta property create --project-id <project_id> --table-type <table_type> --payload '{}'
+ae-cli analysis-meta property create --project-id <project_id> --table-type event --payload '{"prop_name":"amount","prop_desc":"Amount","select_type":"number","common_prop":false,"super_event_ids":[<event_id>]}'
 ae-cli analysis-meta property create --dry-run
 ```
 
@@ -15,11 +15,11 @@ Capability id: `metadata.property.create`.
 
 Input sends `project_id`, `table_type`, `payload`.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output is a successful gateway envelope with no business data. Read back with `property get` using the same table type.
 
 ## Parameters
 | Parameter | Required | Description |
 |---|---|---|
 | `--project-id` | Yes | Numeric project ID. |
 | `--table-type` | Yes | Property table type. |
-| `--payload` | Yes | Capability payload JSON. |
+| `--payload` | Yes | Event form requires `prop_name`, `select_type`; optional `prop_desc`, `prop_remark`, `common_prop`, `super_event_ids`, `source_event_prop`. User form requires `prop_name`, `select_type`; optional `prop_desc`, `prop_remark`, `source_user_prop`. Source objects use `prop_name`, `source_type`, optional `source_route_code`. |

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

@@ -2,20 +2,21 @@
 
 Use when the user needs to batch delete properties or virtual properties.
 
-Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+Do not use it before `property influence-list` is reviewed for every target, and do not mix event/user table types.
 
 Command:
 
 ```bash
-ae-cli analysis-meta property delete --project-id <project_id> --table-type <table_type> --prop-names '{}'
-ae-cli analysis-meta property delete --dry-run
+ae-cli analysis-meta property delete --project-id <project_id> --table-type event --prop-names '["amount"]' --dry-run
+# Summarize the target and impact, then wait for explicit user confirmation.
+ae-cli analysis-meta property delete --project-id <project_id> --table-type event --prop-names '["amount"]' --yes
 ```
 
 Capability id: `metadata.property.delete`.
 
 Input sends `project_id`, `table_type`, `prop_names`.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output is a successful gateway envelope with no business data. Verify with `property list`.
 
 ## Parameters
 | Parameter | Required | Description |

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

@@ -2,7 +2,7 @@
 
 Use when the user needs to get one event or user property metadata detail.
 
-Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+Do not use it for property values or fuzzy discovery; use an analysis query or `property list`.
 
 Command:
 
@@ -15,7 +15,7 @@ Capability id: `metadata.property.get`.
 
 Input sends `project_id`, `table_type`, `prop_name`.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output `data.property` contains the event/user property metadata detail.
 
 ## Parameters
 | Parameter | Required | Description |

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

@@ -2,12 +2,12 @@
 
 Use when the user needs to batch hide or show properties.
 
-Do not use this command for unrelated analysis queries, ad-hoc query construction, or MCP metadata discovery when an existing specialized command already fits the user's request.
+Do not use it for deletion: this keeps the property but changes metadata visibility. Keep all targets in one table type.
 
 Command:
 
 ```bash
-ae-cli analysis-meta property hide-update --project-id <project_id> --table-type <table_type> --prop-names '{}' --is-hide true
+ae-cli analysis-meta property hide-update --project-id <project_id> --table-type event --prop-names '["amount"]' --is-hide true
 ae-cli analysis-meta property hide-update --dry-run
 ```
 
@@ -15,7 +15,7 @@ Capability id: `metadata.property.hide_update`.
 
 Input sends `project_id`, `table_type`, `prop_names`, `is_hide`.
 
-Output is the gateway envelope. `data` contains the common-service capability result.
+Output is a successful gateway envelope with no business data. Verify with `property list|get`.
 
 ## Parameters
 | Parameter | Required | Description |