ae-migrate-tracking-code — Claude Code skill for analytics migration
ae-migrate-tracking-code moves existing Firebase, Amplitude, Mixpanel, Sensors Data, or GA4 tracking calls to the AE SDK. Choose a full switch or keep the old SDK and send events to both.
no license 401 installs ★ 23 updated 2026-11-06
npx skills add ThinkingAIAgenticEngine/ae-cli --skill ae-migrate-tracking-code -a claude-codeWhat ae-migrate-tracking-code does
The skill scans project code for calls to supported analytics SDKs and guides their move to AE. Providers include Firebase Analytics, Amplitude, Sensors Data, Mixpanel, and Google Analytics 4, with a separate adapter for each. You can replace the existing calls or add AE tracking beside them.
Plan creation is handed to ae-generate-tracking-plan; code insertion goes to ae-generate-tracking-code. The skill needs existing tracking code in the project, not just product descriptions. Historical data imports into AE fall outside its scope, so old records require a separate migration process.
What it helps with
- move Firebase Analytics calls to the AE SDK
- replace Amplitude event calls with AE tracking
- send events to AE while retaining the current SDK
- map existing analytics calls into a tracking plan
Example prompts for the agent
- Move the project's existing Firebase Analytics events to the AE SDK.
- Add AE event tracking alongside Mixpanel.
- Find GA4 calls in the project and prepare their migration to AE.
How to install ae-migrate-tracking-code
1Skills CLI (Vercel)
npx skills add ThinkingAIAgenticEngine/ae-cli --skill ae-migrate-tracking-code -a claude-code2Manually: put the files in place
~/.claude/skills/ae-migrate-tracking-code/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/ae-migrate-tracking-code/
1Skills CLI (Vercel)
npx skills add ThinkingAIAgenticEngine/ae-cli --skill ae-migrate-tracking-code -a codex2Manually: put the files in place
.agents/skills/ae-migrate-tracking-code/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add ThinkingAIAgenticEngine/ae-cli --skill ae-migrate-tracking-code -a cursor2Manually: put the files in place
.cursor/skills/ae-migrate-tracking-code/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install ThinkingAIAgenticEngine/ae-cli skills/ae-migrate-tracking-code2Manually: put the files in place
.github/skills/ae-migrate-tracking-code/SKILL.md1Skills CLI (Vercel)
npx skills add ThinkingAIAgenticEngine/ae-cli --skill ae-migrate-tracking-code -a gemini-cli2Platform CLI
gemini skills install https://github.com/ThinkingAIAgenticEngine/ae-cli --path skills/ae-migrate-tracking-codeManually: put the files in place
.devin/skills/ae-migrate-tracking-code/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add ThinkingAIAgenticEngine/ae-cli --skill ae-migrate-tracking-code -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about ae-migrate-tracking-code
How do I install ae-migrate-tracking-code in Claude Code?
Run npx skills add ThinkingAIAgenticEngine/ae-cli --skill ae-migrate-tracking-code -a claude-code.
What does ae-migrate-tracking-code do?
It finds calls to supported third-party analytics SDKs in project code and helps move them to AE, either replacing the old calls or adding parallel tracking.
Can it import historical analytics data into AE?
No. It handles live SDK calls in code; historical data import is outside its scope.