@clix-so/clix-agent-skills 0.1.7 → 0.1.8

package/README.md

@@ -16,9 +16,9 @@ you can install skills in different ways.
 
 ### Universal CLI (Recommended)
 
-For **Cursor**, **VS Code**, **Claude Code**, **OpenCode**, **Goose**, **GitHub
-Copilot**, **Amp**, and **Letta**, use our tool to install skills and configure
-the Clix MCP Server automatically:
+For Amp, Claude Code, Codex, Copilot, Cursor, Goose, Letta, OpenCode, and VS
+Code, we recommend using our installer to set up the skills and automatically
+configure the Clix MCP Server.
 
 #### Installation Modes
 
@@ -50,7 +50,7 @@ npx @clix-so/clix-agent-skills@latest install integration --client cursor --glob
 
 # Install all available skills at once (repo root)
 npx @clix-so/clix-agent-skills@latest install --all --client cursor
-# This will install: integration, event-tracking, user-management
+# This will install: integration, event-tracking, user-management, personalization
 
 # Install all available skills globally (system root)
 npx @clix-so/clix-agent-skills@latest install --all --client cursor --global
@@ -63,6 +63,9 @@ npx @clix-so/clix-agent-skills@latest install --all --client cursor --global
   practices and campaign-ready validation
 - **clix-user-management**: Implement `Clix.setUserId` + user properties with
   logout best practices, personalization (`user.*`), and audience targeting
+- **clix-personalization**: Author and debug personalization templates for
+  message content, deep links/URLs, and audience targeting rules (`user.*`,
+  `event.*`, `trigger.*`, `device.*`)
 
 **Supported Clients:**
 
@@ -101,6 +104,7 @@ Alternatively, you can install a single skill directly by running:
 /plugin install clix-integration@clix-agent-skills
 /plugin install clix-event-tracking@clix-agent-skills
 /plugin install clix-user-management@clix-agent-skills
