@thinkingai/ae-cli 1.0.1

package/skills/te-meta/references/list-metrics.md

@@ -0,0 +1,33 @@
+# te_meta +list_metrics (Metric Search)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Metadata Query**
+
+## Use Cases
+- List metric metadata in the project. Supports keyword filtering and returns metric IDs, names, display names, model types, remarks, and related metadata, but not metric calculation results.
+- List metric metadata in the project.
+
+## Command
+```bash
+ae-cli te_meta +list_metrics --project_id 1
+ae-cli te_meta +list_metrics --project_id 1 --query demo
+ae-cli te_meta +list_metrics --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--query` / `-q` | No | Optional keyword filter. Performs fuzzy matching against metric names, display names, and remarks; if omitted, all metrics are returned. |
+
+## Decision Rules
+- First run should only pass the required parameter (`--project_id`), and add optional parameters only after the path is confirmed to work.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Steps After Failure
+- If the required parameter is missing, fall back to the smallest runnable command and fill it in (focus on `--project_id`).
+- If the result is empty, first confirm the project ID/keyword, then try loosening the filter conditions.
+
+## Recommended Chaining
+- +list_metrics -> +create_metric -> +get_metric

package/skills/te-meta/references/list-project-mark-times.md

@@ -0,0 +1,33 @@
+# te_meta +list_project_mark_times (List Project Mark Times)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Project Configuration**
+
+## Use Cases
+- List project date markers. Returns marker IDs, timestamps, content, and visibility status.
+- List project date markers.
+
+## Commands
+```bash
+te-cli te_meta +list_project_mark_times --project_id 1
+te-cli te_meta +list_project_mark_times --project_id 1 --zone_offset 8
+te-cli te_meta +list_project_mark_times --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--zone_offset` | No | Marker time zone offset |
+
+## Decision Rules
+- For the first run, pass only the required parameter (`--project_id`) to confirm the path works, then add optional parameters.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Steps After Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in first (focus on `--project_id`).
+- If the result is empty, first confirm the project ID/keyword, then try loosening the filter conditions.
+
+## Recommended Chaining
+- +get_project_config -> +list_project_mark_times

package/skills/te-meta/references/list-project-users.md

@@ -0,0 +1,32 @@
+# te_meta +list_project_users (Read Project Member List)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Project Configuration**
+
+## Use Cases
+- Get all project members. Returns userId, loginName, and userName for each member. Use this to resolve userId when managing dashboard share members.
+- Get all project members.
+
+## Command
+```bash
+te-cli te_meta +list_project_users --project_id 1
+te-cli te_meta +list_project_users --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+
+## Decision Rules
+- First run should only pass the required parameter (`--project_id`), and add optional parameters only after the path is confirmed to work.
+- The result can be used for dashboard member configuration, permission mapping, and similar scenarios.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Steps After Failure
+- If the required parameter is missing, fall back to the smallest runnable command and fill it in (focus on `--project_id`).
+- If the result is empty, first confirm the project ID/keyword, then try loosening the filter conditions.
+
+## Recommended Chaining
+- +get_project_config -> +list_project_users

package/skills/te-meta/references/list-properties.md

@@ -0,0 +1,35 @@
+# te_meta +list_properties (Property Metadata Discovery)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Metadata Query**
+
+## Use Cases
+- Read-only query for SYSTEM METADATA properties already effective in the project. Supports event/user scope. Do NOT use for tracking-plan metadata (bury/track program); that belongs to BuryProgramTool.
+- Read-only query for SYSTEM METADATA properties already effective in the project.
+
+## Commands
+```bash
+te-cli te_meta +list_properties --project_id 1
+te-cli te_meta +list_properties --project_id 1 --scope event --event_name purchase --query demo
+te-cli te_meta +list_properties --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--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. Performs fuzzy matching against property names, descriptions, and AI remarks; if omitted, all matched properties are returned. |
+
+## Decision Rules
+- For the first run, pass only the required parameter (`--project_id`) to confirm the path works, then add optional parameters.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+
+## Next Steps After Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in first (focus on `--project_id`).
+- If the result is empty, first confirm the project ID/keyword, then try loosening the filter conditions.
+
+## Recommended Chaining
+- +list_properties -> +create_virtual_property

