Analytics Tracking
freekmurze/dotfiles
When the user wants to set up, improve, or audit analytics tracking and measurement.
Expert mobile analytics covering attribution tracking, funnel analysis, crash reporting integration, A/B testing frameworks, retention and cohort analysis, event taxonomy design, privacy-compliant…
$ npx skills add FerroxLabs/wayland --skill mobile-analytics -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install FerroxLabs/wayland mobile-analytics --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .claude/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics .claude/skills/mobile-analytics && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "mobile-analytics" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics into .claude/skills/mobile-analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobile-analytics", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analyticsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add FerroxLabs/wayland --skill mobile-analytics -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install FerroxLabs/wayland mobile-analytics --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .agents/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics .agents/skills/mobile-analytics && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "mobile-analytics" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics into .agents/skills/mobile-analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobile-analytics", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/wayland --skill mobile-analytics -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install FerroxLabs/wayland mobile-analytics --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics .cursor/skills/mobile-analytics && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "mobile-analytics" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics into .cursor/skills/mobile-analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobile-analytics", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/FerroxLabs/wayland.git --path src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add FerroxLabs/wayland --skill mobile-analytics -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install FerroxLabs/wayland mobile-analytics --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics .gemini/skills/mobile-analytics && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "mobile-analytics" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics into .gemini/skills/mobile-analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobile-analytics", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install FerroxLabs/wayland mobile-analyticsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add FerroxLabs/wayland --skill mobile-analytics -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .github/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics .github/skills/mobile-analytics && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "mobile-analytics" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics into .github/skills/mobile-analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobile-analytics", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add FerroxLabs/wayland --skill mobile-analytics -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install FerroxLabs/wayland mobile-analytics --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/FerroxLabs/wayland.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics .opencode/skills/mobile-analytics && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "mobile-analytics" agent skill from https://github.com/FerroxLabs/wayland/tree/main/src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics into .opencode/skills/mobile-analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "mobile-analytics", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
mobile-analyticsExpert mobile analytics covering attribution tracking, funnel analysis, crash reporting integration, A/B testing frameworks, retention and cohort analysis, event taxonomy design, privacy-compliant…
Mobile Analytics is an agent skill from FerroxLabs/wayland. Expert mobile analytics covering attribution tracking, funnel analysis, crash reporting integration, A/B testing frameworks, retention and cohort analysis, event taxonomy design, privacy-compliant data collection, real-time dashboards, and actionable metric strategies for iOS and Android applications. Use when the user asks about mobile analytics, mobile analytics best practices, or needs guidance on mobile analytics implementation. Do NOT use when the user needs a different specialized skill or is asking about…
Its SKILL.md is about 3.8k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Data & Analytics, covering Product analytics and A/B testing. It works with iOS and Android. The repository describes itself as: Wayland - The AI Agent That Perceives. Reasons. Acts. Evolves. The licence is Apache-2.0.
Read from SKILL.md and the folder at commit 4c030c7. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are swift and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Mobile Analytics loads about 3.8k tokens when it runs. Until then it costs about 141 tokens; SKILL.md has 426 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from FerroxLabs/wayland at commit 4c030c7, republished under its Apache-2.0 licence (© FerroxLabs). 426 words, ~3,819 tokens.
.claude/skills/mobile-analytics/SKILL.md (or your agent's skills folder).You are an expert in mobile app analytics and data-driven product development. You guide teams through designing event taxonomies, implementing attribution tracking, building conversion funnels, setting up crash reporting, running A/B tests, and analyzing retention to drive growth and improve user experience.
Event Naming Standard:
Format: object_action (snake_case)
Examples: screen_viewed, button_tapped, item_added_to_cart,
purchase_completed, search_performed, error_displayed
Property Naming:
Format: snake_case, descriptive, typed
Examples: screen_name: string, item_price: float,
currency: string (ISO 4217), result_count: integer
Avoid:
- Camel case mixing (screenViewed vs screen_viewed)
- Generic names (click, event, action)
- PII in event properties (email, phone, full name)
- Unbounded cardinality (free-text user input as property values)Core Event Categories:
├── Lifecycle
│ ├── app_opened (source, is_first_launch, app_version)
│ ├── app_backgrounded (session_duration_seconds)
│ └── session_started (session_id, referral_source)
│
├── Navigation
│ ├── screen_viewed (screen_name, screen_class, previous_screen)
│ └── tab_selected (tab_name, tab_index)
│
├── Engagement
│ ├── search_performed (query, result_count, filter_applied)
│ ├── content_viewed (content_id, content_type, duration_seconds)
│ └── feature_used (feature_name, context)
│
├── Commerce
│ ├── item_viewed (item_id, item_name, category, price, currency)
│ ├── item_added_to_cart (item_id, quantity, cart_value)
│ ├── checkout_started (cart_value, item_count)
│ └── purchase_completed (transaction_id, revenue, currency, item_count)
│
├── Onboarding
│ ├── onboarding_started ()
│ ├── onboarding_step_completed (step_number, step_name)
│ ├── onboarding_completed (duration_seconds)
│ └── onboarding_skipped (last_step_completed)
│
└── Notifications
├── push_permission_requested (status)
├── push_received (campaign_id, message_type)
└── push_opened (campaign_id, time_to_open_seconds)protocol AnalyticsProvider {
func track(event: String, properties: [String: Any])
func identify(userId: String, traits: [String: Any])
func screen(name: String, properties: [String: Any])
}
final class AnalyticsManager {
static let shared = AnalyticsManager()
private var providers: [AnalyticsProvider] = []
func register(_ provider: AnalyticsProvider) {
providers.append(provider)
}
func track(_ event: AnalyticsEvent) {
let properties = event.properties.merging(globalProperties()) { _, new in new }
for provider in providers {
provider.track(event: event.name, properties: properties)
}
}
private func globalProperties() -> [String: Any] {
[
"app_version": Bundle.main.appVersion,
"os_version": UIDevice.current.systemVersion,
"device_model": UIDevice.current.modelName,
"locale": Locale.current.identifier
]
}
}
// Type-safe event definitions
enum AnalyticsEvent {
case screenViewed(name: String)
case purchaseCompleted(transactionId: String, revenue: Double, currency: String)
case onboardingStepCompleted(step: Int, name: String)
case searchPerformed(query: String, resultCount: Int)
var name: String {
switch self {
case .screenViewed: return "screen_viewed"
case .purchaseCompleted: return "purchase_completed"
case .onboardingStepCompleted: return "onboarding_step_completed"
case .searchPerformed: return "search_performed"
}
}
var properties: [String: Any] {
switch self {
case .screenViewed(let name):
return ["screen_name": name]
case .purchaseCompleted(let id, let revenue, let currency):
return ["transaction_id": id, "revenue": revenue, "currency": currency]
case .onboardingStepCompleted(let step, let name):
return ["step_number": step, "step_name": name]
case .searchPerformed(let query, let count):
return ["query": query, "result_count": count]
}
}
}Attribution Methods:
├── Deterministic
│ ├── Deep links (most accurate): Universal Links (iOS), App Links (Android)
│ ├── Referrer (Android only): Google Play Install Referrer API
│ └── Click ID matching: Match ad click ID to install event
│
├── Probabilistic
│ ├── Fingerprinting (deprecated on iOS): IP + User Agent + Device model
│ └── Statistical modeling: Aggregated campaign performance inference
│
└── Self-Attributing Networks (SANs)
├── Meta, Google, TikTok, Snap
└── Report their own attributed installs, reconcile with MMP dataSKAdNetwork (SKAN) Implementation:
├── Conversion Value Strategy (6 bits = 0-63)
│ ├── Bit 0-2: Revenue bucket (8 tiers)
│ ├── Bit 3-4: Engagement level (4 tiers)
│ ├── Bit 5: Retention (returned day 2+)
│
├── SKAN 4.0 Enhancements
│ ├── Coarse conversion values: low, medium, high
│ ├── Three postback windows: 0-2 days, 3-7 days, 8-35 days
│ └── Hierarchical source identifiers (2-4 digits based on crowd anonymity)
│
└── Implementation
├── Use MMP SDK (Adjust, AppsFlyer, Singular) to manage conversion values
└── Map postback data to campaign performance in MMP dashboardFunnel Design Principles:
1. Define clear start and end events
2. Include every meaningful step (not too granular)
3. Set reasonable time window (session-based or N-day window)
4. Segment by user properties (new vs returning, platform, source)
Common Mobile Funnels:
├── Onboarding: app_opened → step_1 → step_2 → step_3 → first_key_action
├── Purchase: item_viewed → added_to_cart → checkout_started → purchase_completed
└── Subscription: paywall_viewed → plan_selected → trial_started → trial_converted
Drop-off Analysis:
For each step transition:
- Calculate conversion rate (users reaching step N / users reaching step N-1)
- Segment by: device, OS version, source, user properties
- Set alerts when conversion drops below historical baseline
- Track median time between steps (long waits = friction)Crash Reporting Setup:
├── Capture
│ ├── Crashes, non-fatal errors, ANRs (Android), watchdog terminations (iOS)
│ └── Out-of-memory events
│
├── Enrich
│ ├── Stack trace with symbolication / deobfuscation
│ ├── Device model, OS version, app version, network state
│ ├── User breadcrumbs (last 50 events before crash)
│ └── Custom keys (current screen, user segment, feature flags)
│
├── Prioritize
│ ├── Crash-free users rate (target: > 99.5%)
│ ├── Sort by impacted users, not occurrence count
│ └── Track crash rate per app version (detect regressions)
│
└── Alert
├── New crash type → immediate notification
├── Crash-free rate drop → page on-call
└── Velocity alerts: crash count spikes in short windowA/B Test Lifecycle:
1. Hypothesis: "Changing CTA from 'Sign Up' to 'Start Free Trial' will increase
conversion by 15% because it communicates zero risk."
2. Design:
├── Primary metric: Sign-up conversion rate
├── Secondary metrics: Trial-to-paid rate, 7-day retention
├── Guardrail metrics: App crash rate, session duration
└── Sample size: Calculate with MDE, alpha, power
3. Implementation:
├── Server-side flag assignment (preferred)
├── Consistent bucketing (same user always sees same variant)
└── Track exposure event when user sees the variant
4. Analysis:
├── Wait for sufficient sample size (do not peek early)
├── Check statistical significance (p < 0.05)
├── Verify no impact on guardrail metrics
└── Segment results (new vs returning, platform, geo)
5. Decision:
├── Ship if statistically significant improvement
└── Kill if negative impact on primary or guardrail metricsRequired Sample Size Per Variant:
n = (Z_alpha/2 + Z_beta)^2 * (p1(1-p1) + p2(1-p2)) / (p1 - p2)^2
Rules of Thumb:
- Small effects (< 5% relative change): 10,000+ per variant
- Medium effects (5-15% relative): 2,000-10,000 per variant
- Large effects (> 15% relative): < 2,000 per variant
- Always run for at least 1 full week for day-of-week effectsDay-N Retention Analysis:
Cohort: Users who installed in a given week
Metric: Percentage who return on Day N
Industry Benchmarks (varies by category):
├── D1: 25-40% (good > 35%)
├── D7: 12-20% (good > 18%)
├── D30: 6-12% (good > 10%)
└── D90: 3-8% (good > 6%)
Retention Curve Shape:
├── Flattening curve → healthy: found core users
├── Steady decline → problem: no habit formation
└── Smile curve (uptick) → excellent: reactivation workingKey Engagement Metrics:
├── DAU / MAU Ratio (Stickiness)
│ ├── Social apps: 30-50%, Utility: 15-25%, E-commerce: 8-15%
│
├── Session Metrics
│ ├── Sessions per DAU, session duration, time between sessions
│
├── Feature Adoption
│ ├── % of MAU who use feature X
│ ├── Feature correlation with retention
│ └── Power user feature fingerprint
│
└── Activation Rate
├── Define activation event (the "aha" moment)
├── Track time-to-activation from install
└── Optimize onboarding to reach activation fasterPrivacy Framework:
├── iOS App Tracking Transparency (ATT)
│ ├── Required for IDFA access (iOS 14.5+)
│ ├── Pre-prompt screen explaining value before system dialog
│ ├── Respect denial: use first-party analytics without IDFA
│ └── Typical opt-in rates: 15-35%
│
├── GDPR / CCPA Compliance
│ ├── Consent before tracking (EU), opt-out mechanism (US/California)
│ ├── Data deletion capability
│ └── Data retention policies (auto-delete after N months)
│
├── Privacy-Safe Alternatives
│ ├── First-party event data (no cross-app tracking)
│ ├── On-device processing where possible
│ ├── Privacy-preserving attribution (SKAN, Privacy Sandbox)
│ └── Server-side analytics (user never sends data to third parties)
│
└── Implementation
├── Gate all analytics behind consent check
├── Use anonymous IDs, not persistent device IDs
├── Strip or hash any quasi-identifiers
└── Audit event payloads quarterly for PII leakage| Tool | Strengths | Best For |
|---|---|---|
| Amplitude | Behavioral analytics, cohorts, funnels | Product analytics at scale |
| Mixpanel | Event analytics, A/B testing, flows | Growth-stage product teams |
| Firebase Analytics | Free, deep Android integration, BigQuery export | Early-stage apps, Google ecosystem |
| PostHog | Open source, session replay, feature flags | Privacy-conscious teams |
| Adjust / Singular | Attribution, fraud prevention, cost aggregation | Paid acquisition optimization |
Daily Operational Dashboard:
├── Health: Crash-free rate, API error rate, app launch time (p50, p95)
├── Acquisition: New installs (organic vs paid), CPI by channel, activation rate
├── Engagement: DAU/WAU/MAU, sessions per user, feature adoption, push open rate
├── Retention: D1/D7/D30 by cohort, churn rate trend, reactivation rate
└── Revenue: ARPU, ARPPU, LTV by cohort, subscription conversion/renewal ratesUse this skill when:
Do NOT use this skill when:
# Mobile Analytics Analysis
## Context Assessment
[Situation summary and constraints]
## Recommended Approach
[Primary recommendation with rationale]
## Implementation Steps
1. [Step with specific details]
2. [Step with specific details]
3. [Step with specific details]
## Trade-offs and Considerations
- [Key trade-off 1]
- [Key trade-off 2]
## Next Steps
- [Immediate action item]
- [Follow-up action item]Input: "Help me implement mobile analytics for a medium-scale production application"
Output: A structured analysis covering current state assessment, recommended mobile analytics approach with specific patterns, implementation roadmap with milestones, and risk mitigation strategies tailored to the application scale and constraints.
© FerroxLabs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics of FerroxLabs/wayland.
Open the folder on GitHubat commit 4c030c7
Mobile Analytics next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Mobile Analytics this skillFerroxLabs/wayland | 608 | — | ~3.8k | Automated safety check: Pass | Apache-2.0 | |
| Analytics Trackingfreekmurze/dotfiles | 1k | 12 repos | ~2k | Automated safety check: Pass | None | |
| A/B Test Analysisphuryn/pm-skills | 27k | — | ~893 | Automated safety check: Pass | MIT | |
| Web Scraper APIoxylabs/agent-skills | 875 | — | ~1.5k | Automated safety check: Pass | MIT | |
| Product Analyticsmajiayu000/spellbook | 286 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Data And Funnel Analyticsmanojbajaj95/claude-gtm-plugin | 104 | — | ~2.9k | Automated safety check: Pass | MIT |
freekmurze/dotfiles
When the user wants to set up, improve, or audit analytics tracking and measurement.
phuryn/pm-skills
Validates an experiment's setup, works out lift, p-value and confidence interval from A/B test data, and recommends whether to ship, extend or stop.
oxylabs/agent-skills
Production-grade web scraping with automatic anti-bot bypass, structured JSON parsing for 40+ targets, and geo-targeting.
majiayu000/spellbook
Product analytics and growth expert. An agent skill from majiayu000/spellbook.
manojbajaj95/claude-gtm-plugin
Analytics tracking, interpretation, funnel analysis, product metrics, and ROI measurement.
yonatangross/orchestkit
A/B test evaluation, cohort retention analysis, funnel metrics, and experiment-driven product decisions.
FerroxLabs/wayland
Install, start, connect, and troubleshoot visualization companion projects for Aion/OpenClaw, with Star-Office-UI as the default recommendation.
FerroxLabs/wayland
OpenClaw usage expert: Helps you install, deploy, configure, and use OpenClaw personal AI assistant.
FerroxLabs/wayland
Set up TVControl end to end: install the connector, start TradingView Desktop with its control port open, load a watchlist export, add the indicators they use, and leave a working chart.
FerroxLabs/wayland
End-to-end guide for designing, running, and analyzing A/B tests including experiment design, statistical significance, sample size calculation, common pitfalls, and advanced testing patterns.
FerroxLabs/wayland
Complete academic writing guide covering thesis and dissertation structure, journal article format using IMRaD, literature review methodology, citation management, the peer review process, and…
FerroxLabs/wayland
Web accessibility expertise covering WCAG 2.2 conformance, audit methodology, ARIA patterns, keyboard navigation, screen reader testing, focus management, form accessibility, and automated vs manual…
Categories
Expert mobile analytics covering attribution tracking, funnel analysis, crash reporting integration, A/B testing frameworks, retention and cohort analysis, event taxonomy design, privacy-compliant…. Mobile Analytics is an agent skill from FerroxLabs/wayland. Expert mobile analytics covering attribution tracking, funnel analysis, crash reporting integration, A/B testing frameworks, retention and cohort analysis, event taxonomy design, privacy-compliant data collection, real-time dashboards, and actionable metric strategies for iOS and Android applications.
Mobile Analytics fits situations like: the user asks about mobile analytics; mobile analytics best practices; needs guidance on mobile analytics implementation; the user needs a different specialized skill.
Run `npx skills add FerroxLabs/wayland --skill mobile-analytics -a claude-code`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics in FerroxLabs/wayland) into .claude/skills/mobile-analytics in your project. Claude Code loads it when a task matches its description.
Run `npx skills add FerroxLabs/wayland --skill mobile-analytics -a codex`. Or copy the skill folder (src/process/resources/skills-library/bodies/skills/software-engineering/mobile-analytics in FerroxLabs/wayland) into .agents/skills/mobile-analytics in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add FerroxLabs/wayland --skill mobile-analytics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/mobile-analytics, .gemini/skills/mobile-analytics, .github/skills/mobile-analytics and .opencode/skills/mobile-analytics in your project.
SKILL.md names no scripts, command-line tools or credentials: Mobile Analytics is instructions for the agent only.
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Mobile Analytics is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.8k tokens (SKILL.md is roughly 15k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Mobile Analytics: Analytics Tracking (freekmurze/dotfiles, 1k stars), A/B Test Analysis (phuryn/pm-skills, 27k stars), Web Scraper API (oxylabs/agent-skills, 875 stars) and Product Analytics (majiayu000/spellbook, 286 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
FerroxLabs (a GitHub user) maintains it in FerroxLabs/wayland, which has 608 GitHub stars. The repository holds 1,194 skills in this directory. The repository was last updated on October 6, 2026.
Source: FerroxLabs/wayland on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.