clix-user-management

Manage Clix user identity and properties across mobile, web, and backend platforms.

5|Updated Dec 30, 2025
One-click install
npx skills add https://github.com/clix-so/skills --skill clix-user-management
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clix-user-management
Source: https://github.com/clix-so/skills/tree/main/skills/user-management
Command: npx skills add https://github.com/clix-so/skills --skill clix-user-management

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Implements Clix user identification and user properties to enable consistent identity across devices and campaigns, while enforcing safe schemas and logout best practices.

Core Features & Use Cases

  • Manage identity with setUserId / removeUserId across platforms and persist user properties for audience filters and personalization.
  • Support cross-device identity, logout handling, and robust property typing with PII guardrails.
  • Real-world Scenario: a user logs in on mobile, then switches devices; campaigns should consistently target using user.* attributes.

Quick Start

After authenticating a user, pass the stable userId to setUserId to start identity tracking.

Frequently Asked Questions about clix-user-management

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage user identity across mobile and web platforms consistently?

Maintain consistent user identity across platforms by passing a stable userId to setUserId after authentication, persisting user properties for audience targeting, and enforcing safe schemas.

What is the best way to handle user logout without breaking audience filters?

The recommended approach for user logout is to use removeUserId instead of setUserId(null), avoiding audience filter corruption and maintaining consistent user property governance across devices.

How do you enforce PII guardrails and property typing for user properties?

Enforce PII guardrails and robust property typing by validating user properties against a defined user plan, ensuring safe schemas are applied before wiring properties to personalization campaigns.

Can I use user properties for personalization and audience targeting across different devices?

Yes, you can wire user.* attributes to personalization and audience targeting campaigns across mobile, web, and backend contexts, ensuring persistent cross-device identity and consistent property governance.

Why should I avoid setUserId(null) when implementing a logout flow?

Avoid setUserId(null) in logout flows because it breaks identity tracking consistency; instead, use removeUserId to enforce safe schemas and maintain robust user property governance across platforms.