package/skills/te-meta/references/save-track-items.md

@@ -0,0 +1,34 @@
+# te_meta +save_track_items (Save Track Program Items)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Project Configuration**
+
+## Use Cases
+- Create/update TRACKING-PLAN metadata only (planned bury items). Do not use this tool to create or edit effective system metadata. If the user intent is production metadata changes, route to MetaPowerTool instead.
+- Create/update TRACKING-PLAN metadata only (planned bury items).
+
+## Command
+```bash
+te-cli te_meta +save_track_items --project_id 1 --track_data '{}'
+te-cli te_meta +save_track_items --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--track_data` | Yes | Track program JSON object. Example: {"events":[{"eventName":"purchase","displayName":"Purchase","eventDesc":"User purchases a product","eventTag":"eCommerce","dataOrigin":"APP","props":["item_id","price"]}],"eventProps":[{"name":"price","displayName":"Price","type":"number","desc":"Product price"}],"userProps":[{"name":"vip_level","displayName":"Membership Level","type":"string","updateType":"user_set","propTag":"Membership","desc":"User membership level"}],"commonEventProps":[{"name":"platform","displayName":"Platform","type":"string","desc":"Application platform"}]}. Required fields: eventName/name and type. type values: string, number, datetime, bool, array_string, row, array_row. updateType values: user_setOnce, user_set, user_add, user_append. Constraints: eventName/name max 64 chars (letters, digits, underscore), displayName max 60 chars, desc/eventDesc max 200 chars. |
+
+## Decision Rules
+- First run should only pass the required parameters (`--project_id`, `--track_data`), and add optional parameters only after the path is confirmed to work.
+- Wrap JSON arguments in single quotes (for example `--track_data '{}'`) to avoid shell escaping issues.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+- Write operations keep the confirmation prompt by default; re-evaluate whether to use `--yes` in automation scenarios.
+
+## Next Steps After Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--project_id` and `--track_data`).
+- If `Invalid JSON` occurs, validate with the smallest JSON structure first (for example `{}` or `[]`), then add fields step by step.
+
+## Recommended Chaining
+- +get_track_program -> +save_track_items -> +get_track_program

package/skills/te-meta/references/update-metric.md

