Skillget

openclix

skill
Guvenlik Denetimi
Gecti
Health Gecti
  • License — License: MIT
  • Description — Repository has a description
  • Active repo — Last push 0 days ago
  • Community trust — 36 GitHub stars
Code Gecti
  • Code scan — Scanned 12 files during light audit, no dangerous patterns found
Permissions Gecti
  • Permissions — No dangerous permissions requested
Purpose
This tool provides an open-source, local-first framework for automating mobile app user retention and engagement. It uses configuration-driven templates and AI agent workflows to manage onboarding, habits, and feature-discovery messaging.

Security Assessment
Overall Risk: Low. The tool operates with a local-first architecture, meaning it processes and executes engagement logic directly on the user's device rather than relying heavily on external servers. A lightweight code scan of 12 files found no dangerous patterns, no hardcoded secrets, and no requirement for dangerous system permissions. It provides explicit instructions for coding agents and requires manual approval before adding new dependencies, giving developers strict control over what gets executed. While it supports integration with third-party analytics tools like Firebase or Mixpanel, it only forwards standard event data and requires explicit configuration to do so.

Quality Assessment
The project demonstrates strong health and active maintenance, with its most recent push happening today. It is fully licensed under the standard MIT open-source license, ensuring clear legal permissions for use and modification. Community trust is currently low-to-moderate but growing, having earned 36 GitHub stars. The documentation is thorough, offering clear installation guides, agent prompts, and accessible source templates.

Verdict
Safe to use.
SUMMARY

Open-source, local-first mobile app retention and engagement automation with agent-driven workflows.

README.md

Event Flyer - dark Event Flyer - light

OpenClix
Open-source, local-first foundation for config-driven mobile engagement logic.

Introduction

OpenClix helps teams run onboarding, habit, re-engagement, and feature-discovery messaging with local-first execution.

It is designed to be:

  • Open source and auditable
  • Source-first (vendored client code, not runtime SDK lock-in)
  • Agent-friendly (explicit interfaces and clear edit points)

Installation

OpenClix is delivered as skills + source templates.

For Humans

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.
For Agents
  1. Install skills:
npx skills add openclix/openclix
  1. 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.
  2. Run openclix-design-campaigns to generate .openclix/campaigns/openclix-config.json.
  3. Run openclix-analytics to detect provider wiring and generate impact artifacts.
  4. Run openclix-update-campaigns to produce conservative recommendation drafts.
  5. Run openclix-update when the plugin template baseline changes and source files
    need re-synchronization.

Documentation

Topic Link
Installation Install and integrate OpenClix
Workflow Run the OpenClix workflow
Verification Verify your integration
Retention automation Agent retention automation guide
Config delivery Config delivery guide
Campaign design Campaign design guide
Analytics impact Analytics impact guide
Runtime model Runtime model reference
Use cases Use cases reference
FAQ FAQ
Project status Project status

What OpenClix Is Not

  • Not a hosted full engagement platform
  • Not a required runtime package dependency
  • Not dependent on a Clix-hosted control plane for local-first flows

Contributing

Use issues and pull requests to propose improvements to the project and documentation.

License

MIT License. See LICENSE.

Yorumlar (0)

Sonuc bulunamadi