agentsclimarketplace
Sign in

Instrumentation planning

Skill nexus-labs-automation/mobile-observability/skills/instrumentation-planning

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

Install
npx -y skills add nexus-labs-automation/mobile-observability --skill instrumentation-planning

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

2.0 KB, as published. Nobody here has run it

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

TierFocusExamples
1Crashes & errorsCrash reporting, error boundaries
2User contextUser ID, session ID, device info
3PerformanceApp start, screen load, network
4BreadcrumbsNavigation, user actions
5Business metricsFunnels, 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)

Keep looking

Skills are one crate of 627,801. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.