@@ -0,0 +1,61 @@
+# te_meta +update_metric (Update Metric)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Metadata Query**
+
+## Use Cases
+- Before updating `events` / `params`, you must first obtain the corresponding model schema and supplement the project with real event/property metadata.
+- Update a metric definition. Currently only the event and retention models are supported. Returns the updated metric information without executing metric calculation.
+- Update a metric definition.
+
+## MUST Prerequisites
+- Before updating `--events` / `--params`, you must first read and follow these reference documents:
+  - [`../../te-analysis/references/get-analysis-query-schema.md`](../../te-analysis/references/get-analysis-query-schema.md)
+  - [`./list-events.md`](./list-events.md)
+  - [`./list-properties.md`](./list-properties.md)
+- Do not submit new `events` / `params` until the document review and prerequisite command calls above are complete.
+
+## Prerequisite Call Chain (Required for Updating events/params)
+1. Determine `--model_type` first (`event` / `retention`).
+2. Read `get-analysis-query-schema.md`, then call `te-cli te_analysis +get_analysis_query_schema --model_type <event|retention>` to get the structure.
+3. Read `list-events.md`, then call `te-cli te_meta +list_events --project_id 1`.
+4. Read `list-properties.md`, then call `te-cli te_meta +list_properties --project_id 1`.
+5. Build the new `events` / `params` from the schema + metadata, then execute `+update_metric`.
+
+## Commands
+```bash
+te-cli te_meta +update_metric --project_id 1 --metric_id 1 --name demo --display_name demo --model_type event --events '[]'
+te-cli te_meta +update_metric --project_id 1 --metric_id 1 --name demo --display_name demo --remark demo --model_type event --events '[]' --params '{}'
+te-cli te_meta +update_metric --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--project_id` / `-p` | Yes | Project ID |
+| `--metric_id` / `-m` | Yes | Metric ID |
+| `--name` | Yes | Metric name. Must start with a lowercase letter and contain only lowercase letters, digits, and underscores. Maximum length: 80. |
+| `--display_name` | Yes | Metric display name |
+| `--remark` | No | Optional metric remark |
+| `--model_type` | Yes | Metric model type. Currently supports event and retention. |
+| `--events` | Yes | Metric event JSON. MUST follow `+get_analysis_query_schema` for the selected `model_type`, and use fields validated by `te_meta +list_events` / `te_meta +list_properties` in the same `project_id`. |
+| `--params` | No | Metric params JSON. If provided, MUST follow the schema from `+get_analysis_query_schema` and use project metadata from `te_meta +list_events` / `te_meta +list_properties`. |
+
+## Decision Rules
+- `events` / `params` must not be handwritten by intuition alone: they must satisfy both the schema structure and the project's real metadata constraints.
+- Set `--model_type` first, then use the matching schema; do not mix event/retention structures.
+- Before calling `list_events` / `list_properties`, you must first study the corresponding reference documents.
+- For the first run, pass only the required parameters (`--project_id`, `--metric_id`, `--name`) to confirm the path works, then add optional parameters.
+- Wrap JSON parameters in single quotes (for example `--events '{}'` and `--params '{}'`) to avoid shell escaping issues.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+- Write operations keep confirmation prompts by default; evaluate whether to use `--yes` only for automation scenarios.
+
+## Next Steps After Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in first (focus on `--project_id`, `--metric_id`, and `--name`).
+- If `Invalid JSON` appears, first check the schema's required fields, then verify whether the event and property names come from metadata query results in the same `project_id`.
+- If the result after writing does not match expectations, immediately reread the corresponding list/get interfaces for before-and-after comparison.
+
+## Recommended Chaining
+- +get_analysis_query_schema -> te_meta +list_events -> te_meta +list_properties -> +update_metric
+- +list_metrics -> +get_metric -> +update_metric

package/skills/te-meta/references/update-project-mark-time.md

@@ -0,0 +1,39 @@
+# te_meta +update_project_mark_time (Update Project Date Marker)
+
+> **Prerequisite:** Read [`../te-shared/SKILL.md`](../../te-shared/SKILL.md)
+
+Domain: **Project Configuration**
+
+## Use Cases
+- Update an existing project date marker. Returns the updated marker ID, timestamp, content, and visibility status.
+- Update an existing project date marker.
+
+## Command
+```bash
+te-cli te_meta +update_project_mark_time --mark_time_id 1 --project_id 1 --marked_at '2026-04-09 10:00' --content demo
+te-cli te_meta +update_project_mark_time --mark_time_id 1 --project_id 1 --marked_at '2026-04-09 10:00' --zone_offset 8 --content demo --is_visible 1
+te-cli te_meta +update_project_mark_time --dry-run
+```
+
+## Parameters
+| Parameter | Required | Description |
+|---|---|---|
+| `--mark_time_id` | Yes | Marker ID |
+| `--project_id` / `-p` | Yes | Project ID |
+| `--marked_at` | Yes | Marker timestamp. Format: yyyy-MM-dd HH:mm |
+| `--zone_offset` | No | Marker time zone offset |
+| `--content` | Yes | Marker content |
+| `--is_visible` | No | Whether the marker is visible. Default: 1 |
+
+## Decision Rules
+- First run should only pass required parameters (`--mark_time_id`, `--project_id`, `--marked_at`), and add optional parameters only after the path is confirmed to work.
+- For date/time ranges, first validate with a short range, then expand the range step by step.
+- For cross-project troubleshooting, first confirm whether `--project_id` matches the current permissions and target environment.
+- Write operations keep the confirmation prompt by default; re-evaluate whether to use `--yes` in automation scenarios.
+
+## Next Steps After Failure
+- If required parameters are missing, fall back to the smallest runnable command and fill them in (focus on `--mark_time_id`, `--project_id`, and `--marked_at`).
+- If the result after writing is not as expected, immediately read back the corresponding list/get interface for a before-and-after comparison.
+
+## Recommended Chaining
+- +list_project_mark_times -> +update_project_mark_time

