What are the priority tiers for instrumentation?

The skill suggests five tiers: Errors (T1), Core Web Vitals (T2), User Context (T3), Route/API Tracing (T4), and Business Metrics (T5).

Does this skill support OpenTelemetry standards?

Yes, it enforces OTel-compatible naming conventions for HTTP requests and URL paths to ensure your data is compatible with standard observability backends.

How does it prevent measurement noise?

It includes specific guidance on anti-patterns, such as measuring too much (which leads to bundle bloat) and ensuring PII is excluded from breadcrumbs.

Is this skill specific to a single framework?

No, while part of a web-observability repository, the planning logic applies to all modern web frameworks including React, Vue, and Svelte.

How does this skill help with Core Web Vitals?

It provides specific thresholds for LCP, INP, and CLS, along with a tier-based plan to implement monitoring for these critical performance metrics from day one.

Web Instrumentation Planning

Name: Web Instrumentation Planning
Author: nexus-labs-automation

bynexus-labs-automation

0•

Analytics & Monitoring

Plans comprehensive observability strategies for web applications by prioritizing metrics, errors, and user performance signals.

This skill provides a strategic framework for implementing observability in web applications, guiding developers through the prioritization of telemetry data from Day 1 error tracking to long-term business metrics. It leverages OpenTelemetry (OTel) naming conventions and the Jobs-to-be-Done framework to ensure monitoring efforts focus on user outcomes, Core Web Vitals, and actionable error context while avoiding common anti-patterns like measurement noise and bundle bloat.

Key Features

01Core Web Vitals threshold guidance (LCP, INP, CLS)

02OpenTelemetry (OTel) compatible naming convention standards

03Jobs-to-be-Done (JTBD) framework for user journey tracking

04Best practices for error tracking and source map integration

05Strategic 5-tier instrumentation roadmap for progressive implementation

060 GitHub stars

Use Cases

01Prioritizing instrumentation tasks during a performance optimization sprint

02Standardizing telemetry naming conventions for better data portability

03Defining the observability roadmap for a new React, Vue, or Svelte project

What are Skills?·How to Install

Install with 🐟 Skill.Fish

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

For use in Claude.ai and ChatGPT

Download Skill