About segment-cdp
Segment CDP is a skill for work involving Segment Customer Data Platform and its tracking practices. It covers Analytics.js, server-side tracking, tracking plans, identity resolution, destinations, and data governance.
Key features
- 01Analytics.js and server-side tracking guidance
- 02Tracking plans with Protocols
- 03Identity resolution patterns
- 04Destination configuration
- 05Data governance practices
Use cases
- 01Planning customer event tracking
- 02Configuring event data routing
- 03Reviewing identity resolution approaches
- 04Establishing tracking governance
Install
Copy the command and run it in a terminal.
npx skills add https:/ / github.com/ sickn33/ agentic-awesome-skills --skill segment-cdpAfter installing, type/segment-cdpin Claude Code to confirm it loaded.
Bundled filesreferences/detailed-guide.md
Details
From the project READMESegment CDP
Expert patterns for Segment Customer Data Platform including Analytics.js, server-side tracking, tracking plans with Protocols, identity resolution, destinations configuration, and data governance best practices.
Detailed Guide
Read the detailed guide before executing this skill. It retains the complete procedure and reference material. Treat its safety, prerequisites, and validation requirements as mandatory. For focused work, load the relevant sections; for end-to-end work, read the guide completely.
When to Use
- User mentions or implies: segment
- User mentions or implies: analytics.js
- User mentions or implies: customer data platform
- User mentions or implies: cdp
- User mentions or implies: tracking plan
- User mentions or implies: event tracking
- User mentions or implies: identify track page
- User mentions or implies: data routing
Example
User request:
Use @segment-cdp for this task: Expert patterns for Segment Customer Data Platform including Analytics.js, server-side tracking, tracking plans with Protocols, identity resolution, destinations configuration, and data governance best practices.
Limitations
- Use this skill only when the task clearly matches the scope described above.
- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.