Logo Growth Engineer
View AnalyticsCLI
Free OpenClaw & Hermes Agent Skill

Your product data,
turned into work .

Automatically reads your product signals in background intervals. Ranks what matters. Delivers GitHub issues, PRs, or notifications.

hey agent please install this skill https://clawhub.ai/wotaso-dev/growth-engineer

Send this to OpenClaw or any compatible agent.

See setup guide

Reads daily / weekly / monthly

AnalyticsCLI

funnels · retention · dropoffs

RevenueCat

subscriptions · transactions · MRR

Sentry

crash details · errors · releases

App Store Connect

analytics · reviews · ratings

GitHub

code context · issues · PRs

↓
Reasoning
AI

OpenClaw

Runs daily, weekly,
or monthly as you like

Ranks opportunities
Maps evidence to work

with Growth Engineer

Use OpenClaw with Growth Engineer. Normal coding agents can use the raw AnalyticsCLI skill .

↓

Creates automatically

⚡

GitHub Issue

Ready-to-act task with evidence

🔀

Pull Request

Draft PR with implementation notes

💬

Social / Chat

DM via OpenClaw channels

▣

Summaries

Concise signal digests for review

How it works

Signals in. Action out.

1. Reads Product Signals

Connect analytics, revenue, crashes, feedback, store data, and repository context once.

1

2. Maps Signals to Code

The agent connects behavior changes to likely screens, files, funnels, and recent product changes.

2

3. Ranks What Matters

Opportunities are ranked by activation, retention, revenue impact, confidence, and engineering effort.

3

4. Delivers Work

Receive GitHub issues, PR prompts, notifications, or summaries with evidence, affected files, and verification KPIs.

4

What you will get

Actionable insights delivered directly as implementation-ready issues, PR prompts, or notifications.

Analyzed AnalyticsCLI, RevenueCat & GitHub codebase

Growth Engineer Just now

I found a 54% conversion drop after Survey 2.

I created an implementation-ready issue with evidence, affected files, and a KPI to verify the fix.

Recommended Work
  • Add value framing right before the paywall.
  • Use guest / anonymous login to reduce friction.

What each GitHub issue contains

Each issue is built from your real product data and codebase context, so OpenClaw or another coding agent can start from evidence.

Problem
Evidence
Affected Code Modules
Proposed Implementation
Expected Impact
Confidence
Verification KPI
Optional PR Prompt
Improve onboarding activation #124
# Problem Activation drops after Survey 2 before users reach the first useful result. # Evidence - Funnel shows 54% drop between Survey 2 and the paywall. - Feedback mentions setup confusion in the same release window. - No major crash spike, so this is likely product friction. # Affected files/modules - app/onboarding/onboarding.tsx - app/paywall/paywall.ts # Proposed implementation 1. Add value framing before the paywall. 2. Offer guest/anonymous continuation. 3. Track exposure, accept, decline, and first-result completion. # Agent PR prompt "Implement issue #124 and verify activation from Survey 2 to first result."
Setup guide

How to set it up

Ready to connect AnalyticsCLI and run the Growth Engineer in your own app workspace.

1

Install the agent skill

Send this prompt to OpenClaw or any compatible agent to install the Growth Engineer.

To your agent
hey agent please install this skill https://clawhub.ai/wotaso-dev/growth-engineer
2

Run the connector wizard

Use the local terminal wizard to securely connect your data sources. Tokens stay on your machine.

Terminal
$ npx -y @analyticscli/growth-engineer@preview wizard --connectors
3

Verify and start

Simply ask your agent to verify the setup and start analyzing your product signals.

To your agent
hey agent, is the growth engineer correctly set up? If yes, please run the first pass.