> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openclix.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Installation

> Install OpenClix skills and start agent-based mobile app retention and engagement automation.

OpenClix is currently delivered as agent skills plus reference templates.
This installation path is intended for agent-based mobile app retention and engagement automation.

## Option A: Agent-first (recommended)

Use this prompt in your coding agent:

```text theme={null}
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.
Then use openclix-update when updating plugin integrations to refresh source files
from the latest openclix-init templates.
Then 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.
Then use openclix-update-campaigns to draft campaign action recommendations.
Then run scripts/retention_ops_automation.sh with --agent all to generate
OpenClaw, Claude Code, and Codex review prompts before apply.
Do not add dependencies without approval.
```

## Option B: Manual skill install

1. Install skills:

```bash theme={null}
npx skills add openclix/openclix
```

2. Run `openclix-init` in your app project. If local notifications already exist, it will detect those paths, determine whether supported flows are migration-capable, and default to keeping the current implementation unless you explicitly choose migration.
3. Run `openclix-design-campaigns` to generate campaign config.
4. Run `openclix-analytics` to wire event forwarding and produce impact outputs.
5. Run `openclix-update-campaigns` to draft campaign operation changes.
6. Run `openclix-update` when you want to re-sync OpenClix source files after
   template updates from this repository.
7. Run `scripts/retention_ops_automation.sh` to generate OpenClaw/Claude Code/Codex review prompts.

## Option C: Claude Code plugin marketplace

Use Claude Code marketplace registration when you want managed plugin updates:

```bash theme={null}
claude plugin marketplace add openclix/openclix
claude plugin marketplace update openclix
claude plugin install openclix@openclix
```

For local pre-release validation from a checkout:

```bash theme={null}
claude plugin marketplace add /absolute/path/to/openclix
```

To pull marketplace/plugin updates later:

```bash theme={null}
claude plugin marketplace update openclix
claude plugin update openclix@openclix
```

Validate plugin manifests locally before publishing:

```bash theme={null}
bash scripts/validate_claude_plugin.sh
```

Continue with the [agent-based mobile app retention automation workflow](/getting-started/workflow).