@thinkingai/ae-cli 6.0.20 → 6.0.22

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

@@ -33,6 +33,7 @@ ae-cli analysis_audience +build_cluster_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      | Cluster type. Supported values: `condition`, `sql`                                                                                    |
 | `--conditions`        | No       | For type=condition: main condition group JSON (required when type=condition). See `+get_cluster_definition_schema` for the structure. |
 | `--include_filter`    | No       | For type=condition: global include condition group JSON.                                                                              |
@@ -40,6 +41,7 @@ ae-cli analysis_audience +build_cluster_definition --dry-run
 | `--sql`               | No       | For type=sql: SQL query returning a single column named `#user_id`.                                                                   |
 
 ## Decision Rules
+- Use `--authenticated_only true` when the definition should only resolve authenticated events/properties/metrics/clusters/tags.
 
 - Determine `--type` first, then pass the corresponding parameters.
 - For type=condition, `--conditions` is effectively required; `--include_filter` and `--exclude_filter` are optional global filters.

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

@@ -27,6 +27,7 @@ ae-cli analysis +build_distribution_analysis_qp --project_id <project_id> --time
 | Parameter | Required | Description |
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
+| `--authenticated_only` | No | Resolve only authenticated assets while building the QP. Do not pass this flag to `+query_adhoc`. |
 | `--time_range` | Yes | Time range JSON |
 | `--distribution_metrics` | Yes | Distribution metrics JSON array |
 | `--time_particle_size` | No | Time granularity. Allowed values: day, week, month, total. Defaults to day. |
@@ -58,6 +59,7 @@ ae-cli analysis +build_distribution_analysis_qp --project_id 3137 --time_range '
 ```
 
 ## Decision Rules
+- Use `--authenticated_only true` only when the user explicitly wants authenticated assets; do not add this flag to `+query_adhoc`.
 - After successful build (`status=generated`), call `+query_adhoc --model_type distribution --qp '<response.qp>'`.
 - If non-generated status, stop and ask user to clarify.
 

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

@@ -33,6 +33,7 @@ ae-cli analysis +build_event_analysis_qp --project_id <project_id> --time_range
 | Parameter | Required | Description |
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
+| `--authenticated_only` | No | Resolve only authenticated assets while building the QP. Do not pass this flag to `+query_adhoc`. |
 | `--time_range` | Yes | Event analysis time range JSON |
 | `--metrics` | Yes | Event metrics JSON array |
 | `--time_particle_size` | No | Time granularity. Default: total |
@@ -122,6 +123,7 @@ ae-cli analysis +build_event_analysis_qp --project_id 3137 --time_range '{"mode"
 ```
 
 ## Decision Rules
+- Use `--authenticated_only true` only when the user explicitly wants authenticated assets; do not add this flag to `+query_adhoc`.
 - After successful build, call `+query_adhoc --model_type event --qp '<response.qp>'`.
 - If build returns non-generated status, stop and ask user to clarify; do not call `+query_adhoc`.
 - Wrap JSON parameters in single quotes to avoid shell escaping issues.

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

@@ -33,6 +33,7 @@ ae-cli analysis +build_funnel_analysis_qp --project_id <project_id> --time_range
 | Parameter | Required | Description |
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
+| `--authenticated_only` | No | Resolve only authenticated assets while building the QP. Do not pass this flag to `+query_adhoc`. |
 | `--time_range` | Yes | Funnel analysis time range JSON |
 | `--funnel` | Yes | Funnel intent JSON |
 | `--relation` | No | Top-level funnel filter relation. Supported values: and, or. Default: and |
