Wire OpenClix events to an installed product analytics provider (Firebase, PostHog, Mixpanel, or Amplitude) and produce pre/post campaign impact reports centered on 7-day retention. TRIGGER when the user asks to "connect analytics", "measure campaign impact", "check retention", "tag OpenClix events", or wants to know whether campaigns are working — even if they say "are my notifications helping?" without mentioning analytics. DO NOT trigger for campaign config changes based on metrics — that belongs to openclix-update-campaigns.
Design, create, and iterate OpenClix campaign configurations from product goals and app events, producing schema-valid openclix-config.json with delivery mode setup. TRIGGER when the user asks to "create campaigns", "design notifications", "configure engagement messages", "set up onboarding/re-engagement/streak flows", or refine trigger logic, suppression rules, or message content — even if they just describe a retention goal without mentioning campaigns. DO NOT trigger for campaign performance analysis or optimization from metrics — that belongs to openclix-update-campaigns.
Set up OpenClix in a mobile app by detecting the platform, copying source templates into a dedicated namespace, wiring initialization/event/lifecycle touchpoints, and running build verification. TRIGGER when the user asks to "integrate OpenClix", "set up local notifications", "add engagement logic", or mentions OpenClix for the first time in a project without an existing integration — even if they don't mention this skill by name. DO NOT trigger when OpenClix is already integrated and the user is asking about campaigns, analytics, or template updates — those belong to other openclix-* skills.
Propose campaign operations (pause/resume/add/delete/update) from measured analytics performance, produce openclix-config.next.json, and apply only after user confirmation. TRIGGER when the user asks to "optimize campaigns", "pause underperforming notifications", "adjust campaigns based on data", or review campaign performance for operational decisions — even if they say "this campaign isn't working, what should I do?". DO NOT trigger for initial campaign design (openclix-design-campaigns), analytics wiring (openclix-analytics), or source template updates (openclix-update).
Sync OpenClix source-integration code with the latest openclix-init template baseline using dry-run planning and explicit overwrite controls. TRIGGER when the user asks to "update OpenClix", "sync templates", "refresh integration code", or when the openclix-init template baseline has changed and source files need re-sync. DO NOT trigger for campaign config updates — that belongs to openclix-update-campaigns. This skill updates integration source code, not campaign configurations.