queue-observability
Monitor message queues, job processing, and detect backpressure
Browse published AI skills maintained by nexus-labs-automation. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
42Repository stars across indexed skills
850Repository forks
80Average repository stars per indexed skill
20Repository stars may repeat across skills from the same repository.
Monitor message queues, job processing, and detect backpressure
Plan backend observability using RED + USE + 4 Golden Signals + JTBD
Define SLIs, SLOs, and implement burn-rate alerting
Capture errors with rich context for debugging and alerting
Instrument HTTP/gRPC endpoints with distributed tracing and RED metrics
Track cache hit rates, latency, and detect cache-related issues
This skill should be used when the user asks to "write playwright test", "e2e test", "playwright locator", "test isolation", "page object", or needs guidance on Playwright E2E testing patterns, locator strategi...
Measure and optimize Core Web Vitals (LCP, INP, CLS). Use when implementing CWV tracking or debugging performance.
Set up error tracking with actionable context. Use when configuring error capture or error boundaries.
Instrument API requests with spans and distributed tracing. Use when tracking request latency or debugging API issues.
Set up session replay for visual debugging. Use when implementing DOM recording with privacy controls.
Set up synthetic monitoring with Lighthouse CI and Playwright. Use when implementing automated performance testing, CI/CD performance gates, or proactive monitoring.
Measure SSR hydration timing and issues. Use when tracking hydration performance, debugging hydration mismatches, or optimizing SSR/SSG applications.
Measure time from navigation to page fully loaded and interactive. Use when tracking SPA navigation, route changes, or slow page transitions.
Track user journeys with intent context and friction signals. Use when instrumenting funnels or multi-step flows.
Monitor JavaScript bundle size and execution performance. Use when tracking bundle size, identifying large chunks, or optimizing load performance.
Configure source maps for readable stack traces. Use when setting up error tracking, debugging production issues, or configuring build tools.
Plan what to measure in web applications. Use when starting observability or prioritizing instrumentation.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.