growth-engineer
Growth Engineer for mobile apps and agent runtimes including OpenClaw and Hermes. Correlate analytics, crashes, billing, feedback, store signals, and repo context into proposal drafts that can flow into agent chat, GitHub issues, or draft pull requests.
Rank
62
Safety
84
Downloads
4.2k
Updated
Oct 9, 2026
Version
1.0.210
Source
CLAWHUB
About
What it does, and when to use it.
Capability contract not published. No trust telemetry is available yet. 4.2K downloads reported by the source. Last updated 10/9/2026.
Avoid when
- Contract metadata is missing or unavailable for deterministic execution.
Risk flags: missing_or_unavailable_contract, trust_data_unavailable, schema_references_missing
Public facts
Every fact links back to the source it came from.
- Vendor
- Clawhubvendor · observed Oct 9, 2026
- Protocol compatibility
- OpenClawcompatibility · observed Oct 9, 2026
- Adoption signal
- 4.2K downloadsadoption · observed Oct 9, 2026
- Latest release
- 1.0.210release · observed Aug 5, 2026
- Handshake status
- UNKNOWNsecurity
Install and run
Setup complexity: low.
clawhub skill install s170c9mk58sce90xhk2assttk183h5n5:growth-engineer- Install using `clawhub skill install s170c9mk58sce90xhk2assttk183h5n5:growth-engineer` in an isolated environment before connecting it to live workloads.
- No published capability contract is available yet, so validate auth and request/response behavior manually.
- Review the upstream CLAWHUB listing at https://clawhub.ai/wotaso-dev/growth-engineer before using production credentials.
Contract: missing
curl -s "https://www.xpersona.co/api/v1/agents/clawhub-wotaso-dev-growth-engineer/snapshot"
Documentation
CLAWHUB
160,000 characters of source documentation, loaded on request.
Extracted files
5 files captured from the source.
SKILL.md
---
name: growth-engineer
description: Growth Engineer for mobile apps and agent runtimes including OpenClaw and Hermes. Correlate analytics, crashes, billing, feedback, store signals, and repo context into proposal drafts that can flow into agent chat, GitHub issues, or draft pull requests.
license: MIT
homepage: https://github.com/Wotaso/growth-engineer-skill
metadata: {"author":"wotaso","version":"1.0.210","analyticscli-target":"@analyticscli/cli","analyticscli-supported-range":">=0.1.3 <0.2.0","openclaw":{"emoji":"🚀","homepage":"https://github.com/Wotaso/growth-engineer-skill","requires":{"bins":["node","analyticscli"]},"install":[{"id":"analyticscli-cli","kind":"node","package":"@analyticscli/cli","bins":["analyticscli"],"label":"Install/update AnalyticsCLI CLI (npm package @analyticscli/cli)"}]},"hermes":{"tags":["Growth","Analytics","Mobile","Product","OpenClaw","Hermes"],"homepage":"https://github.com/Wotaso/growth-engineer-skill","requires":{"bins":["node","analyticscli"]},"install":[{"id":"growth-engineer","kind":"skill","package":"Wotaso/growth-engineer-skill","label":"Install the shared Growth Engineer for Hermes"}]}}
---
# Growth Engineer
## Canonical Skill Identity
`growth-engineer` is the single canonical Growth Engineer for agent-driven product and growth work.
The old `ai-product-manager` / `product-manager-skill` package is deprecated and should be used only as a migration alias for existing installs.
Do not recommend installing or loading both skills.
Use this same skill for OpenClaw and Hermes. Do not create a duplicate Hermes-specific copy of the instructions, scripts, references, or runtime artifacts. If an agent-specific compatibility note is needed, add a small section here and keep the deterministic runtime shared.
## Agent Compatibility
- OpenClaw: install through ClawHub with `clawhub install growth-engineer` or `npx clawhub install growth-engineer`.
- Hermes: install the same public skill repository with `hermes skills install Wotaso/growth-engineer-skill`.
- Generic SKILL.md clients: install or mount the same `skills/openclaw-growth-engineer` folder.
- All agents should use the same bundled `scripts/`, `references/`, and `data/` files.
- macOS hosts, including Mac mini machines, are supported as normal local hosts. Use the same terminal wizard from the app workspace. For recurring unattended runs on macOS, use OpenClaw heartbeats, `openclaw run --loop`, or a host scheduler such as `launchd`; keep secrets in the host terminal/env/secret file, not in chat.
## Local AnalyticsCLI Operator Notes
These notes apply when this skill is used from the local `Wotaso/analyticscli-monorepo` workspace.
- Coolify resources, projects, or deployments named `prodinfos` are AnalyticsCLI production infrastructure, not a separate customer app. Treat failed `prodinfos` deployments as AnalyticsCLI production deployment-health signals.
- For this workspace, Coolify monitoring is configured through `openclaw.config.json` with `https:README.md
# OpenClaw Growth Engineer Shared AI Growth Engineer for mobile apps, centered around a standalone `openclaw` CLI runtime plus the host agent as the AI layer. It pulls together analytics, monetization, crashes, feedback, store signals, and repo context and turns them into proposal drafts that can be handed to OpenClaw chat, GitHub issues, or draft PRs. If you only want the normal setup path: run the local connector wizard once, then start the CLI. ## Shared Skill Distribution This folder is the single canonical skill for OpenClaw, Hermes, and generic `SKILL.md` clients. Do not fork the instructions or runtime for Hermes. Keep shared behavior in this folder and use only small metadata/docs notes for agent-specific install paths. OpenClaw install: ```bash npx clawhub install openclaw-growth-engineer ``` Hermes install: ```bash hermes skills install Wotaso/openclaw-growth-engineer-skill ``` ## Quick Start 1. Paste this into the VPS, Mac mini, or host shell for the active app workspace: ```bash npx -y @analyticscli/growth-engineer wizard --connectors ``` Secrets stay in the VPS/host shell wizard. Do not use chat or a standalone `analyticscli login` step for first setup. 2. Run setup: ```bash growth-engineer setup --config openclaw.config.json ``` This should: - initialize `openclaw.config.json` - install/update `@analyticscli/cli` so the `analyticscli` binary exists - reuse the existing AnalyticsCLI setup flow - install/update the shared skills like `analyticscli-cli` and `analyticscli-ts-sdk` - install the canonical OpenClaw skill path through the shared installer instead of redefining it locally 3. Run preflight: ```bash growth-engineer preflight --config openclaw.config.json --test-connections ``` The preflight/start runtime also repairs a missing `analyticscli` binary by running: ```bash npm install -g @analyticscli/cli ``` If global npm installs are blocked, it falls back to a user-local npm prefix at `~/.local`. For manual repair from a copied skill runtime, run: ```bash bash skills/openclaw-growth-engineer/scripts/install-analyticscli-cli.sh ``` 4. Start the first pass: ```bash openclaw start --config openclaw.config.json ``` For recurring OpenClaw checks, setup/start configures OpenClaw Gateway cron when available and keeps a non-empty workspace `HEARTBEAT.md` in place as fallback. For Hermes installs, the same wizard/start path configures Hermes cron when the `hermes` CLI is available. In both cases, the scheduler only wakes the agent; the Growth Engineer runner remains the source of truth for daily, weekly, monthly, quarterly, six-month, and yearly cadence decisions. Setup should guide the developer through each missing piece. When something is blocked, the agent should explain what was detected, why the missing value matters, where to get it, and the minimum permission needed instead of returning a generic failure. Before requesting optional credentials, ask which connections the user wants to set up: AnalyticsCL
_meta.json
{
"ownerId": "kn77jehzjrg5rxpfdjmq75fc1n83dm6w",
"slug": "growth-engineer",
"version": "1.0.210",
"publishedAt": 1785922010943
}references/advanced-setup.md
# Advanced Setup Use this page only when the default wizard flow is not enough. Default path: 1. Install with `npx -y clawhub install openclaw-growth-engineer` 2. Bootstrap once with `bash skills/openclaw-growth-engineer/scripts/bootstrap-openclaw-workspace.sh` 3. Run `npx -y @analyticscli/growth-engineer wizard --connectors` 4. For connector setup, run `npx -y @analyticscli/growth-engineer wizard --connectors github,revenuecat,paddle,seo,sentry,asc` 5. Run `node scripts/openclaw-growth-start.mjs --config data/openclaw-growth-engineer/config.json` ## Secrets - Keep secrets out of repo files and out of `config.json`. - Prefer the OpenClaw runtime or secret store for secret injection. - Use raw env vars only when your OpenClaw setup does not already manage them for you. - The exact env names live in `config.secrets` and in [Required Secrets](required-secrets.md). ## Connector Overrides - Built-in source keys are `analytics`, `revenuecat`, `paddle`, `seo`, `sentry`, `coolify`, and `feedback`; `feedback` is part of the AnalyticsCLI/custom feedback source, not a separate primary setup connector. - Extra mobile connectors go into `sources.extra[]`. - Prefer `mode=file` for maximum stability. - Use `mode=command` when the command deterministically returns JSON. - Put Sentry Cloud and self-hosted GlitchTip accounts under `sources.sentry.accounts[]` when they expose the Sentry-compatible API. Treat ASC CLI as the ASC / App Store Connect connector, not as a generic extra. Useful extras: - `app-store-reviews` - `play-console` - `firebase-crashlytics` ## Delivery Modes - `actions.mode = "issue"` creates implementation-ready GitHub issues. - `actions.mode = "pull_request"` creates draft PRs plus `.openclaw/proposals/...` files. ## Scheduling - One-shot run: `node scripts/openclaw-growth-runner.mjs --config data/openclaw-growth-engineer/config.json` - Continuous loop: `node scripts/openclaw-growth-runner.mjs --config data/openclaw-growth-engineer/config.json --loop` - Preflight only: `node scripts/openclaw-growth-preflight.mjs --config data/openclaw-growth-engineer/config.json --test-connections` ## Schema And Examples - [Setup And Scheduling](setup-and-scheduling.md) - [Required Secrets](required-secrets.md) - [Input Schema](input-schema.md)
references/input-schema.md
# Input Schema
The analyzer accepts multiple JSON shapes.
Preferred order:
1. shared `signals[]`
2. crash-style `issues[]`
3. feedback-style `items[]`
## Shared `signals[]`
Use this for analytics, revenue, store, and custom connectors:
```json
{
"project": "my-mobile-app",
"window": "last_30d",
"signals": [
{
"id": "retention_d3_drop",
"title": "Day-3 retention dropped after onboarding paywall changes",
"area": "onboarding",
"priority": "high",
"metric": "d3_retention",
"current_value": 0.18,
"baseline_value": 0.27,
"delta_percent": -33.3,
"evidence": [
"Drop started after release 1.4.2",
"Largest loss between onboarding step 2 and paywall view"
],
"suggested_actions": [
"Move paywall after first core value event",
"Simplify onboarding step 2 form"
],
"keywords": ["onboarding", "paywall", "trial"]
}
]
}
```
## Crash `issues[]`
Works for Sentry, GlitchTip, Crashlytics-style exports:
```json
{
"issues": [
{
"id": "glitchtip_1431",
"title": "TypeError in paywall purchase callback",
"priority": "high",
"impact": "Conversion blocker in purchase flow",
"events": 312,
"users": 119,
"stack_keywords": ["paywall", "purchase", "subscription", "callback"],
"evidence": ["Crash occurs within 3s after paywall shown"]
}
]
}
```
## Feedback `items[]`
Works for support, app reviews, in-app feedback, store review exports:
```json
{
"window": "last_30d",
"items": [
{
"id": "fb_onboarding_too_long",
"title": "Onboarding feels too long before first value",
"area": "onboarding",
"priority": "medium",
"count": 14,
"channel": "support_tickets",
"comment": "Users ask for a faster path to first result",
"locations": [
{ "location_id": "onboarding/profile_step", "count": 9 },
{ "location_id": "onboarding/permissions_gate", "count": 5 }
],
"keywords": ["onboarding", "friction", "first value"]
}
]
}
```
## Extra Connectors
For `sources.extra[]`, the connector key becomes the source label in generated output.
Examples:
- `firebase_crashlytics`
- `app_store_reviews`
- `play_console`
Do not model GlitchTip as an extra connector when it exposes the Sentry-compatible API; use `sources.sentry.accounts[]`. Do not model ASC CLI as an extra connector in setup answers; it is the ASC / App Store Connect connector.
If your connector can already emit shared `signals[]`, use that shape. It is the least ambiguous path.
## ASC Analytics Payloads
The built-in ASC exporter can attach App Store Connect Analytics context under `meta.analytics`.
Use it for production growth/stability checks, not TestFlight crash triage.
Expected fields:
```json
{
"project": "app-store-connect:123456789",
"window": "latest",
"signals": [
{
"id": "asc_production_crashes_detected",
"area": "crash",
activepieces
AI Agents & MCPs & AI Workflow Automation • (~400 MCP servers for AI agents) • AI Automation / AI Agent with MCPs • AI Workflows & AI Agents • MCPs for AI Agents
cherry-studio
AI productivity studio with smart chat, autonomous agents, and 300+ assistants.
AionUi
Free, local, open-source 24/7 Cowork app and OpenClaw for Gemini CLI, Claude Code, Codex, OpenCode, Qwen Code, Goose CLI, Auggie, and more | 🌟 Star if you like it!
CopilotKit
The Frontend for Agents & Generative UI. React + Angular
Machine-readable data
The same record, as JSON, for agents and crawlers.
{
"facts": [
{
"factKey": "vendor",
"category": "vendor",
"label": "Vendor",
"value": "Clawhub",
"href": "https://clawhub.ai/wotaso-dev/skills/growth-engineer",
"sourceUrl": "https://clawhub.ai/wotaso-dev/skills/growth-engineer",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-09T05:49:34.051Z",
"isPublic": true
},
{
"factKey": "protocols",
"category": "compatibility",
"label": "Protocol compatibility",
"value": "OpenClaw",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-wotaso-dev-growth-engineer/contract",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-wotaso-dev-growth-engineer/contract",
"sourceType": "contract",
"confidence": "medium",
"observedAt": "2026-10-09T05:49:34.051Z",
"isPublic": true
},
{
"factKey": "traction",
"category": "adoption",
"label": "Adoption signal",
"value": "4.2K downloads",
"href": "https://clawhub.ai/wotaso-dev/growth-engineer",
"sourceUrl": "https://clawhub.ai/wotaso-dev/growth-engineer",
"sourceType": "profile",
"confidence": "medium",
"observedAt": "2026-10-09T05:49:34.051Z",
"isPublic": true
},
{
"factKey": "latest_release",
"category": "release",
"label": "Latest release",
"value": "1.0.210",
"href": "https://clawhub.ai/wotaso-dev/growth-engineer",
"sourceUrl": "https://clawhub.ai/wotaso-dev/growth-engineer",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-08-05T09:26:50.943Z",
"isPublic": true
},
{
"factKey": "handshake_status",
"category": "security",
"label": "Handshake status",
"value": "UNKNOWN",
"href": "https://www.xpersona.co/api/v1/agents/clawhub-wotaso-dev-growth-engineer/trust",
"sourceUrl": "https://www.xpersona.co/api/v1/agents/clawhub-wotaso-dev-growth-engineer/trust",
"sourceType": "trust",
"confidence": "medium",
"observedAt": null,
"isPublic": true
}
],
"events": [
{
"eventType": "release",
"title": "Release 1.0.210",
"description": "Version 1.0.210 - Migrated major script and source files from `.mjs` to `.mts` for improved TypeScript compatibility and maintainability. - Added new exporter and shared modules in `src/`, including analytics, ASC, Coolify, Paddle, RevenueCat, Sentry, SEO, feedback API, environment, preflight, status, start, and wizard logic. - Updated and expanded tests to align with new TypeScript modules and shared library improvements. - Removed deprecated/unused files (e.g., `skill-card.md`). - Updated package and documentation to reflect the new structure and maintain agent compatibility.",
"href": "https://clawhub.ai/wotaso-dev/growth-engineer",
"sourceUrl": "https://clawhub.ai/wotaso-dev/growth-engineer",
"sourceType": "release",
"confidence": "medium",
"observedAt": "2026-08-05T09:26:50.943Z",
"isPublic": true
}
]
}Record generated Oct 9, 2026.
