76 件 ・ 関連度順
概要と使いどころ
Design observability strategies: SLI/SLO frameworks, alerting, and dashboards. Use when instrumenting a production service, tuning alert rules, designing Grafana dashboards, defining SLOs and error budgets, or reducing alert fatigue.
日本語の概要は準備中です。原文の説明を表示しています。
Expert knowledge for Azure Container Storage development including troubleshooting, decision making, limits & quotas, security, and configuration. Use when configuring Elastic SAN-backed pools, CMK encryption, LRS/ZRS redundancy, volume resizing, or Prometheus/Grafana monitoring, and other Azure Container Storage related development tasks. Not for Azure Blob Storage (use azure-blob-storage), Azure Files (use azure-files), Azure Elastic SAN (use azure-elastic-san), Azure NetApp Files (use azure-netapp-files).
日本語の概要は準備中です。原文の説明を表示しています。
Structured logging with Pino/Winston, OpenTelemetry tracing, metrics collection, Grafana dashboards, and alerting rules.
日本語の概要は準備中です。原文の説明を表示しています。
PromQL queries, alerting rules, recording rules, Grafana dashboard JSON, SLO
日本語の概要は準備中です。原文の説明を表示しています。
Monitoring, logging, and tracing implementation using OpenTelemetry as the unified standard. Use when building production systems requiring visibility into performance, errors, and behavior. Covers OpenTelemetry (metrics, logs, traces), Prometheus, Grafana, Loki, Jaeger, Tempo, structured logging (structlog, tracing, slog, pino), and alerting.
日本語の概要は準備中です。原文の説明を表示しています。
Generate LogQL queries, log stream selectors, metric queries, and alerting rules for Grafana Loki.
日本語の概要は準備中です。原文の説明を表示しています。
Observability and SRE expert. Use when setting up monitoring, logging, tracing, defining SLOs, or managing incidents. Covers Prometheus, Grafana, OpenTelemetry, and incident response best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Define, track, and act on QA metrics: test coverage percentage, flakiness rate, defect escape rate, MTTR, test execution time trends, automation ROI, quality gates, and SLAs for test suites. Includes metric formulas, realistic targets by company stage, and the action to take when each metric goes red. Use when: "QA metrics," "test metrics," "quality KPIs," "test health," "flakiness rate," "defect escape rate." Not for: building the dashboard UI (Allure/Grafana) — use qa-dashboard; measuring coverage gaps and mutation score — use coverage-analysis. Related: qa-dashboard, coverage-analysis, ci-cd-integration, release-readiness, quality-postmortem.
日本語の概要は準備中です。原文の説明を表示しています。
OpenStack monitoring operations skill for deploying, configuring, and operating the cloud health monitoring stack. Covers Prometheus metric collection and scrape targets, Grafana dashboard provisioning and visualization, Alertmanager notification channels and routing, alerting rules for service health and resource exhaustion, service endpoint health checks, log aggregation strategies, SLA tracking with availability and response time percentiles, and capacity trend analysis from historical metrics. Use when deploying monitoring via Kolla-Ansible, configuring alert thresholds, troubleshooting blank dashboards, tuning noisy alerts, or analyzing cloud performance trends.
日本語の概要は準備中です。原文の説明を表示しています。
Automatic init the first time Claude acts in an incident or alerts channel — one named like #inc-…, #incident-…, #sev0-…/#sev1-…, or whose recent messages are pages or alerts from PagerDuty, Opsgenie, incident.io, Datadog, Sentry or Grafana, or relayed by people (talk about being paged is not an alert) — that isn't already a team's oncall / monitoring channel. Run once per channel, on first contact (just invited, first @-mention, channel just created), before doing what was asked: load the oncall memory oncall setup wrote to shared workspace memory, pick the owning team's section, work out which monitoring / paging / code tools Claude can reach and which are missing, post one short zero-context message, note findings in this channel's memory, then hand off to `incident-investigate` if something was asked — or immediately, unasked, when the channel was plainly opened for a live outage. Works with no oncall memory (offers setup once). Also on "load the oncall setup here" / "init this incident".
日本語の概要は準備中です。原文の説明を表示しています。
配置监控和告警时使用。适用于 Prometheus / Grafana / Loki / PagerDuty / SLO 定义 / 告警规则设计。融合 Google SRE 四大黄金信号 + USE Method + 告警分级。
日本語の概要は準備中です。原文の説明を表示しています。
实现日志 / 指标 / 追踪三大支柱时使用。覆盖 OpenTelemetry / Prometheus / Grafana / Jaeger / Datadog / Sentry 集成。融合 Google SRE 三支柱 + 结构化日志 + Trace Context 传播。
日本語の概要は準備中です。原文の説明を表示しています。
Post-deploy observability for production services — structured logging, RED metrics + Prometheus, Grafana dashboards, SLO-based alerting. Use when setting up monitoring or instrumenting a live service. Trigger on "add logging", "metrics", "dashboard", "alerting", "observability", "monitor this service".
日本語の概要は準備中です。原文の説明を表示しています。
Install Tilt and scaffold or audit Tiltfile + tilt/ configurations with ecosystem-aware templates. Auto-detects Java/Gradle (Spring Boot), Next.js, Python/uv, and external infrastructure; recommends single-file or modular tilt/*.star + service-config.yaml + environments.yaml patterns based on project complexity. Bakes in production-context safety guards, PVC persistence toggles, JDWP debug ports, and optional Prometheus/Grafana/Traefik scaffolds. Use when user runs /devtools:tilt-setup, mentions "tilt setup", "setup tilt", "scaffold tiltfile", "audit tiltfile", "tilt configure", "tilt project setup", "Tiltfile", "local kubernetes dev", or "kubernetes development environment".
日本語の概要は準備中です。原文の説明を表示しています。
Set up application observability with Prometheus, Grafana, Datadog, or CloudWatch — instrument metrics endpoints, configure Golden Signal dashboards, define alert rules with burn-rate SLOs, and add structured logging
日本語の概要は準備中です。原文の説明を表示しています。
Generate a production-grade OEE (Overall Equipment Effectiveness) measurement pipeline for a manufacturing line — data ingestion from MQTT/OPC-UA/Modbus/CSV, A×P×Q calculation engine, Six Big Losses categorizer, MTBF/MTTR/TEEP metrics, Grafana or Streamlit dashboard.
日本語の概要は準備中です。原文の説明を表示しています。
Build monitoring dashboards that answer real operator questions for Grafana, SigNoz, and similar platforms. Use when turning metrics into a working dashboard instead of a vanity board.
日本語の概要は準備中です。原文の説明を表示しています。
Structured logging conventions for DraftForge backend (Django/Celery/Daphne) and frontend (React). This skill should be used when adding log statements, creating new modules, debugging with logs, or reviewing logging patterns. Covers structlog usage, system/subsystem taxonomy, required fields, log levels, and Grafana query patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Review approved Grafana business-intelligence evidence for revenue, conversion, and operational KPIs. Use for bounded KPI scorecards, financial or operational metric checks, baseline comparisons, and business-unit reviews without changing source systems.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze reviewed Grafana log evidence for event patterns, error-rate changes, and enrolled security markers. Use when a user needs bounded log analytics for an incident window, error-log comparison, anomaly triage, operational debugging, or a cautious check of approved security signals.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect reviewed Grafana infrastructure evidence for host or fleet CPU usage, memory load, disk space, and system load. Use for server-health checks, capacity symptoms, resource saturation, disk pressure, cloud or local host comparisons, and bounded infrastructure triage.
日本語の概要は準備中です。原文の説明を表示しています。
Investigate reviewed Grafana APM evidence for request rate, error rate, and operational latency. Use when an application is slow, erroring, dropping traffic, regressing against a baseline, or needs a bounded request-rate, error, and p95 latency health assessment.
日本語の概要は準備中です。原文の説明を表示しています。
Monitor reviewed Grafana telemetry and freshness evidence for IoT devices and edge fleets. Use for smart devices, home automation sensors, remote equipment, wind turbines, space hardware, device-fleet freshness, missing telemetry, and bounded edge-health comparisons.
日本語の概要は準備中です。原文の説明を表示しています。
Builds real-time incident response dashboards in Splunk, Elastic, or Grafana to provide SOC analysts and leadership with situational awareness during active incidents, tracking affected systems, containment status, IOC spread, and response timeline. Use when IR teams need unified visibility during incident coordination and post-incident reporting.
日本語の概要は準備中です。原文の説明を表示しています。