SkillsAdd

smithery/nexus-labs-automation

instrumentation-planning

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

Installation

$ npx skills add smithery/nexus-labs-automation --skill instrumentation-planning
View on skills.sh ↗ Website ↗

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

vercel-react-native-skills Shared topics
vercel-labs/agent-skills 205.5K installs
firebase-data-connect Shared topics
firebase/agent-skills 142.2K installs
appinsights-instrumentation Similar name
microsoft/azure-skills

Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns…

566.6K installs
appinsights-instrumentation Similar name
github/awesome-copilot

Instrument a webapp to send useful telemetry data to Azure App Insights

9.6K installs
posthog-instrumentation Similar name
posthog/posthog-for-claude

Automatically add PostHog analytics instrumentation to code. Triggers when user asks to add tra…

1.8K installs
arize-instrumentation Similar name
github/awesome-copilot

Adds Arize AX tracing to an LLM application for the first time.

1.1K installs

Also in this package

Other skills from smithery/nexus-labs-automation · top by installs.

npx skills add smithery/nexus-labs-automation
user-journey-tracking 0 token-cost-tracking 0 symbolication-setup 0 route-transition-tracking 0 prompt-versioning 0 network-tracing 0 navigation-latency 0 health-checks 0 error-retry-tracking 0 decision-tracing 0

Browse all from smithery/nexus-labs-automation

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,073 B
  • docs SUMMARY.md 164 B

History

  1. First recorded snapshot · 0 installs

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)