@@ -131,6 +132,7 @@ ae-cli analysis +query_adhoc --project_id 3137 --model_type funnel --qp '<respon
 ```
 
 ## Decision Rules
+- Use `--authenticated_only true` only when the user explicitly wants authenticated assets; do not add this flag to `+query_adhoc`.
 - After successful build, call `+query_adhoc --model_type funnel --qp '<response.qp>'`.
 - If build returns non-generated status, stop and ask user to clarify; do not call `+query_adhoc`.
 - Wrap JSON parameters in single quotes to avoid shell escaping issues.

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

@@ -25,6 +25,7 @@ ae-cli analysis +build_heat_map_analysis_qp --project_id <project_id> --time_ran
 | Parameter | Required | Description |
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
+| `--authenticated_only` | No | Resolve only authenticated assets while building the QP. Do not pass this flag to `+query_adhoc`. |
 | `--time_range` | Yes | Time range JSON |
 | `--heat_map` | Yes | Heatmap intent JSON |
 
@@ -45,6 +46,7 @@ ae-cli analysis +build_heat_map_analysis_qp --project_id 3137 --time_range '{"mo
 ```
 
 ## Decision Rules
+- Use `--authenticated_only true` only when the user explicitly wants authenticated assets; do not add this flag to `+query_adhoc`.
 - After successful build (`status=generated`), call `+query_adhoc --model_type heat_map --qp '<response.qp>'`.
 - If non-generated status, stop and ask user to clarify.
 

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

@@ -27,6 +27,7 @@ ae-cli analysis +build_interval_analysis_qp --project_id <project_id> --time_ran
 | Parameter | Required | Description |
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
+| `--authenticated_only` | No | Resolve only authenticated assets while building the QP. Do not pass this flag to `+query_adhoc`. |
 | `--time_range` | Yes | Time range JSON |
 | `--interval` | Yes | Interval intent JSON |
 | `--relation` | No | Filter relation for top-level filters. Values: and, or. Default: and. |
@@ -51,6 +52,7 @@ ae-cli analysis +build_interval_analysis_qp --project_id 3137 --time_range '{"mo
 ```
 
 ## Decision Rules
+- Use `--authenticated_only true` only when the user explicitly wants authenticated assets; do not add this flag to `+query_adhoc`.
 - After successful build (`status=generated`), call `+query_adhoc --model_type interval --qp '<response.qp>'`.
 - If non-generated status, stop and ask user to clarify.
 

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

@@ -26,6 +26,7 @@ ae-cli analysis +build_path_analysis_qp --project_id <project_id> --time_range '
 | Parameter | Required | Description |
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
+| `--authenticated_only` | No | Resolve only authenticated assets while building the QP. Do not pass this flag to `+query_adhoc`. |
 | `--time_range` | Yes | Time range JSON |
 | `--path` | Yes | Path intent JSON |
 
@@ -44,6 +45,7 @@ ae-cli analysis +build_path_analysis_qp --project_id 3137 --time_range '{"mode":
 ```
 
 ## Decision Rules
+- Use `--authenticated_only true` only when the user explicitly wants authenticated assets; do not add this flag to `+query_adhoc`.
 - After successful build (`status=generated`), call `+query_adhoc --model_type path --qp '<response.qp>'`.
 - If non-generated status, stop and ask user to clarify.
 

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

@@ -32,6 +32,7 @@ ae-cli analysis +build_prop_analysis_qp --project_id <project_id> --prop_analysi
 | Parameter | Required | Description |
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
+| `--authenticated_only` | No | Resolve only authenticated assets while building the QP. Do not pass this flag to `+query_adhoc`. |
 | `--prop_analysis` | Yes | User property analysis intent JSON |
 
 ## JSON Shape
@@ -110,6 +111,7 @@ ae-cli analysis +build_prop_analysis_qp --project_id 3137 --prop_analysis '{"met
 ```
 
 ## Decision Rules
+- Use `--authenticated_only true` only when the user explicitly wants authenticated assets; do not add this flag to `+query_adhoc`.
 - After successful build, call `+query_adhoc --model_type prop_analysis --qp '<response.qp>'`.
 - If build returns non-generated status, stop and ask user to clarify; do not call `+query_adhoc`.
 - Wrap JSON parameters in single quotes to avoid shell escaping issues.

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

@@ -26,6 +26,7 @@ ae-cli analysis +build_rank_list_analysis_qp --project_id <project_id> --time_ra
 | Parameter | Required | Description |
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
+| `--authenticated_only` | No | Resolve only authenticated assets while building the QP. Do not pass this flag to `+query_adhoc`. |
 | `--time_range` | Yes | Time range JSON |
 | `--rank_list` | Yes | Rank list intent JSON |
 
@@ -54,6 +55,7 @@ ae-cli analysis +build_rank_list_analysis_qp --project_id 3137 --time_range '{"m
 ```
 
 ## Decision Rules