package/skills/te-shared/SKILL.md

@@ -0,0 +1,115 @@
+---
+name: te-shared
+version: 1.0.0
+description: "TE CLI basics: authentication configuration, global parameters, error handling, and security constraints"
+metadata:
+  requires:
+    bins: ["ae-cli"]
+  cliHelp: "ae-cli --help"
+---
+
+# te-shared
+
+TE CLI (`ae-cli`) is the command-line tool for the ThinkingEngine data analysis platform, used by AI Agents and human users.
+
+## Authentication
+
+You must authenticate before use. Authentication priority:
+
+1. Environment variable `TE_TOKEN` (highest priority, suitable for CI/scripts)
+2. Cached token (`~/.ae-cli/tokens.json`, valid for 20 hours)
+3. macOS automatically extracts it from Chrome (macOS only)
+
+### Authentication Commands
+
+```bash
+# Automatic macOS authentication (extract token from Chrome)
+ae-cli auth login
+
+# Manually set token
+ae-cli auth set-token <token>
+
+# View authentication status
+ae-cli auth status
+
+# Log out
+ae-cli auth logout
+```
+
+### Multi-environment Support
+
+```bash
+# Specify host
+te-cli auth login --host ta-staging.example.com
+te-cli auth set-token <token> --host ta-staging.example.com
+
+# Configure default host
+te-cli config set defaultHost ta-staging.example.com
+```
+
+## Global Parameters
+
+All commands support the following global parameters:
+
+| Parameter | Description | Default |
+|------|------|--------|
+| `--host <host>` | TE instance address | defaultHost from config or ta.thinkingdata.cn |
+| `--format <json\|table>` | Output format | json |
+| `--jq <expr>` | jq filter expression | - |
+| `--dry-run` | Show the request only, do not execute it | false |
+| `--yes` | Skip confirmation for write operations | false |
+
+## Output Format
+
+### JSON (default)
+
+```json
+{
+  "ok": true,
+  "data": { ... }
+}
+```
+
+### Table
+
+```bash
+te-cli te_meta +list_events --project_id <YOUR_PROJECT_ID> --format table
+```
+
+### jq Filtering
+
+```bash
+te-cli te_meta +list_events --project_id <YOUR_PROJECT_ID> --jq '.'
+```
+
+## Error Handling
+
+Error output goes to stderr, in the following format:
+
+```json
+{
+  "ok": false,
+  "error": {
+    "type": "auth | api | validation | config",
+    "message": "...",
+    "hint": "..."
+  }
+}
+```
+
+Exit code: success `0`, error `1`.
+
+## Security Constraints
+
+- Commands with `risk: read` execute directly
+- Commands with `risk: write` require confirmation unless `--yes` is passed
+- Use `--dry-run` to preview the request that will be sent
+
+## Command Structure
+
+```bash
+te-cli <domain> +<command> [flags]
+te-cli api <METHOD> <PATH> [--params] [--data]
+```
+
+Domains: `te_analysis` (analysis), `te_audience` (audience), `te_meta` (metadata), `te_common` (common), `operation` (operations)