Agent skill

instrumentation-planning

Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?"

View SKILL.md on GitHub Repository
Stars 108
Forks 11

Install this agent skill to your Project

npx add-skill https://github.com/nexus-labs-automation/mobile-observability/tree/main/skills/instrumentation-planning

SKILL.md

Instrumentation Planning

Strategic guidance for what to measure using Jobs-to-be-Done framework.

Core Question

For each user job, ask:

  • Did it complete? → completion rate
  • How long? → duration (p50, p95, p99)
  • What failed? → error type, context
  • Did they give up? → drop-off rate

Priority Tiers

Tier Focus Examples
1 Crashes & errors Crash reporting, error boundaries
2 User context User ID, session ID, device info
3 Performance App start, screen load, network
4 Breadcrumbs Navigation, user actions
5 Business metrics Funnels, feature usage

Implementation Order

Day 1:  Crash reporting + User context
Week 1: Breadcrumbs + Release tracking
Week 2: Performance spans
Month 1: Business metrics

Future-Proofing

Use OTel-compatible span/attribute names now (zero cost, easier migration later):

  • http.request.method not method
  • ui.screen.load not screenLoad
  • app.start.cold not coldStart

See references/otel-mobile.md for full naming conventions.

Anti-Patterns

  • Measure everything (noise, battery drain)
  • Skip symbolication (unreadable crashes)
  • Block main thread for telemetry
  • Log PII in breadcrumbs

Implementation

See references/instrumentation-patterns.md for:

  • Detailed 5-tier checklist
  • Span naming conventions
  • Sampling strategies
  • Testing checklist

See references/jtbd.md for full Jobs-to-be-Done framework.

Related Skills

  • See skills/user-journey-tracking for implementing JTBD instrumentation
  • See skills/crash-instrumentation for Tier 1 (crashes)
  • See skills/symbolication-setup for Tier 1 (readable stack traces)

Recommended Agent Skills

Expand your agent's capabilities with these related and highly-rated skills.

nexus-labs-automation/mobile-observability

symbolication-setup

Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or source maps (React Native).

108 11
Explore
nexus-labs-automation/mobile-observability

network-tracing

Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces, or debugging API issues.

108 11
Explore
nexus-labs-automation/mobile-observability

crash-instrumentation

Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb strategies.

108 11
Explore
nexus-labs-automation/mobile-observability

user-journey-tracking

Track user journeys with intent context and friction signals. Use when instrumenting onboarding, checkout, or any multi-step flow where you need to understand WHY users fail.

108 11
Explore
nexus-labs-automation/mobile-observability

navigation-latency

Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab switches.

108 11
Explore
nexus-labs-automation/mobile-observability

interaction-latency

Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any tap-triggered operation.

108 11
Explore

Didn't find tool you were looking for?

Be as detailed as possible for better results