+- Use `--authenticated_only true` only when the user explicitly wants authenticated assets; do not add this flag to `+query_adhoc`.
 - After successful build (`status=generated`), call `+query_adhoc --model_type rank_list --qp '<response.qp>'`.
 - If non-generated status, stop and ask user to clarify.
 

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

@@ -33,6 +33,7 @@ ae-cli analysis +build_retention_analysis_qp --project_id <project_id> --time_ra
 | Parameter | Required | Description |
 |---|---|---|
 | `--project_id` / `-p` | Yes | Project ID |
+| `--authenticated_only` | No | Resolve only authenticated assets while building the QP. Do not pass this flag to `+query_adhoc`. |
 | `--time_range` | Yes | Retention analysis time range JSON |
 | `--retention` | Yes | Retention intent JSON |
 | `--relation` | No | Top-level retention filter relation. Supported values: and, or. Default: and |
@@ -129,6 +130,7 @@ ae-cli analysis +build_retention_analysis_qp --project_id 3137 --time_range '{"m
 ```
 
 ## Decision Rules
+- Use `--authenticated_only true` only when the user explicitly wants authenticated assets; do not add this flag to `+query_adhoc`.
 - After successful build, call `+query_adhoc --model_type retention --qp '<response.qp>'`.
 - If build returns non-generated status, stop and ask user to clarify; do not call `+query_adhoc`.
 - Wrap JSON parameters in single quotes to avoid shell escaping issues.

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/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-generate-tracking-code/SKILL.md

@@ -58,14 +58,14 @@ First, check if `.ae-cli/draft.json` exists and read existing configuration:
 |---|---|---|
 | AE projectId | `meta.project_id` | Has value → confirm; missing → ask |
 | AE web address | `meta.host` | Has value → confirm; missing → ask |
-| **SERVER_URL** | `meta.server_url` | **Must ask**. Data ingestion endpoint — different from web address |
-| **APP_ID** | `meta.app_id` | **Must ask**. Obtained from AE Admin → "Integration Config" |
+| **SERVER_URL** | `meta.server_url` | Has value → confirm; missing → try lookup from project config, then ask if unavailable |
+| **APP_ID** | `meta.app_id` | Has value → confirm; missing → try lookup from accessible project list, then ask if unavailable |
 | SDK integration mode | `meta.sdk_integration_mode` | Has value → use directly |
 | Client SDK type | `meta.client_platforms` (preferred) or `meta.client_sdk_type` | Has value → use directly |
 | Server language | `meta.server_language` | Has value → use directly |
 | User identity system | `meta.user_identity` | Has value → use directly |
 
-**Important**: `project_id` ≠ `APP_ID`, and `host` ≠ `SERVER_URL`. Even if project_id and host are already set, SERVER_URL and APP_ID must still be asked separately.
+**Important**: `project_id` ≠ `APP_ID`, and `host` ≠ `SERVER_URL`. Even if project_id and host are already set, SERVER_URL and APP_ID must still be resolved and confirmed separately. Prefer lookup first; ask the user only when lookup is unavailable or ambiguous.
 
 **Multi-platform support**:
 - If `client_platforms` exists (array): multi-platform scenario — generate code for each platform
@@ -86,14 +86,21 @@ First, check if `.ae-cli/draft.json` exists and read existing configuration:
 - User says `yes` → use draft value
 - User enters new value → update draft.json and use new value
 
-### Required configuration (must confirm each item)
+### Required configuration (must resolve and confirm each item)
 
-**⚠️ Key: SERVER_URL and APP_ID are independent config items. Even if draft.json has project_id and host, you MUST ask. `project_id` ≠ `APP_ID`, `host` ≠ `SERVER_URL`.**
+**⚠️ Key: SERVER_URL and APP_ID are independent config items. Even if draft.json has project_id and host, you MUST resolve and confirm them. `project_id` ≠ `APP_ID`, `host` ≠ `SERVER_URL`.**
 
-1. **SERVER_URL** — Data ingestion endpoint (**different from web URL**; go to AE Admin → "Project Settings" → "Integration Config" → fill in "Public URL")
+1. **APP_ID** — Prefer automatic lookup before asking:
+   - If `meta.project_id` is known, run `ae-cli analysis_common +list_projects` once for the current host.
+   - Find the project whose `projectId` matches `meta.project_id`.
+   - If the matched project has `appId`, ask: **"I found APP_ID `<appId>` for project `<projectId>`. Use it? yes / enter new value"**
+   - If the project is missing, ambiguous, or has no `appId`, ask the user to copy APP_ID from AE Admin → "Project Settings" → "Integration Config".
+2. **SERVER_URL** — Data ingestion endpoint (**different from web URL**; go to AE Admin → "Project Settings" → "Integration Config" → fill in "Public URL")
+   - If `meta.project_id` is known, you may try `ae-cli analysis_meta +get_project_config --project_id <project_id>` once.
+   - Use the returned value only if the response explicitly contains a receiver URL field such as `serverUrl`, `pushUrl`, `push_url`, `receiverUrl`, `publicUrl`, or equivalent ingestion endpoint field.
+   - If a value is found, ask: **"I found SERVER_URL `<url>` for project `<projectId>`. Use it? yes / enter new value"**
    - ⚠️ "Public URL" only shows if previously filled in; if empty, this field won't display
    - Solution: ask ops for the URL, or **skip this step** (use `SERVER_URL` or `PUSH_URL` placeholder in code)
-2. **APP_ID** — Go to AE Admin → "Project Settings" → "Integration Config" → copy "APP_ID"
 
 **host handling** (optional):
 - If you need to fetch plan from AE (no local draft.json) → ask for host
@@ -194,7 +201,7 @@ Ask in order, one item per message:
    - Account ID source: user_account / role_id / none
    - Visitor ID strategy: auto / device_id / custom
 
-5. **SERVER_URL / APP_ID** (skip if already configured)
+5. **APP_ID / SERVER_URL**: resolve them with the lookup-first flow above, confirm any found values with the user, and ask only for values that cannot be found or are rejected by the user.
 
 **Step 4: Merge configuration and proceed to Phase 1**
 
@@ -224,26 +231,31 @@ Without `.ae-cli/draft.json` or `.ae-cli/remote-plan.json`:
 
 **Client platforms** (corresponding to client SDKs):
 
-| plan field | Platform | SDK | Document Path |
-|---|---|---|---|
-| `android` | Android | Android SDK | `~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/client-sdk/android.md` |
-| `ios` | iOS | iOS SDK | `~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/client-sdk/ios.md` |
-| `openharmony` | OpenHarmony | OpenHarmony SDK | `~/.ae-cli/wiki/te-docs/raw/客户端-sdk/openharmony.md` |
-| `javascript` | Web / H5 | JavaScript SDK | `~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/client-sdk/javascript.md` |
-| `miniprogram` | Mini-program | Mini-program SDK | `~/.ae-cli/wiki/te-docs/raw/客户端-sdk/小程序小游戏.md` |
-| `unity` | Unity | Unity SDK | `~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/client-sdk/game-engine/unity.md` |
-| `game_engine` | Game Engine | Cocos / Laya / Unreal | See `references/sdk-index.md` |
+| plan field | Platform | SDK |
+|---|---|---|
+| `android` | Android | Android SDK |
+| `ios` | iOS | iOS SDK |
+| `openharmony` | OpenHarmony | OpenHarmony SDK |
+| `javascript` | Web / H5 | JavaScript SDK |
+| `miniprogram` | Mini-program | Mini-program SDK |
+| `unity` | Unity | Unity SDK |
+| `game_engine` | Game Engine | Cocos / Laya / Unreal |
 
 **Server languages** (corresponding to server SDKs):
 
-| plan field | Language | SDK | Document Path |
-|---|---|---|---|
-| `java` | Java | Java SDK | `~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/server-sdk/java.md` |
-| `python` | Python | Python SDK | `~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/server-sdk/python.md` |
-| `go` | Go | Go SDK | `~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/server-sdk/golang.md` |
-| `nodejs` | Node.js | Node SDK | `~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/server-sdk/nodejs.md` |
-| `php` | PHP | PHP SDK | `~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/server-sdk/php.md` |
-| `csharp` | C# | C# SDK | `~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/server-sdk/c.md` |
+| plan field | Language | SDK |
+|---|---|---|
+| `java` | Java | Java SDK |
+| `python` | Python | Python SDK |
+| `go` | Go | Go SDK |
+| `nodejs` | Node.js | Node SDK |
+| `php` | PHP | PHP SDK |
+| `csharp` | C# | C# SDK |
+
+**SDK document paths**:
+- Do not use hard-coded wiki paths from this section.
+- Always read `references/sdk-index.md` first and use the path listed there for the selected SDK.
+- If the path from `references/sdk-index.md` does not exist in the local wiki mirror, search under `~/.ae-cli/wiki/te-docs/raw/` with SDK-specific keywords and use the best matching latest main document.
 
 ---
 
@@ -437,7 +449,7 @@ test -z "$(git status --porcelain)" || echo "uncommitted changes present"
 **Only generate events where `platform === "client"` or `platform === "both"`**
 
 **⚠️ Hard rule: Never guess SDK imports**
-- Before generating, MUST read the corresponding SDK wiki document (see `references/sdk-index.md`)
+- Before generating, MUST read `references/sdk-index.md`, resolve the corresponding SDK wiki main document, verify the path exists, and then read that main document
 - **MUST copy import statements and package names from the wiki main document**, never guess
 - Example: JavaScript SDK npm package is `thinkingdata-browser`, import variable is `ta`
 - If generated code doesn't match wiki docs (e.g. `TDAnalytics`/`te`/`@thinkingdata/web-sdk`), re-read wiki and fix
@@ -460,7 +472,7 @@ test -z "$(git status --porcelain)" || echo "uncommitted changes present"
 - **Always provide LogBus2 official docs link**: https://docs-v2.thinkingdata.cn/?version=latest&code=logbus2_installation&lan=en-US
 
 **⚠️ Hard rule: Never guess SDK imports**
-- Before generating, MUST read the corresponding SDK wiki document (see `references/sdk-index.md`)
+- Before generating, MUST read `references/sdk-index.md`, resolve the corresponding SDK wiki main document, verify the path exists, and then read that main document
 - **MUST copy import statements and package names from the wiki main document**, never guess
 - **Re-read docs before every code generation**, never rely on "remembered" code
 
@@ -478,6 +490,25 @@ test -z "$(git status --porcelain)" || echo "uncommitted changes present"
 
 Show deliverables based on selected output modes:
 
+### Attachment upload
+
+After all `.ae-cli/output/` files are generated, upload every generated output file to the Agent attachment library so the user can download them from the file/attachment management entry.
+
+Use the existing attachment command:
+
+```bash
+ae-cli agent +add-attachment --yes --files '<json-array-of-generated-output-files>'
+```
+
+Upload list rules:
+- Include all generated snippet files under `.ae-cli/output/`.
+- Include generated server config files such as `.ae-cli/output/daemon.json` and LogBus README files.
+- Include `.ae-cli/output/README.md`.
+- Include generated debug scripts if the user selected the debug option.
+- Do not upload files inserted directly into the user's project; only upload generated output artifacts.
+
+If upload succeeds, include the attachment upload result in the final response and tell the user the files are available from the file/attachment management entry. If upload fails because Agent attachment credentials are unavailable, keep the local `.ae-cli/output/` files and tell the user the upload did not complete.
+
 ### All snippets
 
 ```
