Does this skill support both Android and iOS?

Yes, it provides platform-agnostic strategic guidance suitable for iOS, Android, and cross-platform frameworks like React Native.

What is the Jobs-to-be-Done framework in this context?

It focuses on measuring specific user goals (jobs) to determine completion rates, duration, and friction points rather than just tracking random events.

How does it help with OpenTelemetry migration?

It suggests OTel-compatible span and attribute names from the start, ensuring your telemetry data is standardized and easier to migrate to modern backends later.

Can this skill help reduce app battery drain?

Yes, by identifying anti-patterns like 'measuring everything,' it helps you focus on high-value metrics that don't unnecessarily consume device resources.

What are the priority tiers for instrumentation?

The skill organizes tracking into five tiers: 1. Crashes & errors, 2. User context, 3. Performance, 4. Breadcrumbs, and 5. Business metrics.

Instrumentation Planning

Name: Instrumentation Planning
Author: nexus-labs-automation

bynexus-labs-automation

•

Mobile Development

Provides strategic guidance for mobile app observability using the Jobs-to-be-Done framework and OpenTelemetry standards.

About

The Instrumentation Planning skill empowers developers to strategically determine what to track in mobile applications by leveraging a tiered priority system and the Jobs-to-be-Done framework. It helps avoid common pitfalls like over-instrumentation and performance bottlenecks while ensuring telemetry is future-proofed through OTel-compatible naming conventions. This skill is essential for teams looking to implement structured observability across iOS, Android, and React Native platforms, guiding you from initial crash reporting to advanced business metric tracking.

Key Features

98 GitHub stars
Jobs-to-be-Done (JTBD) telemetry framework integration
Identification of common mobile telemetry anti-patterns
Implementation roadmap from Day 1 to Month 1
5-tier instrumentation priority hierarchy
OpenTelemetry (OTel) compatible naming convention guidance

Use Cases

Auditing existing telemetry to reduce noise and improve data quality
Prioritizing observability tasks for a new mobile application launch
Standardizing naming conventions across cross-functional mobile teams

What are Skills?·How to Install

Install with 🐟 Skill.Fish

npx skillfish add nexus-labs-automation/mobile-observability instrumentation-planning

For use in Claude.ai and ChatGPT

Download Skill

GitHub