+/plugin install clix-personalization@clix-agent-skills
 ```
 
 Remember to restart Claude Code after installation to load the new skills.

package/llms.txt

@@ -54,6 +54,24 @@ Integrates Clix Mobile SDK into iOS, Android, Flutter, and React Native projects
 
 ---
 
+## clix-personalization
+
+Helps developers author and debug Clix personalization templates (Liquid-style) for message content, deep links/URLs, and audience targeting. Use when the user mentions personalization variables, Liquid, templates, conditional logic, loops, filters, deep links, message logs, or when the user types `clix-personalization`.
+
+- [clix-personalization](https://raw.githubusercontent.com/clix-so/skills/refs/heads/main/skills/personalization/SKILL.md): Helps developers author and debug Clix personalization templates (Liquid-style) for message content, deep links/URLs, and audience targeting. Use when the user mentions personalization variables, Liquid, templates, conditional logic, loops, filters, deep links, message logs, or when the user types `clix-personalization`.
+
+### References
+
+- [Common Patterns (Reference)](https://raw.githubusercontent.com/clix-so/skills/refs/heads/main/skills/personalization/references/common-patterns.md): Reference documentation for personalization skill
+- [Debugging (Reference)](https://raw.githubusercontent.com/clix-so/skills/refs/heads/main/skills/personalization/references/debugging.md): Reference documentation for personalization skill
+- [Template Syntax (Reference)](https://raw.githubusercontent.com/clix-so/skills/refs/heads/main/skills/personalization/references/template-syntax.md): Reference documentation for personalization skill
+
+### Scripts
+
+- [Validate Template (Script)](https://raw.githubusercontent.com/clix-so/skills/refs/heads/main/skills/personalization/scripts/validate-template.sh): Utility script for personalization skill
+
+---
+
 ## clix-user-management
 
 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, audience targeting or when the user types `clix-user-management`.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@clix-so/clix-agent-skills",
-  "version": "0.1.7",
+  "version": "0.1.8",
   "description": "An open collection of agent skills for Clix.",
   "main": "dist/index.js",
   "bin": {

package/skills/personalization/LICENSE.txt

@@ -0,0 +1,204 @@
+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/personalization/SKILL.md

@@ -0,0 +1,128 @@
+---
+name: clix-personalization
+description:
+  Helps developers author and debug Clix personalization templates
+  (Liquid-style) for message content, deep links/URLs, and audience targeting.
+  Use when the user mentions personalization variables, Liquid, templates,
+  conditional logic, loops, filters, deep links, message logs, or when the user
+  types `clix-personalization`.
+---
+
+# Clix Personalization
+
+Use this skill to help developers write **personalized Clix campaigns** using
+template-based variables and light logic in:
+
+- **Message content** (title, body, subtitle)
+- **Links** (dynamic URL or deep link params)
+- **Audience targeting** (conditional include/exclude rules)
+
+## What the official docs guarantee (high-signal)
+
+- **Data namespaces**:
+  - `user.*` (user traits/properties)
+  - `event.*` (event payload properties)
+  - `trigger.*` (custom properties passed via API-trigger)
+  - Device/system vars: `device.id`, `device.platform`, `device.locale`,
+    `device.language`, `device.timezone`, plus `user.id`, `event.name`
+- **Missing variables** render as an **empty string**.
+- **Output**: print values with `{{ ... }}`.
+- **Conditionals**: `{% if %}`, `{% else %}`, `{% endif %}` with operators
+  `== != > < >= <= and or not`. Invalid conditions evaluate to `false`.
+- **Loops**: `{% for x in y %}` / `{% endfor %}` (use guards for empty lists).
+- **Filters**: `upcase`, `downcase`, `capitalize`, `default`, `join`, `split`,
+  `escape`, `strip`, `replace` (chain with `|`).
+- **Errors**: template rendering errors show up in **Message Logs**.
+
+## MCP-first (source of truth)
+
+If the Clix MCP tools are available, treat them as the source of truth:
+
+- `clix-mcp-server:search_docs` for personalization behavior and supported
+  syntax
+
+If MCP tools are not available, use the bundled references in `references/`.
+
+## Workflow (copy + check off)
+
+```
+Personalization progress:
+- [ ] 1) Identify where the template runs (message / URL / audience rule)
+- [ ] 2) Identify trigger type (event-triggered vs API-triggered)
+- [ ] 3) Confirm available inputs (user.*, event.*, trigger.*, device.*)
+- [ ] 4) Draft templates with guards/defaults
+- [ ] 5) Validate template structure (balance tags, avoid missing vars)
+- [ ] 6) Verify in Clix (preview/test payloads, check Message Logs)
+```
+
+## 1) Confirm the minimum inputs
+
+Ask only what’s needed:
+
+- **Where used**: title/body/subtitle vs URL/deep link vs audience targeting
+  rule
+- **Campaign trigger**:
+  - Event-triggered → `event.*` is available
+  - API-triggered → `trigger.*` is available
+- **Inputs**:
+  - Which `user.*` properties are set by the app
+  - Which `event.*` / `trigger.*` properties are passed (include example
+    payload)
+- **Fallback policy**: what to show when data is missing (default strings,
+  guards)
+
+## 2) Produce a “Template Plan” (before tweaking lots of templates)
+
+Return a compact table the user can approve:
+
+- **field** (title/body/url/audience)
+- **template** (Liquid)
+- **required variables** (and their source: user/event/trigger/device)
+- **fallbacks** (default filter and/or conditional guards)
+- **example payload** + **expected rendered output**
+
+## 3) Authoring guidelines (what to do by default)
+
+- Prefer **simple variables + `default`** over complex branching.
+- Add **guards** for optional data and for arrays (`size > 0`) before looping.
+- Prefer **pre-formatted** properties from your app (e.g., `"7.4 miles"`,
+  `"38m 40s"`) instead of formatting inside templates.
+- Keep logic minimal; complex branching belongs in the app or segmentation
+  setup.
+
+## 4) Validation (fast feedback loop)
+
+If you have a template file (recommended for review), run:
+
+```bash
+bash <skill-dir>/scripts/validate-template.sh path/to/template.liquid
+```
+
+This script does lightweight checks (matching `{% if %}`/`{% endif %}`,
+`{% for %}`/`{% endfor %}`, and brace balancing). It can’t guarantee the
+variables exist — you still need a payload + console verification.
+
+## 5) Verification checklist
+
+- **Missing data**: does the template still read well with empty strings?
+- **Trigger type**: API triggers use `trigger.*` (not `event.*`).
+- **Message Logs**: check rendering errors and fix syntax issues first.
+- **Upstream data**:
+  - If `user.*` is missing → fix user property setting (see
+    `clix-user-management`)
+  - If `event.*` is missing → fix event tracking payload (see
+    `clix-event-tracking`)
+
+## Progressive Disclosure
+
+- **Level 1**: This `SKILL.md` (always loaded)
+- **Level 2**: `references/` (load when writing/debugging templates)
+- **Level 3**: `scripts/` (execute directly, do not load into context)
+
+## References
+
+- `references/template-syntax.md` - Variables, output, conditionals, loops,
+  filters
+- `references/common-patterns.md` - Copy/paste patterns for messages + URLs +
+  guards
+- `references/debugging.md` - Troubleshooting missing variables and Message Logs

package/skills/personalization/references/common-patterns.md

@@ -0,0 +1,69 @@
+# Common Personalization Patterns (Reference)
+
+Copy/paste starting points for Clix templates. Prefer simple templates with
+guards/defaults.
+
+## Welcome / fallback-safe greeting
+
+```liquid
+Hi {{ user.username | default: "there" }},
+```
+
+## Dynamic message body (event-triggered)
+
+```liquid
+Hi {{ user.username | default: "Runner" }},
+you ran {{ event.distance | default: "?" }} miles in {{ event.elapsedTime | default: "?" }} seconds.
+```
+
+## Dynamic deep link / URL (event-triggered)
+
+```liquid
+myapp://run/summary?distance={{ event.distance }}&time={{ event.elapsedTime }}
+```
+
+Tip: If a value may contain spaces or special characters, prefer passing a
+pre-encoded string from your app (or keep the template value simple).
+
+## API-triggered promo (trigger.\*)
+
+```liquid
+🎉 {{ trigger.promotion | default: "A new promotion" }} is here!
+Get {{ trigger.discount | default: "a discount" }} off now!
+```
+
+## Conditional title by threshold
+
+```liquid
+{% if event.distance >= 10 %}
+Long run completed!
+{% else %}
+Good run today!
+{% endif %}
+```
+
+## Nested conditions (keep minimal)
+
+```liquid
+{% if user.tier == "pro" %}
+Pro stats updated successfully.
+{% else %}
+{% if event.elapsedTime > 3600 %}
+You ran for more than an hour! Great job!
+{% else %}
+New record saved.
+{% endif %}
+{% endif %}
+```
+
+## Looping over an array with a guard
+
+```liquid
+{% if user.badges and user.badges.size > 0 %}
+{% for badge in user.badges %}
+- {{ badge }}
+{% endfor %}
+{% else %}
+No badges yet.
+{% endif %}
+```

package/skills/personalization/references/debugging.md

@@ -0,0 +1,89 @@
+# Debugging Personalization (Reference)
+
+This guide helps you troubleshoot when a personalized message renders
+unexpectedly.
+
+## First principles (what the renderer does)
+
+- Unknown / missing variables render as an **empty string**.
+- Invalid conditions evaluate to `false`.
+- Template rendering errors (syntax issues) surface in **Message Logs**.
+
+## Quick checklist
+
+- **Are you using the right namespace?**
+  - Event-triggered campaign → use `event.*`
+  - API-triggered campaign → use `trigger.*`
+  - User traits/properties → use `user.*`
+- **Is the variable actually set upstream?**
+  - `user.*` comes from your app calling user property APIs.
+  - `event.*` comes from the event payload you track.
+  - `trigger.*` comes from properties in the API trigger request.
+- **Is the template resilient to missing data?**
+  - Add `| default: "..."` for strings.
+  - Wrap optional blocks in `{% if ... %}` guards.
+- **Are you looping safely?**
+  - Guard with `collection and collection.size > 0` before `{% for %}`.
+
+## Common failure modes
+
+### 1) Blank values
+
+Symptoms:
+
+- Output is missing where you expected text.
+
+Causes:
+
+- Variable doesn’t exist for that user/campaign trigger.
+
+Fix:
+
+- Use `default` for output values:
+
+```liquid
+{{ user.username | default: "Guest" }}
+```
+
+### 2) Conditional branch never runs
+
+Symptoms:
+
+- Always hits the `{% else %}` branch.
+
+Causes:
+
+- `event.*` is missing (or you should be using `trigger.*`).
+- Value is not the type you expect (e.g., string vs number).
+
+Fix:
+
+- Verify trigger type and payload shape.
+- Keep comparisons simple and ensure the property is sent as a number when you
+  compare numerically.
+
+### 3) Syntax error / rendering error
+
+Symptoms:
+
+- Message fails to render or shows an error in logs.
+
+Causes:
+
+- Missing `{% endif %}` / `{% endfor %}`
+- Unbalanced `{{` / `}}` or `{%` / `%}`
+
+Fix:
+
+- Check **Message Logs** first.
+- Validate the template structure locally:
+
+```bash
+bash <skill-dir>/scripts/validate-template.sh path/to/template.liquid
+```
+
+## When to escalate (data issue vs template issue)
+
+- If **defaults/guards** fix it → template issue.
+- If values are always blank across many users → upstream tracking/user-property
+  issue (fix app instrumentation).

package/skills/personalization/references/template-syntax.md

@@ -0,0 +1,113 @@
+# Personalization Template Syntax (Reference)
+
+This reference summarizes the personalization syntax supported by Clix
+templates.
+
+## Data namespaces
+
+- `user.*`: user properties (traits) you capture about a user
+  - Examples: `user.username`, `user.tier`
+- `event.*`: properties from the triggering event (event-triggered campaigns)
+  - Examples: `event.distance`, `event.elapsedTime`
+- `trigger.*`: custom properties passed via API trigger (API-triggered
+  campaigns)
+  - Examples: `trigger.promotion`, `trigger.discount`
+
+Missing or undefined variables render as an **empty string**.
+
+## Device and system variables
+
+Clix templates also support device and environment variables:
+
+- `device.id`
+- `device.platform` (`IOS` or `ANDROID`)
+- `device.locale`
+- `device.language`
+- `device.timezone`
+- `user.id` (project user id)
+- `event.name` (event name)
+
+## Output variables
+
+Print a value:
+
+```liquid
+{{ user.username }}
+```
+
+Nested / bracket access (useful when the key is not a valid identifier):
+
+```liquid
+{{ event["distance"] }}
+```
+
+## Conditionals
+
+Use `{% if %}`, `{% else %}`, `{% endif %}` blocks.
+
+Supported operators:
+
+- `==`, `!=`, `>`, `<`, `>=`, `<=`
+- `and`, `or`, `not`
+
+Example:
+
+```liquid
+{% if event.distance >= 10 %}
+Amazing! You completed a long run today.
+{% else %}
+Nice work! Keep it up!
+{% endif %}
+```
+
+Notes:
+
+- Unknown variables render as empty strings.
+- Invalid conditions evaluate to `false`.
+
+## Loops
+
+Iterate over arrays with `{% for %}` / `{% endfor %}`:
+
+```liquid
+{% for badge in user.badges %}
+- {{ badge }}
+{% endfor %}
+```
+
+Guard empty collections:
+
+```liquid
+{% if user.badges and user.badges.size > 0 %}
+{% for badge in user.badges %}
+{{ badge }}
+{% endfor %}
+{% else %}
+No badges yet.
+{% endif %}
+```
+
+## Filters
+
+Filters transform values inside `{{ ... }}` blocks and can be chained with `|`.
+
+Supported filters:
+
+- `upcase` / `downcase`
+- `capitalize`
+- `default`
+- `join`
+- `split`
+- `escape`
+- `strip`
+- `replace`
+
+Examples:
+
+```liquid
+Hi {{ user.username | default: "Guest" }}
+```
+
+```liquid
+{{ user.username | default: "Guest" | upcase }}
+```

package/skills/personalization/scripts/validate-template.sh

@@ -0,0 +1,134 @@
+#!/usr/bin/env bash
+set -euo pipefail
+
+usage() {
+  cat <<'EOF'
+Validate a Clix personalization template (Liquid-style) with lightweight checks.
+
+Usage:
+  validate-template.sh <template-file>
+
+Checks:
+  - Balanced {{ ... }} and {% ... %} delimiters
+  - Properly nested {% if %}/{% endif %} and {% for %}/{% endfor %} blocks
+
+Notes:
+  - This is a best-effort validator; it cannot guarantee that variables exist.
+  - If Clix shows a rendering error, always trust Message Logs as the source of truth.
+EOF
+}
+
+if [[ "${1:-}" == "-h" || "${1:-}" == "--help" || "${1:-}" == "" ]]; then
+  usage
+  exit 0
+fi
+
+file="$1"
+
+if [[ ! -f "$file" ]]; then
+  echo "Error: file not found: $file" >&2
+  exit 2
+fi
+
+errors=0
+
+echo "Validating: $file"
+
+brace_counts="$(
+  awk '
+    {
+      c_open_curly += gsub(/\{\{/, "&");
+      c_close_curly += gsub(/\}\}/, "&");
+      c_open_tag += gsub(/\{%/, "&");
+      c_close_tag += gsub(/%\}/, "&");
+    }
+    END {
+      printf("%d %d %d %d\n", c_open_curly, c_close_curly, c_open_tag, c_close_tag);
+    }
+  ' "$file"
+)"
+
+read -r open_curly close_curly open_tag close_tag <<<"$brace_counts"
+
+if [[ "$open_curly" -ne "$close_curly" ]]; then
+  echo "Error: unbalanced mustache braces: '{{'=$open_curly vs '}}'=$close_curly" >&2
+  errors=$((errors + 1))
+fi
+
+if [[ "$open_tag" -ne "$close_tag" ]]; then
+  echo "Error: unbalanced tag braces: '{%'=$open_tag vs '%}'=$close_tag" >&2
+  errors=$((errors + 1))
+fi
+
+awk_exit=0
+awk '
+  function trim(s) { sub(/^[ \t\r\n]+/, "", s); sub(/[ \t\r\n]+$/, "", s); return s }
+  function push(x) { stack[++sp] = x }
+  function top() { return stack[sp] }
+  function pop() { if (sp > 0) return stack[sp--]; return "" }
+
+  BEGIN { sp = 0; errors = 0 }
+
+  {
+    line = $0
+    while (match(line, /\{%[ \t]*[^%]*%\}/)) {
+      tag = substr(line, RSTART, RLENGTH)
+      inner = tag
+      gsub(/^\{%[ \t]*/, "", inner)
+      gsub(/[ \t]*%\}$/, "", inner)
+      inner = trim(inner)
+
+      # Tag name is first token.
+      split(inner, parts, /[ \t]+/)
+      name = parts[1]
+
+      if (name == "if") {
+        push("if")
+      } else if (name == "for") {
+        push("for")
+      } else if (name == "endif") {
+        if (top() != "if") {
+          printf("Error: found endif but top of stack is '%s'\n", top()) > "/dev/stderr"
+          errors++
+        } else {
+          pop()
+        }
+      } else if (name == "endfor") {
+        if (top() != "for") {
+          printf("Error: found endfor but top of stack is '%s'\n", top()) > "/dev/stderr"
+          errors++
+        } else {
+          pop()
+        }
+      } else if (name == "else" || name == "elsif") {
+        if (top() != "if") {
+          printf("Error: found %s outside of if block\n", name) > "/dev/stderr"
+          errors++
+        }
+      }
+
+      # Move forward in line after the matched tag.
+      line = substr(line, RSTART + RLENGTH)
+    }
+  }
+
+  END {
+    if (sp > 0) {
+      printf("Error: unclosed blocks remaining on stack (count=%d)\n", sp) > "/dev/stderr"
+      errors++
+    }
+    exit(errors > 0 ? 1 : 0)
+  }
+' "$file" || awk_exit=$?
+
+if [[ "$awk_exit" -ne 0 ]]; then
+  errors=$((errors + 1))
+fi
+
+if [[ "$errors" -ne 0 ]]; then
+  echo "❌ Validation failed ($errors issue(s))." >&2
+  exit 1
+fi
+
+echo "✅ Template structure looks OK."
+