crash-instrumentation
Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb…
Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?
$ npx -y skills add nexus-labs-automation/mobile-observability --skill instrumentation-planning --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/instrumentation-planningContext preview
The summary Claude sees to decide when to auto-load this skill.
Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?
name: instrumentation-planning description: Plan what to measure in mobile apps. Use when starting observability, prioritizing instrumentation, or asking "what should I track?" triggers: - "planning telemetry" - "prioritize instrumentation" - "start observability" - "what should I track" - "what to measure" - "where to begin" priority: 1
Strategic guidance for what to measure using Jobs-to-be-Done framework.
For each user job, ask:
| 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 |
Day 1: Crash reporting + User context Week 1: Breadcrumbs + Release tracking Week 2: Performance spans Month 1: Business metrics
Use OTel-compatible span/attribute names now (zero cost, easier migration later):
See `references/otel-mobile.md` for full naming conventions.
See `references/instrumentation-patterns.md` for:
See `references/jtbd.md` for full Jobs-to-be-Done framework.
Teaches Claude how to instrument mobile apps correctly — what to measure, what context to attach, and what mistakes to avoid.
Set up crash instrumentation with actionable context. Use when configuring crash capture, error boundaries, or breadcrumb…
Measure time from user tap to action completion. Use when tracking button response times, form submissions, add-to-cart, or any…
Measure time from navigation tap to screen fully loaded and interactive. Use when tracking screen transitions, deep links, or tab…
Instrument API requests with spans and distributed tracing. Use when tracking request latency, correlating client-backend traces,…
Set up session replay for visual debugging. Use when implementing screen recording, replay features, or visual debugging tools.
Configure crash symbolication for readable stack traces. Use when setting up dSYMs (iOS), ProGuard/R8 mappings (Android), or…