Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Track mobile app metrics with Firebase, App Store Connect, Play Console, retention, funnels, and cohort analysis.
Track mobile app metrics with Firebase, App Store Connect, Play Console, retention, funnels, and cohort analysis.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
On first use, read setup.md for integration guidelines. Create ~/mobile-app-analytics/ if it doesn't exist.
User needs to track, analyze, or optimize mobile app performance metrics. Agent handles Firebase Analytics queries, App Store Connect data, Play Console reports, retention analysis, funnel debugging, and cohort comparisons.
Memory lives in ~/mobile-app-analytics/. See memory-template.md for setup. ~/mobile-app-analytics/ ├── memory.md # Apps tracked, goals, alerts ├── apps/ # Per-app analytics configs │ └── {app-name}.md # Events, funnels, KPIs per app └── benchmarks.md # Industry benchmarks reference
TopicFileSetup processsetup.mdMemory templatememory-template.mdFirebase Analyticsfirebase.mdApp Store Connectapp-store.mdPlay Consoleplay-console.mdCore metricsmetrics.md
Detect from context which platform(s) the app targets: iOS only → focus on App Store Connect + Firebase Android only → focus on Play Console + Firebase Cross-platform → cover both stores + unified Firebase
Always prioritize metrics in this order: Revenue metrics (LTV, ARPU, conversion) — what pays the bills Retention metrics (D1, D7, D30) — determines long-term success Engagement metrics (DAU/MAU, session length) — leading indicators Acquisition metrics (installs, sources) — growth levers
Never report aggregate numbers alone. Always segment by: Install cohort (when users joined) Acquisition source (organic, paid, referral) User tier (free, trial, paid) Platform (iOS vs Android)
Proactively flag anomalies: MetricAlert ifD1 retention< 25% (below industry floor)Crash-free rate< 99%DAU/MAU ratioDrops > 10% week-over-weekLTV:CAC ratio< 3:1
Know platform data delays: SourceTypical DelayFirebase real-timeMinutesFirebase daily reports24-48h for full dataApp Store Connect24-48hPlay Console24-48h
Never track PII in custom events Respect ATT (iOS) and consent requirements User properties: demographics OK, personal identifiers NOT OK GDPR: support data deletion requests
Vanity metrics obsession → Total downloads means nothing; track active users and retention instead Ignoring platform differences → iOS users often have 20-30% higher LTV; don't merge data blindly Wrong attribution window → 7-day attribution misses subscription conversions; use 30-day for subscriptions Survivorship bias → Analyzing only current users ignores why churned users left Timezone mismatches → Firebase uses UTC by default; App Store uses your configured timezone
EndpointData SentPurposeFirebase Analytics APIApp ID, date rangeFetch metricsApp Store Connect APIApp ID, credentialsiOS analyticsPlay Console APIApp ID, credentialsAndroid analytics No other data is sent externally.
Data that leaves your machine: Analytics queries to Firebase/Apple/Google APIs when you provide credentials Data that stays local: Your tracked apps and goals in ~/mobile-app-analytics/ Benchmark comparisons and notes This skill does NOT: Store credentials (use your platform's standard credential methods) Access files outside ~/mobile-app-analytics/ Make requests to undeclared endpoints
This skill ONLY: Provides guidance on mobile app analytics platforms Stores your app configurations in ~/mobile-app-analytics/ Queries Firebase, App Store Connect, and Play Console when you provide credentials This skill NEVER: Stores credentials in files (use environment variables) Accesses files outside ~/mobile-app-analytics/ Makes requests to undeclared endpoints Modifies global agent memory or other skills
Install with clawhub install <slug> if user confirms: app-store-connect — iOS App Store management flutter — Cross-platform app development saas — SaaS business metrics and growth
If useful: clawhub star mobile-app-analytics Stay updated: clawhub sync
Data access, storage, extraction, analysis, reporting, and insight generation.
Largest current source with strong distribution and engagement signals.