@@ -496,6 +527,8 @@ Standalone:
 - .ae-cli/output/te-debug.java (validation script)
 
 README: .ae-cli/output/README.md (usage instructions)
+
+Attachment upload: uploaded generated output files to the file/attachment management entry
 ```
 
 ### Mixed (some insert + some snippet)
@@ -514,6 +547,8 @@ LogBus2 official docs: https://docs-v2.thinkingdata.cn/?version=latest&code=logb
 
 Standalone:
 - .ae-cli/output/te-debug.java (validation script)
+
+Attachment upload: uploaded generated output files to the file/attachment management entry
 ```
 
 ### Markdown code snippet display
@@ -623,7 +658,9 @@ All output mode rules are in `references/*.md`. This SKILL.md only handles phase
 - `~/.ae-cli/wiki/te-docs/synthesis/` — LLM-synthesized overview documents
 
 **Document reading order during code generation**:
-1. Read `references/sdk-index.md` to find the SDK's wiki document path
-2. Read wiki main doc (initialization, basic API)
-3. Read wiki advanced guide (LoggerConsumer, user properties, etc.)
-4. Check advanced guide sub-documents if needed
+1. Read `references/sdk-index.md` to find the selected SDK's main document and advanced guide paths.
+2. Verify the main document path exists in the local wiki mirror before reading it.
+3. If the indexed path is missing, search under `~/.ae-cli/wiki/te-docs/raw/` with SDK-specific keywords such as SDK name, platform name, language name, and `main doc`; choose the latest main document, not historical/versioned documents.
+4. Read the wiki main doc first (initialization, imports, package names, basic API).
+5. Read the advanced guide only after the main doc (LoggerConsumer, user properties, auto-track, preset properties, etc.).
+6. Check advanced guide sub-documents if needed.

