openclix

Option A: Let an agent do it

Paste this prompt into your coding agent:

OpenClix is an open-source, MIT-licensed project (https://github.com/openclix/openclix).
Install OpenClix first-party skills by running: npx skills add openclix/openclix
Skills are not available until the next session, so read each SKILL.md directly
from the installed skill directory and follow its instructions for this session.
Use openclix-init to detect platform, copy templates into the dedicated OpenClix namespace,
wire initialization/event/lifecycle touchpoints, and run build verification.
If this project already has local notifications outside OpenClix, detect whether they are migration-capable,
ask whether to migrate supported flows into OpenClix or keep them as-is, and default to keeping them unchanged.
Then use openclix-design-campaigns to create .openclix/campaigns/app-profile.json
and generate .openclix/campaigns/openclix-config.json.
Do not add dependencies without approval.

Option B: Manual setup

Follow the full guide: Install and integrate OpenClix

Option C: Claude Code plugin marketplace

Follow the guide here: Add Claude Code Plugin

Advanced setup

If you wnat to integrate with your PA tools

Use openclix-analytics to detect installed Firebase/PostHog/Mixpanel/Amplitude,
forward OpenClix events with openclix tags, and produce a pre/post impact report
for D7 retention and engagement metrics.

To update campaigns

Use openclix-update-campaigns to propose pause/resume/add/delete/update
actions from campaign metrics and produce openclix-config.next.json before
applying any change to the active config.

To sync OpenClix source code

Use openclix-update to re-sync existing OpenClix source integration files
with the latest openclix-init template baseline.
This keeps custom campaign logic updates (openclix-update-campaigns) and
template maintenance (openclix-update) clearly separated.

1. Install skills:

npx skills add openclix/openclix

2. Run openclix-init to integrate templates and touchpoints. If the app already has local notifications, openclix-init will detect them, classify whether supported flows can migrate into OpenClix, and default to keeping the existing implementation unless migration is explicitly requested.
3. Run openclix-design-campaigns to generate .openclix/campaigns/openclix-config.json.
4. Run openclix-analytics to detect provider wiring and generate impact artifacts.
5. Run openclix-update-campaigns to produce conservative recommendation drafts.
6. Run openclix-update when the plugin template baseline changes and source files need re-synchronization.