@clix-so/clix-agent-skills 0.1.3 → 0.1.5

package/skills/user-management/LICENSE.txt

@@ -0,0 +1,203 @@
+Copyright (c) 2026 Clix (https://clix.so/)
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright (c) 2026 Clix (https://clix.so/)
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/skills/user-management/SKILL.md

@@ -0,0 +1,114 @@
+---
+name: clix-user-management
+description:
+  Implements Clix user identification and user properties (setUserId,
+  removeUserId, setUserProperty/setUserProperties,
+  removeUserProperty/removeUserProperties) with safe schemas, logout best
+  practices, and campaign-ready personalization/audience usage. Use when the
+  user mentions login/logout, userId, user properties, personalization, or
+  audience targeting.
+---
+
+# Clix User Management
+
+Use this skill to help developers implement **Clix user identification** and
+**user properties** so campaigns can use `user.*` variables and audience
+filters, and so user identity is consistent across devices and sessions.
+
+## What the official docs guarantee (high-signal)
+
+- **Anonymous vs identified**: if no user ID is set, Clix treats the user as
+  anonymous; setting a user ID converts the anonymous user into an identified
+  user and links prior activity.
+- **Logout**: **do not** call `setUserId(null)` on logout; handle logout in app
+  logic only; when a different user logs in, call `setUserId(newUserId)` to
+  switch.
+- **User properties**: values are strings, numbers, or booleans; user operations
+  can throw—handle errors.
+
+## MCP-first (source of truth)
+
+If Clix MCP tools are available, treat them as the **source of truth**:
+
+- `clix-mcp-server:search_docs` for conceptual behavior and logout guidance
+- `clix-mcp-server:search_sdk` for exact SDK signatures per platform
+
+If MCP tools are not available, use the bundled references:
+
+- Contract + pitfalls → `references/user-management-contract.md`
+- Logout + switching rules → `references/logout-and-switching.md`
+- Property schema + PII → `references/property-schema.md`
+- Implementation patterns → `references/implementation-patterns.md`
+- Personalization + audience mapping →
+  `references/personalization-and-audience.md`
+- Debugging checklist → `references/debugging.md`
+
+## Workflow (copy + check off)
+
+```
+User management progress:
+- [ ] 1) Confirm platform(s) and auth model (anonymous browsing? login? shared devices?)
+- [ ] 2) Propose user plan (when setUserId/removeUserId, properties, logout policy)
+- [ ] 3) Validate plan (PII, property types, logout rules)
+- [ ] 4) Implement (platform-correct calls + error handling)
+- [ ] 5) Verify (switching works, properties appear, campaigns can target/personalize)
+```
+
+## 1) Confirm the minimum inputs
+
+Ask only what’s needed:
+
+- **Platform**: iOS / Android / React Native / Flutter
+- **Auth events**: where login success and logout happen in code
+- **User identifier**: what stable ID to use (prefer internal user id, not
+  email)
+- **PII policy**: what must never be stored as user properties
+- **Campaign goals**: personalization, audience filters, or both
+
+## 2) Propose a “User Plan” (before touching code)
+
+Return a compact table:
+
+- **user_id source**: where it comes from (auth response, local db)
+- **setUserId timing**: exact point (after login success / token saved)
+- **logout behavior**: explicitly “no call to setUserId(null)”
+- **properties**: key + type, required vs optional
+- **purpose**: personalization / audience / analytics
+
+## 3) Validate the plan (fast feedback loop)
+
+Create `user-plan.json` in `.clix/` (recommended) or project root.
+
+**For agents**: locate `scripts/validate-user-plan.sh` in the installed skill
+directory and run:
+
+```bash
+# From project root:
+bash <skill-dir>/scripts/validate-user-plan.sh .clix/user-plan.json
+# Or if in root:
+bash <skill-dir>/scripts/validate-user-plan.sh user-plan.json
+```
+
+If validation fails: fix the plan first, then implement.
+
+## 4) Implement (platform-correct)
+
+Use MCP to fetch the exact signatures per platform, then:
+
+- Place `setUserId(...)` **after** login/signup is confirmed.
+- On logout: **do nothing with Clix** (no `setUserId(null)`).
+- When switching users: call `setUserId(newUserId)` after the new login
+  succeeds.
+- Set user properties only from controlled sources; avoid free-text/PII.
+- Always handle errors (async calls can throw).
+
+## 5) Verify
+
+- Identity:
+  - Anonymous flow works without calling `setUserId`
+  - After login, `setUserId` is called once and stable
+  - Switching accounts updates the active profile
+- Properties:
+  - Properties are primitives (string/number/boolean) and consistent
+  - Campaign audiences can filter on them
+  - Messages can use `user.*` personalization

package/skills/user-management/references/debugging.md

@@ -0,0 +1,29 @@
+# Debugging User Management
+
+## Contents
+
+- Quick triage
+- Common causes
+- Verification checklist
+
+## Quick triage
+
+1. Confirm `Clix.initialize(...)` is called before user operations.
+2. Confirm `setUserId(...)` is called only after login success.
+3. Confirm logout does **not** call `setUserId(null)`.
+4. Confirm user properties are primitives and stable.
+
+## Common causes
+
+- **Not initialized**: calls before init completes.
+- **Wrong timing**: calling `setUserId` before auth success.
+- **Bad property values**: objects/arrays, inconsistent types.
+- **PII leakage**: sending email/phone/name.
+
+## Verification checklist
+
+- Add temporary logs around login success and user calls (remove after).
+- Verify in Clix dashboard:
+  - user id shows as expected
+  - properties appear and are filterable
+  - message templates can resolve `user.*`

package/skills/user-management/references/implementation-patterns.md

@@ -0,0 +1,37 @@
+# Implementation Patterns
+
+## Contents
+
+- When to call setUserId
+- When to remove user id
+- Property update patterns
+- Error handling
+
+## When to call setUserId
+
+Call `setUserId(userId)`:
+
+- after login/signup succeeds (not on button tap)
+- after you have a stable identifier (prefer internal user id)
+- ideally once per session change (dedupe repeated calls)
+
+## When to remove user id
+
+Prefer the docs-recommended logout behavior:
+
+- On logout: **do nothing with Clix**.
+
+Only use `removeUserId()` if you have a strong reason and you understand the
+impact on shared devices and re-engagement.
+
+## Property update patterns
+
+- Set properties from controlled sources (backend flags, billing state).
+- Use small, stable values (enums/known strings).
+- Avoid frequent writes in tight loops.
+
+## Error handling
+
+- Treat user management operations as potentially failing:
+  - wrap async calls in try/catch
+  - log enough context to debug (user id, property keys—not values if sensitive)

package/skills/user-management/references/logout-and-switching.md

@@ -0,0 +1,32 @@
+# Logout and User Switching
+
+## Contents
+
+- Golden rule
+- Recommended patterns
+- What to avoid
+
+## Golden rule
+
+**Do not call `setUserId(null)` on logout.**
+
+Instead:
+
+- On logout: do nothing with Clix (only clear your app session).
+- On next login: call `setUserId(newUserId)` to switch profiles.
+
+## Recommended patterns
+
+- **Login success boundary**:
+  - after auth succeeds (and you have a stable user id)
+  - after tokens/session are stored (if applicable)
+  - then call `setUserId(userId)`
+
+- **Shared device**:
+  - keep an internal notion of “current user”
+  - do not try to “reset” Clix user on logout
+
+## What to avoid
+
+- `setUserId(null)` or “clear user” calls on logout.
+- setting user ID based on unverified inputs (typed email in login form).

package/skills/user-management/references/personalization-and-audience.md

@@ -0,0 +1,34 @@
+# Personalization + Audience Mapping
+
+## Contents
+
+- How user properties are used
+- Personalization (`user.*`)
+- Audience filters
+- Common mistakes
+
+## How user properties are used
+
+User properties power:
+
+- **Message personalization** via `user.*`
+- **Audience targeting** (filters on user/custom attributes)
+
+## Personalization (`user.*`)
+
+Use `user.*` variables in templates to personalize message content and links.
+Missing values render as empty string.
+
+## Audience filters
+
+Audience builder can filter on:
+
+- user id
+- built-in attributes (like last session)
+- custom attributes (your user properties)
+
+## Common mistakes
+
+- Storing PII (email/phone/name) as user properties by default.
+- Sending inconsistent types for the same property (e.g., `"25"` vs `25`).
+- Renaming keys without migrating campaign filters.

package/skills/user-management/references/property-schema.md

@@ -0,0 +1,65 @@
+# User Property Schema + PII Guardrails
+
+## Contents
+
+- Naming rules
+- Allowed types
+- PII guardrails
+- User Plan template
+
+## Naming rules
+
+- **Property keys**: `snake_case` recommended.
+- Prefer stable keys that won’t be renamed every sprint.
+
+## Allowed types
+
+- `string`
+- `number`
+- `boolean`
+
+If you must send complex objects: stringify intentionally and document it.
+
+## PII guardrails
+
+Default stance: **do not store PII in user properties** unless explicitly
+approved.
+
+Common PII/sensitive values to avoid:
+
+- email, phone number, full name
+- free-text fields (notes, messages)
+- government IDs, payment card details
+
+Prefer stable internal IDs:
+
+- `user_id` (your system’s id) instead of email/phone
+
+## User Plan template
+
+Create `.clix/user-plan.json` (recommended) or `user-plan.json` in project root:
+
+```json
+{
+  "conventions": {
+    "property_key_case": "snake_case"
+  },
+  "pii": {
+    "allowed": [],
+    "blocked": ["email", "phone", "name", "free_text"]
+  },
+  "user_id": {
+    "source": "auth response",
+    "example": "user_12345"
+  },
+  "logout_policy": "do_not_set_user_id_null",
+  "properties": {
+    "subscription_tier": { "type": "string", "required": false },
+    "premium": { "type": "boolean", "required": false },
+    "age": { "type": "number", "required": false }
+  }
+}
+```
+
+**Note**: The validation script validates `logout_policy`, `user_id`, and
+`properties`. The `conventions` and `pii` fields are optional metadata.

package/skills/user-management/references/user-management-contract.md

@@ -0,0 +1,56 @@
+# Clix User Management Contract
+
+## Contents
+
+- Core concepts
+- SDK surface (conceptual)
+- User properties types
+- Platform notes
+- Pitfalls
+
+## Core concepts
+
+- **Anonymous user**: default when no user ID is set.
+- **Identified user**: after setting user ID; historical activity is linked.
+- **Multi-device**: user identity can be consistent across devices when using
+  the same user ID.
+
+## SDK surface (conceptual)
+
+- `setUserId(userId)`
+- `removeUserId()`
+- `setUserProperty(key, value)`
+- `setUserProperties(map)`
+- `removeUserProperty(key)`
+- `removeUserProperties(keys)`
+
+## User properties types
+
+Prefer JSON primitives:
+
+- **string**
+- **number**
+- **boolean**
+
+Avoid:
+
+- `null` (inconsistent behavior)
+- nested objects/arrays unless you intentionally stringify them
+- PII unless explicitly approved
+
+## Platform notes
+
+- **iOS**: async + sync APIs exist; async is recommended.
+- **Android**: suspend functions; internal device service maps user ID to a user
+  property on the device backend.
+- **React Native**: Promise-based APIs.
+- **Flutter**: async APIs; user property model infers type and stringifies
+  unsupported values.
+
+## Pitfalls
+
+- Calling `setUserId(null)` on logout (don’t).
+- Setting user ID before login is confirmed (causes wrong attribution).
+- Sending PII as user properties by default.
+- Using unstable identifiers (email/phone) as user ID when an internal ID
+  exists.

package/skills/user-management/scripts/validate-user-plan.sh

@@ -0,0 +1,92 @@
+#!/usr/bin/env bash
+#
+# Validate a Clix user management plan (user-plan.json).
+#
+# Usage:
+#   bash skills/user-management/scripts/validate-user-plan.sh path/to/user-plan.json
+#
+set -euo pipefail
+
+plan_path="${1:-}"
+if [[ -z "$plan_path" ]]; then
+  echo "Usage: bash skills/user-management/scripts/validate-user-plan.sh path/to/user-plan.json" >&2
+  exit 2
+fi
+
+if [[ ! -f "$plan_path" ]]; then
+  echo "Error: file not found: $plan_path" >&2
+  exit 2
+fi
+
+validate_with_python() {
+  python3 - "$plan_path" <<'PY'
+import json
+import re
+import sys
+
+path = sys.argv[1]
+snake = re.compile(r"^[a-z][a-z0-9_]*$")
+
+with open(path, "r", encoding="utf-8") as f:
+  data = json.load(f)
+
+errors = []
+
+logout_policy = data.get("logout_policy")
+if logout_policy not in (None, "do_not_set_user_id_null"):
+  errors.append("logout_policy must be 'do_not_set_user_id_null' if present")
+
+user_id = data.get("user_id")
+if not isinstance(user_id, dict):
+  errors.append("user_id must be an object")
+else:
+  src = user_id.get("source")
+  ex = user_id.get("example")
+  if not isinstance(src, str) or not src.strip():
+    errors.append("user_id.source must be a non-empty string")
+  if ex is not None and (not isinstance(ex, str) or not ex.strip()):
+    errors.append("user_id.example must be a non-empty string if present")
+
+props = data.get("properties")
+if not isinstance(props, dict) or not props:
+  errors.append("properties must be a non-empty object")
+else:
+  for key, spec in props.items():
+    if not isinstance(key, str) or not snake.match(key):
+      errors.append(f"properties key '{key}' must be snake_case")
+      continue
+    if not isinstance(spec, dict):
+      errors.append(f"properties['{key}'] must be an object")
+      continue
+    t = spec.get("type")
+    if t is None:
+      errors.append(f"properties['{key}'].type is required")
+    elif t not in ("string", "number", "boolean"):
+      errors.append(f"properties['{key}'].type must be one of: string, number, boolean")
+    req = spec.get("required")
+    if req is not None and not isinstance(req, bool):
+      errors.append(f"properties['{key}'].required must be boolean if present")
+
+if errors:
+  print("❌ user-plan validation failed:")
+  for e in errors:
+    print(f"- {e}")
+  sys.exit(1)
+
+print("✅ user-plan validation passed")
+PY
+}
+
+if command -v python3 >/dev/null 2>&1; then
+  validate_with_python
+  exit 0
+fi
+
+echo "Warning: python3 not found; only checking JSON validity with node if available." >&2
+if command -v node >/dev/null 2>&1; then
+  node -e "JSON.parse(require('fs').readFileSync(process.argv[1], 'utf8')); console.log('✅ JSON is valid');" "$plan_path"
+  exit 0
+fi
+
+echo "Error: neither python3 nor node found; cannot validate." >&2
+exit 2