← ClaudeAtlas

rudder-ai-events-verifylisted

Verifies RudderStack AI events locally and checks a move from existing RudderStack events: validates captures against the v0.4 schema, joins, switches and legacy events. Use when testing AI events, comparing old and new tracking, or when AI or MCP events look wrong or missing.
rudderlabs/rudder-agent-skills · ★ 19 · AI & Automation · score 77
Install: claude install-skill rudderlabs/rudder-agent-skills
# RudderStack AI Events Verification Proves the instrumentation sends what `ai-events.md` promises, before any real traffic. Default checks run offline: a recorder or mock RudderStack client, a mock model, no provider keys. Verification is not optional: it runs, and passes, before a commit or PR is proposed. If the user commits first, say plainly that verify has not run. The checker (`check`, `what-changes`), the recorders and both schemas ship with the SDKs, `@rudderstack/ai` / `rudderstack-ai` 0.8.0 or later and `ai-sdk-go` v0.4.0 or later (`cmd/aicheck` v0.2.0); this skill adds the mock data plane and model server (`scripts/mock_server.py`, Python 3) and the procedures and checklist in `references/verification.md`. The 0.8.0 checkers accept 0.3.0 and 0.4.0 captures; v0.4 events must carry 0.4.0 fields only when the plan pins a v0.4 SDK. For an app on an older SDK, run the latest checker from scratch and, in tests, import its `Recorder` from that scratch install. **Stacked delivery.** When the plan splits the work into several PRs (`## Files to change`), verify the surfaces instrumented up to the PR at hand, with every check below; report the plan's later surfaces as `n/a (later PR)`. The last PR's run covers the whole plan. With `server_dependency`, the backend PR lands first; browser verification drives that backend and combines both captures to check joins and the consumed switch. **Migration or new install.** When the plan lists legacy events (the app already sends