add-catch-error
Add custom error handling with catchError to a mix() call for logging, error conversion, or suppression
Add custom error handling with catchError to a mix() call for logging, error conversion, or suppression
Use when 你已经确定了 Discover 的范围(P0/P1/P2),现在需要快速建立 `.aisdlc/project/` 的 Level-0 北极星(memory)与 Level-1 地图层索引骨架(components/products),以便后续按模块补证据而不发生双写与漂移。
Help new users get started with MetaClaw - setup wizard, first steps, and guided configuration
Enable and configure Claude Code OTEL telemetry for local or Railway observability stacks. Use when setting up Claude Code to send metrics, logs, and traces to observability backends.
EKS observability with metrics, logging, and tracing. Use when setting up monitoring, configuring logging pipelines, implementing distributed tracing, building production dashboards, troubleshooting EKS issues, optimizing observability costs, or establishing SLOs.
Gating CI on perf regressions. Automated threshold alerts, baseline tracking, trend reports.
Adding observability. OpenTelemetry traces/metrics/logs, health checks, custom metrics.
Track and analyze usage metrics with timestamped logging, reporting, and trend detection
Sub-skill of orcaflex-line-wizard: YAML-Based Line Setup (+1).
Guide for adding new semantic conventions to OpenTelemetry semantic-conventions repositories using the YAML model + Weaver toolchain. Use when adding new attributes, spans, metrics, events, or resources to a semconv project, creating new area conventions, or editing model/*.yaml and docs/*.md files in semantic-conventions repos.
Sub-skill of orcaflex-line-wizard: Before Using Line Setup Wizard (+2).
Sub-skill of marp: 2. Frontmatter Configuration (+4).
Observability stack with Prometheus, Grafana, and alerting.
Choose the right metrics for a LaunchDarkly experiment, guarded rollout, or release policy. Use when the user wants to know which metrics to use, which is the primary metric for an experiment, what guardrails to add, or which events to monitor in a rollout. Surfaces what will auto-attach from existing release policies before making additional recommendations.
Instrument a LaunchDarkly metric event in a codebase by adding a track() call. Use when the user wants to wire up an event, instrument an action for a metric, add tracking to a feature, or confirm that an event is flowing to LaunchDarkly.
Create new openrappter skills with proper SKILL.md format and metadata.
Observability and monitoring patterns including logging, metrics, distributed tracing, alerting, and monitoring stack setup. Use when setting up monitoring, implementing logging strategies, configuring alerts, or debugging production issues.
Set up APM instrumentation and log shipping — framework-specific agents, Filebeat, Elastic Agent, and correlation.
Implements comprehensive observability with OpenTelemetry tracing, Prometheus metrics, and structured logging. Includes instrumentation plans, sample dashboards, and alert candidates. Use for "observability", "monitoring", "tracing", or "metrics".
OpenTelemetry - vendor-neutral observability framework for distributed systems. Provides traces, metrics, and logs with standardized instrumentation and exporters. USE WHEN: user mentions "opentelemetry", "otel", "distributed tracing", "observability", asks about "how to trace microservices", "opentelemetry setup", "jaeger integration", "prometheus metrics" DO NOT USE FOR: Application logging only - use logging skills instead, APM vendor-specific - use vendor docs, Simple monitoring - Prometheus/Grafana may be sufficient
Production server monitoring stack covering Prometheus, Node Exporter, Grafana, Alertmanager, Loki, and Promtail on bare-metal or VM Linux hosts. USE WHEN: - Setting up monitoring for a new production server or VPS - Configuring Prometheus scrape targets for application or system metrics - Creating Grafana dashboards and datasource provisioning - Writing Alertmanager routing rules with email/Slack notifications - Implementing the PLG stack (Promtail + Loki + Grafana) for log aggregation - Performing live system diagnostics with htop, iotop, nethogs, ss, vmstat, iostat - Setting up uptime monitoring with UptimeRobot or healthchecks.io DO NOT USE FOR: - Kubernetes-native observability (use the kubernetes skill instead) - Application-level APM (distributed tracing with Jaeger/Tempo — use observability skill) - Cloud-managed monitoring (CloudWatch, GCP Monitoring, Azure Monitor) - Windows Server monitoring
OpenTelemetry SDK initialization and configuration. Use when setting up or reviewing TracerProvider, MeterProvider, or LoggerProvider; choosing exporters, processors, or propagators; configuring OTLP transport; or extending an existing SDK setup for new signals. Use this skill whenever the task involves wiring up the OpenTelemetry SDK, even if the user only mentions "add tracing" or "set up metrics" without saying "SDK."