from agent-assistant50
Patterns and best-practices for implementing Segment (Analytics.js and server-side) tracking, event schema design, and avoiding common anti-patterns.
Provides concrete patterns for integrating Segment's Analytics.js on the client and @segment/analytics-node on the server, plus guidance for designing tracking plans and avoiding common mistakes. Includes practical recommendations on event naming, identify/anonymous ID handling, batching non-blocking server calls, and where to enforce validation.
Use this skill when building or auditing analytics/tracking implementations that rely on Segment as the CDP—especially when you need consistent event schemas, safe server-side ingestion, or to fix flaky client-side identity merges. Helpful during onboarding of analytics engineers, instrumentation sprints, or when migrating tracking to a CDP-backed architecture.
Likely useful for agents that perform devops/engineering assistant tasks (Code-writing agents like Copilot/Codex/Gemini Code) and for QA/analytics reviewers who validate event schemas.
Segment CDP skill is a documentation-only skill with no scripts. It covers Analytics.js browser integration, server-side tracking with Node.js, and tracking plan design, but all sections are shallow stubs. The anti-patterns are just headers with no explanations, and the Sharp Edges table is entirely placeholder content (every row says 'Issue' / 'See docs'). Provides minimal actionable value despite addressing a genuinely useful topic.
Likely auto-generated/vibeship skill with no real substance. All content is skeletal. Not malicious, but also not useful in current form.
