Rheo Agent Skill
Use a local AI agent to install Rheo for Analytics, Convert, and Engage, or to import a flow manifest.
Purpose
The Rheo agent skill helps local AI assistants (Cursor, Claude Code, Codex, and similar) work with Rheo on your machine. When @getrheo/cli is installed, prefer rheo import … for validate/scaffold/audit; the skill scripts remain for offline agent packs.
Rheo is one SDK and one Customer across three products:
- Analytics: sessions, screens, custom events, and revenue attribution
- Convert: onboarding, paywalls, and experiments rendered from a flow manifest
- Engage: email, webhook, and push (
identifyandregisterPushon web and React Native)
The skill can:
- Install the SDK and wire the products you ask for (
RheoProvider, product analytics,Flow,identify) on supported install stacks (below) - Import an existing mobile onboarding or paywall into a Convert manifest (React Native or SwiftUI source)
- Validate that manifest against dashboard publish rules
Your source code never leaves your machine. Only the generated manifest or ZIP bundle is uploaded to Rheo when you import in the dashboard.
Supported stacks
| Capability | Supported today |
|---|---|
| SDK install | Expo, bare React Native, and React web |
| Flow import | React Native and SwiftUI source → Convert FlowManifest |
SwiftUI and Flutter SDK install paths are coming soon — not customer-installable packages yet. Do not ask the skill to install a SwiftUI or Flutter SDK. You can still import a SwiftUI flow into a Convert manifest for the dashboard. See SDK overview.
Install the skill
npx skills add getrheo/rheo-skillWhat the skill includes
| Capability | Use when |
|---|---|
| Best practices | Installing the SDK for Expo, bare React Native, or React web. Analytics (logEvent, web consent), Convert channels and terminal callbacks, Engage identify / registerPush, RevenueCat / Superwall / Stripe, AppsFlyer, External Surface Nodes, auth handlers |
| Flow import | Analyzing a React Native or SwiftUI flow, exporting a FlowManifest, validating it, and packaging rheo-import.zip |
Example prompts
Use the Rheo skill to add Analytics to this Expo app. Mount the provider and record screen views. Do not add a flow.Use the Rheo skill to implement Convert in this Expo app with placeholders for the publishable key and channel id.Use the Rheo skill to call identify when the user opts into Engage messages, and logEvent trial_started when that Analytics event should start an automation.Use the Rheo skill to import our onboarding from app/onboarding.tsx.Audit this manifest against Rheo publish rules before I upload rheo-import.zip.Typical workflows
Implement the SDK
- Say which products you want. Analytics, Convert, and Engage can be wired independently. The provider is shared.
- The agent follows the best-practice reference for your stack (Expo, bare React Native, or React web).
- It installs one SDK, mounts
RheoProvider, and adds only the calls that product uses. - Manifest changes happen only if you also asked for an import.
On the web, product analytics stays off until your site grants consent. Engage identify ships in @getrheo/react alongside registerPush() for Web Push (save a VAPID key first). See Web SDK.
Import an existing flow
- Point the agent at your flow entry file (React Native or SwiftUI).
- Answer the intake questions (purpose, fidelity vs editability, motion import, and so on).
- The agent audits your code, scaffolds a manifest, validates it, and writes
rheo-import.zip. - Upload the ZIP in the Rheo builder with Import from agent. See Agent import.
Import produces a Convert manifest. It does not install the SDK.