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

package/README.md

@@ -1,7 +1,7 @@
 # Agent Skills for Clix
 
 [![npm version](https://img.shields.io/npm/v/%40clix-so%2Fclix-agent-skills.svg?logo=npm&label=npm)](https://www.npmjs.com/package/@clix-so/clix-agent-skills)
-[![npm downloads](https://img.shields.io/npm/dm/%40clix-so%2Fclix-agent-skills.svg)](https://www.npmjs.com/package/@clix-so/clix-agent-skills)
+[![npm downloads](https://img.shields.io/npm/d18m/%40clix-so%2Fclix-agent-skills.svg)](https://www.npmjs.com/package/@clix-so/clix-agent-skills)
 
 This repository contains a collection of **Agent Skills for Clix**. Each skill
 is a self-contained package that can be loaded and executed by AI clients.
@@ -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, api-triggered-campaigns
 
 # Install all available skills globally (system root)
 npx @clix-so/clix-agent-skills@latest install --all --client cursor --global
@@ -58,11 +58,18 @@ npx @clix-so/clix-agent-skills@latest install --all --client cursor --global
 
 ### Available Skills
 
-- **clix-integration**: Integrate Clix Mobile SDK and MCP server setup
+- **clix-integration**: Seamlessly integrate Clix Mobile SDK to your mobile
+  application with Clix MCP Server
 - **clix-event-tracking**: Implement `Clix.trackEvent` with naming/schema best
   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.*`)
+- **clix-api-triggered-campaigns**: Configure API-triggered campaigns in the
+  console and trigger them from your backend with safe auth, dynamic filters
+  (`trigger.*`), and personalization patterns
 
 **Supported Clients:**
 
@@ -101,6 +108,8 @@ 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
+/plugin install clix-api-triggered-campaigns@clix-agent-skills
 ```
 
 Remember to restart Claude Code after installation to load the new skills.

package/dist/bin/commands/install.js

@@ -120,11 +120,13 @@ async function installSkill(skillName, options) {
         throw error;
     }
     // 4. MCP Configuration (always global/system root)
-    try {
-        await (0, mcp_1.configureMCP)(options.client);
-    }
-    catch (error) {
-        console.warn(chalk_1.default.yellow(`MCP Configuration warning: ${getErrorMessage(error)}`));
+    if (!options.skipMCPConfig) {
+        try {
+            await (0, mcp_1.configureMCP)(options.client);
+        }
+        catch (error) {
+            console.warn(chalk_1.default.yellow(`MCP Configuration warning: ${getErrorMessage(error)}`));
+        }
     }
     console.log(`\n${chalk_1.default.green("✔")} Skill ${chalk_1.default.bold(skillName)} is ready to use!`);
     console.log(`  - Docs: ${path_1.default.join(destPath, "SKILL.md")}`);
@@ -170,7 +172,8 @@ async function installAllSkills(options) {
     let failCount = 0;
     for (const skillName of skills) {
         try {
-            await installSkill(skillName, options);
+            // Avoid configuring MCP once per skill. We'll do it once at the end.
+            await installSkill(skillName, { ...options, skipMCPConfig: true });
             successCount++;
         }
         catch (error) {
@@ -178,6 +181,15 @@ async function installAllSkills(options) {
             failCount++;
         }
     }
+    // Configure MCP once per `--all` run (always global/system root)
+    if (successCount > 0) {
+        try {
+            await (0, mcp_1.configureMCP)(options.client);
+        }
+        catch (error) {
+            console.warn(chalk_1.default.yellow(`MCP Configuration warning: ${getErrorMessage(error)}`));
+        }
+    }
     console.log();
     if (failCount === 0) {
         console.log(chalk_1.default.green(`\n✔ Successfully installed all ${chalk_1.default.bold(successCount)} skill(s)!`));

package/dist/bin/utils/mcp.js

@@ -159,7 +159,13 @@ function getClientConfig(client) {
                 format: "json",
             };
         }
+        // GitHub Copilot runs inside VS Code, so its MCP configuration lives in VS Code's MCP config.
+        // We accept `github` / `copilot` as aliases and write to the same file as `vscode`.
         case "vscode":
+        case "github":
+        case "copilot":
+        case "github-copilot":
+        case "github copilot":
             return {
                 path: path_1.default.join(home, ".vscode", "mcp.json"),
                 configKey: "mcpServers",

package/llms.txt

@@ -7,6 +7,32 @@ Each entry includes the file path, type, and description for semantic search.
 
 ---
 
+## clix-api-triggered-campaigns
+
+Helps developers configure API-triggered campaigns in the Clix console and trigger them from backend services with safe auth, payload schemas, dynamic audience filters (trigger.*), and personalization best practices. Use when the user mentions transactional notifications, backend-triggered sends, campaign_id trigger APIs, or "API-triggered campaigns".
+
+- [clix-api-triggered-campaigns](https://raw.githubusercontent.com/clix-so/skills/refs/heads/main/skills/api-triggered-campaigns/SKILL.md): Helps developers configure API-triggered campaigns in the Clix console and trigger them from backend services with safe auth, payload schemas, dynamic audience filters (trigger.*), and personalization best practices. Use when the user mentions transactional notifications, backend-triggered sends, campaign_id trigger APIs, or "API-triggered campaigns".
+
+### References
+
+- [Api Contract (Reference)](https://raw.githubusercontent.com/clix-so/skills/refs/heads/main/skills/api-triggered-campaigns/references/api-contract.md): Reference documentation for api-triggered-campaigns skill
+- [Backend Patterns (Reference)](https://raw.githubusercontent.com/clix-so/skills/refs/heads/main/skills/api-triggered-campaigns/references/backend-patterns.md): Reference documentation for api-triggered-campaigns skill
+- [Console Setup (Reference)](https://raw.githubusercontent.com/clix-so/skills/refs/heads/main/skills/api-triggered-campaigns/references/console-setup.md): Reference documentation for api-triggered-campaigns skill
+- [Debugging (Reference)](https://raw.githubusercontent.com/clix-so/skills/refs/heads/main/skills/api-triggered-campaigns/references/debugging.md): Reference documentation for api-triggered-campaigns skill
+- [Personalization And Dynamic Filters (Reference)](https://raw.githubusercontent.com/clix-so/skills/refs/heads/main/skills/api-triggered-campaigns/references/personalization-and-dynamic-filters.md): Reference documentation for api-triggered-campaigns skill
+- [Security And Keys (Reference)](https://raw.githubusercontent.com/clix-so/skills/refs/heads/main/skills/api-triggered-campaigns/references/security-and-keys.md): Reference documentation for api-triggered-campaigns skill
+
+### Examples
+
+- [Trigger Campaign Node (Example)](https://raw.githubusercontent.com/clix-so/skills/refs/heads/main/skills/api-triggered-campaigns/examples/trigger-campaign-node.js): Code example for api-triggered-campaigns skill
+- [Trigger Campaign Python (Example)](https://raw.githubusercontent.com/clix-so/skills/refs/heads/main/skills/api-triggered-campaigns/examples/trigger-campaign-python.py): Code example for api-triggered-campaigns skill
+
+### Scripts
+
+- [Validate Api Trigger Plan (Script)](https://raw.githubusercontent.com/clix-so/skills/refs/heads/main/skills/api-triggered-campaigns/scripts/validate-api-trigger-plan.sh): Utility script for api-triggered-campaigns skill
+
+---
+
 ## clix-event-tracking
 
 Implements Clix event tracking (Clix.trackEvent) with consistent naming, safe property schemas, and campaign-ready validation. Use when adding, reviewing, or debugging event tracking; when configuring event-triggered campaigns; or when the user mentions events, tracking, funnels, or properties — or when the user types `clix-event-tracking`.
@@ -54,6 +80,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.9",
   "description": "An open collection of agent skills for Clix.",
   "main": "dist/index.js",
   "bin": {

package/skills/api-triggered-campaigns/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/api-triggered-campaigns/SKILL.md

@@ -0,0 +1,186 @@
+---
+name: clix-api-triggered-campaigns
+description:
+  Helps developers configure API-triggered campaigns in the Clix console and
+  trigger them from backend services with safe auth, payload schemas, dynamic
+  audience filters (trigger.*), and personalization best practices. Use when the
+  user mentions transactional notifications, backend-triggered sends,
+  campaign_id trigger APIs, or "API-triggered campaigns".
+---
+
+# API-Triggered Campaigns (Backend → Clix)
+
+Use this skill to set up **API-triggered campaigns** in the Clix console and
+trigger them from your backend with dynamic data (`trigger.*`) for:
+
+- Transactional notifications (orders, password reset, receipts)
+- Workflow messages (assignments, approvals)
+- System alerts (moderation, support tickets)
+- Programmatic sends where marketers/ops should control content + targeting
+
+## What the official docs guarantee (high-signal)
+
+- API-triggered campaigns are configured in the console, then triggered via:
+  `POST /api/v1/campaigns/{campaign_id}:trigger`
+- Authentication uses **secret** headers:
+  - `X-Clix-Project-ID`
+  - `X-Clix-API-Key`
+- Request `properties` become **`trigger.*`** for:
+  - **Dynamic audience filtering** (console audience rules)
+  - **Personalization** in templates (title/body/deep links)
+- `audience.broadcast=true` sends to all users eligible under the campaign’s
+  segment definition; `audience.targets` narrows to specific users/devices
+  (still filtered by the segment definition).
+- Dynamic audience filters are intentionally constrained for performance: **max
+  3 attributes** in the audience definition.
+
+## MCP-first (source of truth)
+
+If Clix MCP tools are available, treat them as the **source of truth**:
+
+- Use `clix-mcp-server:search_docs` to confirm the latest API contract + limits:
+  - query examples:
+    - `"API-triggered campaign trigger endpoint"`
+    - `"campaigns/{campaign_id}:trigger audience targets broadcast"`
+    - `"trigger.* dynamic audience filters limitations"`
+
+If MCP tools are not available, use the bundled references:
+
+- API contract → `references/api-contract.md`
+- Console setup + dynamic filters → `references/console-setup.md`
+- Backend patterns (auth, retries, timeouts) → `references/backend-patterns.md`
+- Security/key handling → `references/security-and-keys.md`
+- Personalization + dynamic filters →
+  `references/personalization-and-dynamic-filters.md`
+- Debugging checklist → `references/debugging.md`
+
+## Workflow (copy + check off)
+
+```
+API-triggered campaign progress:
+- [ ] 1) Confirm goals + trigger source (what backend event sends the message?)
+- [ ] 2) Define campaign contract (properties keys/types; PII policy)
+- [ ] 3) Configure campaign in console (API-triggered + audience rules + templates)
+- [ ] 4) Implement backend trigger wrapper (auth, timeout, retries, logging)
+- [ ] 5) Validate trigger plan JSON (schema + naming + safety)
+- [ ] 6) Verify in Clix (test payloads, Message Logs, segment matching)
+```
+
+## 1) Confirm the minimum inputs
+
+Ask only what’s needed:
+
+- **Campaign**: where is it in the console? do you already have `campaign_id`?
+- **Channel**: push / in-app / email / etc. (affects message template fields)
+- **Audience mode**: broadcast vs explicit targets
+- **Dynamic filter keys**: which `trigger.*` keys are used in audience rules
+- **Properties**: list of keys + types + example values (avoid PII by default)
+- **Backend**: runtime and HTTP client (Node/Fetch, Axios, Python, Go, etc.)
+
+## 2) Create a “Trigger Plan” (before touching backend code)
+
+Create `api-trigger-plan.json` in `.clix/` (recommended) or project root.
+
+**Recommended location**: `.clix/api-trigger-plan.json`
+
+**Plan schema (high-level):**
+
+- `campaign_id` (string)
+- `audience.mode`: `"broadcast" | "targets" | "default"`
+- `audience.targets` (if mode is `"targets"`)
+- `dynamic_filter_keys` (array of up to 3 snake_case keys)
+- `properties` (map of snake_case keys → `{ type, required?, example?, pii? }`)
+
+Example:
+
+```json
+{
+  "campaign_id": "019aa002-1d0e-7407-a0c5-5bfa8dd2be30",
+  "audience": {
+    "mode": "broadcast"
+  },
+  "dynamic_filter_keys": ["store_location"],
+  "properties": {
+    "store_location": {
+      "type": "string",
+      "required": true,
+      "example": "San Francisco"
+    },
+    "order_id": { "type": "string", "required": true, "example": "ORD-12345" },
+    "item_count": { "type": "number", "required": true, "example": 3 },
+    "pickup_time": { "type": "string", "required": false, "example": "2:30 PM" }
+  }
+}
+```
+
+## 3) Configure campaign in the console (API-triggered)
+
+- Set the campaign type to **API-Triggered**.
+- Build audience rules using `{{ trigger.* }}` for dynamic filters.
+- Use `{{ trigger.* }}` in message templates + deep links.
+
+See: `references/console-setup.md` for exact guidance and limitations.
+
+## 4) Implement backend trigger wrapper (best practices)
+
+Backend wrapper responsibilities:
+
+- **Auth**: load `X-Clix-Project-ID` and `X-Clix-API-Key` from
+  environment/secret store (never commit).
+- **Timeout**: set a short timeout (e.g., 3–10s) and fail fast.
+- **Retries**: retry only on transient failures (network/5xx), with backoff; do
+  not retry blindly on 4xx.
+- **Dedupe**: prevent double-sends in your system (e.g., unique key per order
+  event) since the API call is “send-like”.
+- **Logging**: log `campaign_id`, your correlation id (order id), and the Clix
+  response (e.g., `trigger_id`).
+
+Copy/paste examples:
+
+- Node: `examples/trigger-campaign-node.js`
+- Python: `examples/trigger-campaign-python.py`
+
+## 5) Validate the plan (fast feedback loop)
+
+Run:
+
+```bash
+bash <skill-dir>/scripts/validate-api-trigger-plan.sh .clix/api-trigger-plan.json
+```
+
+This validator checks:
+
+- valid JSON
+- `campaign_id` present
+- `dynamic_filter_keys` is ≤ 3 and snake_case
+- `properties` keys are snake_case and have valid types
+- example values match declared types
+- `targets` entries specify exactly one of `project_user_id` or `device_id`
+
+## 6) Verify (Clix + end-to-end)
+
+Minimum verification:
+
+- Campaign is **API-Triggered** and `campaign_id` matches.
+- If using dynamic audience filters, the `trigger.*` keys exist in the API call
+  and match audience rules exactly.
+- Trigger once with a known-good payload; confirm delivery + inspect Message
+  Logs for rendering errors.
+
+See `references/debugging.md`.
+
+## Progressive Disclosure
+
+- **Level 1**: This `SKILL.md` (always loaded)
+- **Level 2**: `references/` (load when implementing details)
+- **Level 3**: `examples/` (load when copy/pasting backend code)
+- **Level 4**: `scripts/` (execute directly; do not load into context)
+
+## References
+
+- `references/api-contract.md`
+- `references/console-setup.md`
+- `references/backend-patterns.md`
+- `references/security-and-keys.md`
+- `references/personalization-and-dynamic-filters.md`
+- `references/debugging.md`

package/skills/api-triggered-campaigns/examples/trigger-campaign-node.js

@@ -0,0 +1,62 @@
+/**
+ * Minimal Node.js example: trigger an API-triggered campaign.
+ *
+ * Requirements:
+ * - Node 18+ (fetch is available) OR replace with your HTTP client
+ * - Env vars:
+ *   - CLIX_PROJECT_ID
+ *   - CLIX_API_KEY
+ */
+
+const CLIX_PROJECT_ID = process.env.CLIX_PROJECT_ID;
+const CLIX_API_KEY = process.env.CLIX_API_KEY;
+
+if (!CLIX_PROJECT_ID || !CLIX_API_KEY) {
+  throw new Error("Missing CLIX_PROJECT_ID or CLIX_API_KEY");
+}
+
+async function triggerCampaign({ campaignId, audience, properties }) {
+  const url = `https://api.clix.so/api/v1/campaigns/${campaignId}:trigger`;
+
+  const res = await fetch(url, {
+    method: "POST",
+    headers: {
+      "X-Clix-Project-ID": CLIX_PROJECT_ID,
+      "X-Clix-API-Key": CLIX_API_KEY,
+      "Content-Type": "application/json",
+    },
+    body: JSON.stringify({
+      audience,
+      properties,
+    }),
+  });
+
+  const text = await res.text();
+  if (!res.ok) {
+    throw new Error(`Clix trigger failed (${res.status}): ${text}`);
+  }
+  return JSON.parse(text);
+}
+
+// Example usage
+async function main() {
+  const campaignId = "019aa002-1d0e-7407-a0c5-5bfa8dd2be30"; // replace
+
+  const payload = {
+    audience: { broadcast: true },
+    properties: {
+      store_location: "San Francisco",
+      order_id: "ORD-12345",
+      item_count: 3,
+      pickup_time: "2:30 PM",
+    },
+  };
+
+  const out = await triggerCampaign({ campaignId, ...payload });
+  console.log(out); // { trigger_id: "..." }
+}
+
+main().catch((e) => {
+  console.error(e);
+  process.exit(1);
+});