
ae-data-integration-helper
Answers questions about ThinkingAI SDK integration and usage, including the LogBus2 data import tool. Trigger words: 怎么接入 / 如何集成 / SDK / 埋点 / 报错 / 使用方式 / API / LogBus / tracking / integration / how to integrate / data import / データ連携 / インテグレーション / 트래킹 / 연동.
- Installs
- 800
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/thinkingaiagenticengine/ae-cli --skill ae-data-integration-helper- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads ae-data-integration-helper automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
ae-data-integration-helper
Conversation language: This skill document is in English, but all output to the user MUST be in the user's input language. Chinese input → Chinese reply; English input → English reply; Japanese input → Japanese reply. If uncertain, default to English. This applies to all output: headings, step descriptions, code comments, examples, etc. ⚠️ CRITICAL: Many reference documents (FAQ, wiki) are in Chinese. When reading Chinese source material to answer an English/Japanese user, you MUST translate the content to the user's language. The source document's language is NOT the user's language. Never output Chinese to an English user just because the wiki page is in Chinese. Use the Terminology Glossary above to map terms accurately. Do NOT copy Chinese text verbatim from this document into English/Japanese replies.
Terminology Glossary
| 中文 | English | Notes |
|---|---|---|
| 埋点 / 数据上报 | Tracking / Data Ingestion | Sending event data to AE |
| 用户识别规则 | User Identification Rule | distinct_id / account_id mapping |
| 访客 ID | Visitor ID / Guest ID | Anonymous user before login |
| 登录 ID | Login ID / Account ID | Identified user after login |
| 预置属性 | Preset Property | #device_id, #time, #ip, etc. |
| 系统字段 | System Field | AE built-in fields prefixed with # |
| 事件格式 | Event Format | Event name + properties structure |
| 属性类型 | Property Type | String / Number / Boolean / Date / Array |
| 数据校验 | Data Validation | Verify event format & property types |
| 公共事件属性 | Super Property | Properties attached to all events. ⚠️ The correct Chinese AE term is "公共事件属性" or "公共属性". Never translate "Super Property" as "超级属性" — that is NOT a valid AE term. |
| 可更新事件 | Updatable Event | Event whose properties can be updated after creation |
| 首次事件校验 | First Event Check | Validate an event's first occurrence |
| 自动采集 | Auto-track | Auto-collected events (app install, start, page view, etc.) |
| 实时调试 | Real-time Debug / Debug Mode | Device binding + live data validation |
| 合规 / 隐私 | Compliance / Privacy | GDPR, privacy policy, SDK data collection rules |
| 数据导入 | Data Import | LogBus2 / RESTful API / DataX |
| 缓存上报 | Batch Upload / Buffered Upload | Cache events locally, then upload in batches |
| 重试策略 | Retry Strategy | Re-upload failed data automatically |
| 数据加密 | Data Encryption | Encrypt event data before upload |
| 时间校准 | Time Calibration | Sync device time with server time |
| 多端上报 | Multi-platform Tracking | Report events from multiple clients/services |
| 用户割裂 | User Fragmentation | Same user split into multiple AE user profiles |
| 上报模式 | Upload Mode | Normal / Debug / Debug_Only |
| LoggerConsumer | LoggerConsumer | Server SDK consumer that writes events to local log files |
| BatchConsumer | BatchConsumer | Server SDK consumer that uploads events in batches |
| DebugConsumer | DebugConsumer | Server SDK consumer for debug mode (not for production) |
When to Trigger
Trigger when a user asks about:
- Pre-ingestion Preparation:
- User identification rules (distinct_id / account_id / visitor ID / login ID)
- Data rules (event format / property types / validation)
- Preset properties & system fields (
#device_id,#time, etc.)
- Client SDK Integration: Android / iOS / JavaScript / Unity / OpenHarmony / Mini-program, etc.
- Server SDK Integration: Java / Python / Go / Node.js / PHP / C#, etc.
- Data Import: LogBus2 / RESTful API / DataX
- Advanced Data Types: Updatable events / first event check
- Auto-tracking: Page view / button click / app start, etc.
- Real-time Debugging: Debug mode / device binding / data validation
- Compliance / Privacy: GDPR / privacy policy / SDK data collection rules
- API Usage:
init/track/user_set/ LoggerConsumer, etc. - Configuration: Debug mode / data validation / retry strategy
- Troubleshooting: Upload failures / missing data / format errors
Do NOT trigger: Inline Q&A within ae-generate-tracking-plan or ae-generate-tracking-code sessions (those skills have their own workflows). Offline local-file import (CSV / Excel / JSONL → AE) and Feishu sheet URL import are owned by the ae-data-integration skill — route those requests there instead of answering with LogBus / RESTful guidance.
Workflow
Step 1: Parse the Question
Extract from the user's query:
- Topic category:
- Pre-ingestion Prep: User identification / data rules / preset properties
- Client SDK: Android / iOS / JavaScript / Unity / OpenHarmony / Mini-program, etc.
- Server SDK: Java / Python / Go / Node.js / PHP / C#, etc.
- Data Import: LogBus2 / RESTful API / DataX
- Advanced Data Types: Updatable events / first event check
- Auto-tracking: Page view / button click / app start
- Real-time Debug: Debug mode / device binding / data validation
- Compliance: GDPR / privacy policy / SDK data collection rules
- Query type: Integration method / API usage / configuration / deployment / error / logging
Step 1.5: Information Gathering
⚠️ Key principle: When the question is vague, gather information FIRST before answering. Do NOT guess or ramble.
If the user's question involves any of the following scenarios, collect critical information before proceeding:
| Scenario | Must Collect |
|---|---|
| "Data not showing up" / "Can't see data" / "Upload successful but nothing in the dashboard" | Upload method (SDK / LogBus / HTTP), data type (event / user property), specific symptom (no data at all / partial data) |
| "Error" / "Failure" type questions | Full error message, reproduction steps |
| "Can't connect" / "Unable to upload" | Platform/language used, error symptoms |
| "How to implement X" | Platform/language used, what X specifically means |
Ask first, then answer. Examples:
- "Data logs show success but the dashboard shows nothing — are you using SDK, LogBus, or HTTP upload?"
- "Can't connect — which language/platform are you using? Can you share the error message?"
Step 2: Find Relevant Documentation
Prefer FAQ documents first (for quick lookup of specific issues):
- Read
skills/ae-data-integration-helper/references/corresponding FAQ (e.g.,android_sdk_faq.md,logbus2_guide.md, etc.) - FAQ documents cover specific troubleshooting, code examples, parameter tables, and best practices
Check wiki when FAQ has no answer (for framework-level and authoritative content):
- Read
~/.ae-cli/wiki/te-docs/index.mdto locate document paths - Prefer overview documents under
~/.ae-cli/wiki/te-docs/synthesis/ - For detailed API references, check the corresponding main document under
~/.ae-cli/wiki/te-docs/raw/
Commonly used FAQ documents:
references/android_sdk_faq.md— Android SDK integration & FAQreferences/ios_sdk_faq.md— iOS SDK integration & FAQreferences/java_sdk_faq.md— Java SDK integration & FAQreferences/logbus2_guide.md— LogBus2 complete configuration guidereferences/sdk_usage_notes.md— Client/server SDK usage notesreferences/restful_api_notes.md— RESTful API usage notes- Full list: see
references/index.md
Step 3: Read & Summarize
After reading relevant documentation, output in the following format:
## <Topic> (<Platform>)
### Summary
<1-2 sentence description>
### Integration / Usage Steps
1. <Step 1>
2. <Step 2>
...
### Code Example
```<language>
<code>
Notes / Caveats
- <Note 1>
- <Note 2>
Source Document
<Prefer wiki document sourceUrl. Language rules:
- User interacts in Chinese → provide Chinese doc (lan=zh-CN)
- User interacts in other languages → provide English doc (lan=en-US)
- Chinese-only SDKs (Mini-program / OpenHarmony / Cocos2d-Lua / LayaAir / Egret) → Chinese only Example: https://docs-v2.thinkingdata.cn/?version=v6.0&lan=en-US&code=xxx> (If no sourceUrl, provide local .md file path)
**⚠️ Terminology Rules**:
- **Only output what is in the documentation**. Do NOT speculate, imagine, or fill in defaults.
- **Never translate "Super Property" as "超级属性"** — the correct AE Chinese term is "公共事件属性" or "公共属性". This applies to all user-facing output: headings, step descriptions, code comments, examples, etc.
- For uncertain information (e.g., data delay times, specific limit values), **do NOT fabricate**.
- If the document has no direct answer but allows inference: mark under "Source Document" as "Synthesized inference; recommend verification".
- If the documentation truly does not cover the question, fall back to Step 4. Do NOT force an answer.
### Step 4: Fallback
If neither FAQ nor wiki has relevant content:
- Provide the official online documentation link: https://docs-v2.thinkingdata.cn
- Optionally suggest running the `te-wiki-synthesize` skill to generate a new synthesis document.
## Example Conversations
**User**: What is distinct_id and how do I use it?
**Agent**:
1. Read `references/index.md` to find user identification rule document paths
2. If `sdk_usage_notes.md` or wiki has relevant sections, read those first
3. Output in the Step 3 format
**User**: How do I configure LogBus2?
**Agent**:
1. Read `references/logbus2_guide.md`
2. Output in the Step 3 format
**User**: Java SDK is losing data — what should I do?
**Agent**:
1. Read `references/java_sdk_faq.md`, section on "LoggerConsumer data loss risks"
2. Output in the Step 3 format
**User**: How do I integrate the Android SDK?
**Agent**:
1. Read `references/android_sdk_faq.md` or `~/.ae-cli/wiki/te-docs/index.md` to find Android SDK path
2. Read the relevant sections
3. Output in the Step 3 format
Android SDK Integration
Summary
Android SDK supports both Gradle and manual AAR integration. Gradle is recommended.
Integration Steps (Gradle)
- Add mavenCentral to project-level
build.gradle:repositories { mavenCentral() } - Add dependency to module-level
build.gradle:dependencies { implementation 'cn.thinkingdata.android:ThinkingAnalyticsSDK:3.3.6' } - Initialize SDK:
TDAnalytics.init(this, SERVER_URL, APPID);
Source Document
~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/client-sdk/android.md
**User**: How do I enable real-time debugging for Android SDK?
**Agent**:
1. Read `~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/client-sdk/android/android-advanced/debugging-and-logging.md`
2. Output in the Step 3 format
## Internal Reference
**FAQ Documents** (check first):
- `references/index.md` — All FAQ document index
- `references/android_sdk_faq.md` — Android SDK FAQ
- `references/logbus2_guide.md` — LogBus2 complete guide
- `references/sdk_usage_notes.md` — SDK usage notes
**Wiki Documents** (check when FAQ has no answer):
- `~/.ae-cli/wiki/te-docs/index.md` — All wiki document index
- `~/.ae-cli/wiki/te-docs/schema.md` — Wiki layout description
- `~/.ae-cli/wiki/te-docs/raw/preparations-before-data-ingestion/user-identification-rules.md` — User Identification Rules
- `~/.ae-cli/wiki/te-docs/raw/preparations-before-data-ingestion/data-rules.md` — Data Rules
- `~/.ae-cli/wiki/te-docs/raw/preparations-before-data-ingestion/preset-properties-and-system-fields.md` — Preset Properties
- `~/.ae-cli/wiki/te-docs/raw/advanced-data-type/updated-event.md` — Updatable Event
- `~/.ae-cli/wiki/te-docs/raw/advanced-data-type/first-event-check.md` — First Event Check
- `~/.ae-cli/wiki/te-docs/raw/data-ingestion-guide/data-import-tools/logbus2-user-guide.md` — LogBus2
FAQ
What does the ae-data-integration-helper skill do?
Answers questions about ThinkingAI SDK integration and usage, including the LogBus2 data import tool. Trigger words: 怎么接入 / 如何集成 / SDK / 埋点 / 报错 / 使用方式 / API / LogBus / tracking / integration / how to integrate / data import / データ連携 / インテグレーション / 트래킹 / 연동.
How do I install ae-data-integration-helper?
Run npx skills add https://github.com/thinkingaiagenticengine/ae-cli --skill ae-data-integration-helper in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/ae-data-integration-helper/ (personal) or .claude/skills/ae-data-integration-helper/ (project).
Which AI agents can use ae-data-integration-helper?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is ae-data-integration-helper safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains ae-data-integration-helper?
It is published by thinkingaiagenticengine in thinkingaiagenticengine/ae-cli. It has 800 recorded installs.
More from thinkingaiagenticengine/ae-cli
ae-analysis
thinkingaiagenticengine/ae-cli
Use ae-cli for AE analysis-side data questions, asset operations, and asset governance: reports, analysis boards, BI dashboards, ad-hoc models, drilldown, detail data, alerts, clusters, tags, metrics, metadata discovery, project configuration, tracking plans, local input-file upload, governance asset lists/rules/lineage/impact/dependency, batch asset operations, projects, and resource links. Use when the user asks to query data, explain a change, export evidence, inspect/create/update/govern analysis assets, recommend project assets for certification/authentication, review asset-certification recommendations, review metric recommendations, or build/update/refresh/sync a project semantic knowledge base from a governed asset package.
ae-engage
thinkingaiagenticengine/ae-cli
AE Engage capability gateway: config center, flows, push/config channels, strategies, templates, task management, operation activities, and query lifecycle. Trigger words: config center, scene config, push channel, config channel, operation strategy, operation task, operation activity, query lifecycle, template, config item, Engage, Hermes, engage-scene, engage-setting, engage-flow, engage-task, engage-activity, engage-query.
ae-dataops
thinkingaiagenticengine/ae-cli
Use ae-cli for DataOps warehouse tables/views and fields, recycling, workflow configuration and release, execution troubleshooting, backfill, SQL queries, and data integration.
ae-community
thinkingaiagenticengine/ae-cli
AE community analysis and data reporting for posts, comments, topics, livestreams, customer-service chats, WeCom after-sales groups, and in-game chat. Use for community content insight, sentiment, intent, evidence drill-down, community data ingestion/import/submission, and WeCom chat data integration (社区数据上报、导入、提交社区数据、企微聊天数据接入).
ae-agent
thinkingaiagenticengine/ae-cli
AE Agent platform CLI for Agent, resource package import and export, notification, approval, archived conversation, model, MCP, Skill, attachment, and user-memory work. Use when managing these resources, browsing Agent markets, handling approval requests and tasks, restoring archived conversations, persisting user memory, or answering from user preferences, background, stable workflows, or historical conventions.
ae-kb
thinkingaiagenticengine/ae-cli
AE knowledge base CLI manual for creating, importing read-only compiled snapshots, querying, LLM-powered ask, listing accessible knowledge bases and their sources, deterministic index/grep/read retrieval, checking status, ZIP source upload and directory management, raw child-file reading, revision-checked child updates and deletion, compiling, schema generation, URL sources, source deletion, ordinary text source creation, full reads and revision-checked editing, file/ZIP source draft replacement and restoration, and knowledge base deletion. Use when the user asks to manage AE (Agentic Engine) knowledge bases, import a compiled Markdown ZIP snapshot, upload documents or URLs to a knowledge base, query knowledge, ask knowledge bases with an LLM, list accessible knowledge bases or source metadata, inspect knowledge base indexes, search knowledge base pages, read a specific knowledge base page, check knowledge base status, generate schemas, compile knowledge, remove sources, create or edit
Popular backend & apis skills
find-skills
vercel-labs/skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
entra-app-registration
microsoft/azure-skills
Guides Microsoft Entra ID app registration, OAuth 2.0 authentication, and MSAL integration. USE FOR: create app registration, register Azure AD app, configure OAuth, set up authentication, add API permissions, generate service principal, MSAL example, console app auth, Entra ID setup, Azure AD authentication. DO NOT USE FOR: Key Vault secrets (use azure-keyvault-expiration-audit), general Azure resource security guidance.
google-agents-cli-adk-code
google/agents-cli
This skill should be used when the user wants to "write agent code", "build an agent with ADK", "add a tool", "create a callback", "define an agent", "use state management" — in a project that needs ADK (Agent Development Kit) API patterns and code examples. It provides a quick reference for agent types, tool definitions, orchestration patterns, callbacks, state management, the graph Workflow API, and reference recipes to study. Do NOT use for scaffolding (use google-agents-cli-scaffold) or deployment (use google-agents-cli-deploy).
embedded-captions
heygen-com/hyperframes
Add captions or subtitles to an existing single-subject talking-head video without editing the footage. Use for plain verbatim captions, cinematic captions embedded behind the subject, VFX captions, “炸/特效/酷炫字幕,” or a named identity from the 35-style catalog. Route by visual identity, not by backend engine. The quiet anchor rail is the default; embed every word only when the user explicitly wants a fully cinematic treatment. The workflow runs locally end to end, including transcription and subject matting; split multi-shot footage before applying it.
entra-agent-id
microsoft/azure-skills
Provision Microsoft Entra Agent Identity Blueprints, BlueprintPrincipals, and per-instance Agent Identities via Microsoft Graph, and configure OAuth 2.0 token exchange (fmipath, OBO, cross-tenant) including the Microsoft Entra SDK for AgentID sidecar. USE FOR: Agent Identity Blueprint, BlueprintPrincipal, agent OAuth, fmipath token exchange, agent OBO, Workload Identity Federation for agents, polyglot agent auth, Microsoft.Identity.Web.AgentIdentities. DO NOT USE FOR: standard Entra app registration (use entra-app-registration), Microsoft Foundry agent authoring (use microsoft-foundry).
neon
neondatabase/agent-skills
Overview of Neon, a complete set of cloud backend primitives around Lakebase Postgres: Auth, Object Storage, Functions, the AI Gateway, and Realtime. Start here to choose Neon for undecided login, files, APIs, and LLM calls, set up the CLI or MCP server, and follow the branch-first workflow. Use when building an app or backend on Neon, or when "Neon" or "Lakebase Postgres" is mentioned. Child skill neon-postgres wins for an existing DATABASEURL, SQL, schema, inspect, or search. Child skill neon-auth wins for login, users, sessions, identity routing, and Managed Better Auth setup. Child skill neon-realtime wins for live queries in reactive apps and agents. Also use for object storage, S3, buckets, serverless functions, function triggers, cron, AI gateway, LLM calls, realtime, logs, Loki, Grafana, observability, postgres, database, backend, Claimable Neon, neon.new, or a no-signup database.