package/skills/ae-generate-tracking-code/references/snippet-delivery.md

@@ -4,9 +4,10 @@
 
 ## Deliverables
 
-Two outputs:
+Three outputs:
 1. **Markdown response**: code snippets grouped by platform (for reading)
 2. **Code files**: `.ae-cli/output/<platform>-sdk.<ext>` (for copy-paste use)
+3. **Attachment library upload**: generated files uploaded with `ae-cli agent +add-attachment` so the user can download them from the file/attachment management entry
 
 ---
 
@@ -230,6 +231,26 @@ AE Debug mode requires the device ID to be added in AE Admin before data can be
 
 ---
 
+## Attachment Library Upload
+
+After all snippet output files are written, upload generated output artifacts to the Agent attachment library:
+
+```bash
+ae-cli agent +add-attachment --yes --files '<json-array-of-generated-output-files>'
+```
+
+Upload list must include:
+- Every generated platform snippet file under `.ae-cli/output/`
+- `.ae-cli/output/README.md`
+- Server-side config files, including `.ae-cli/output/daemon.json` and related README files
+- Generated debug scripts, if any
+
+Only upload generated output artifacts. Do not upload files inserted directly into the user's project.
+
+If upload succeeds, report that the files are available from the file/attachment management entry. If upload fails because Agent attachment credentials are unavailable, preserve the local output files and report the upload failure separately.
+
+---
+
 ## Generation Workflow
 
 ### ⚠️ Mandatory Pre-checks (do not skip)
@@ -302,6 +323,10 @@ After generation, perform language style checks on each output file:
 1. Additionally generate `daemon.json` for server-side
 2. **Must always provide LogBus2 official documentation link**
 
+#### Step 5: Upload Generated Artifacts
+
+Upload all generated `.ae-cli/output/` artifacts to the Agent attachment library using `ae-cli agent +add-attachment --yes --files '<json-array>'`.
+
 ---
 
 ## Code Style