[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ARDRMM5FQ0WY9ZF6AF65CZ":3,"skill-same:01M7ARDRMM5FQ0WY9ZF6AF65CZ":99},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M7ARDRMM5FQ0WY9ZF6AF65CZ","observability-designer",null,"Design production-ready observability strategies combining metrics, logs, and traces. Includes SLI\u002FSLO design, golden-signals monitoring, alert optimization. Use when adding observability to a new service, refactoring alerting that is too noisy, or designing an SLO program before scaling production load.","GongYuanCaiJi\u002Fdsh-claude-skills","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7APPQ7AEZTDQB0N6HCPTR2X",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fobservability-designer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"observability-designer\"\ndescription: \"Design production-ready observability strategies combining metrics, logs, and traces. Includes SLI\u002FSLO design, golden-signals monitoring, alert optimization. Use when adding observability to a new service, refactoring alerting that is too noisy, or designing an SLO program before scaling production load.\"\n---\n\n# Observability Designer (POWERFUL)\n\n**Category:** Engineering  \n**Tier:** POWERFUL  \n**Description:** Design comprehensive observability strategies for production systems including SLI\u002FSLO frameworks, alerting optimization, and dashboard generation.\n\n## Overview\n\nObservability Designer creates production-ready dashboards, alert configurations, and monitoring strategies across the three pillars (metrics, logs, traces).\n\n**When NOT to use → slo-architect.** For SLO\u002FSLI design with error-budget math, multi-window burn-rate alerting thresholds, and SLO review gates, route to `slo-architect` — it is the authoritative skill for that half. This skill's `slo_designer.py` produces a quick scaffold only. This skill's lane: dashboards (`dashboard_generator.py`) and alert-noise reduction (`alert_optimizer.py`).\n\n## Quick Start\n\n```bash\n# Dashboard spec (Grafana JSON + docs) for a service\npython3 scripts\u002Fdashboard_generator.py --service-type api --name payments --criticality critical --role sre --format grafana -o dashboard.json --doc-output dashboard.md\n\n# Analyze an existing alert config for noise, duplicates, and coverage gaps\npython3 scripts\u002Falert_optimizer.py --input alerts.json --analyze-only --report alert_report.json\n# ...then emit the optimized config once the report is reviewed:\npython3 scripts\u002Falert_optimizer.py --input alerts.json --output alerts_optimized.json\n\n# Quick SLO scaffold (hand off to slo-architect for the real error-budget work)\npython3 scripts\u002Fslo_designer.py --service-type api --criticality high --user-facing true --service-name payments -o slo_scaffold.json\n```\n\n**Verification loop:** after deploying optimized alerts, track the report's noise metrics for one on-call rotation — if the actionable-alert ratio didn't improve, re-run `--analyze-only` against the live config and iterate. Import the generated dashboard into Grafana and confirm every golden-signal panel renders with live data before closing the task.\n\n## Core Competencies\n\n### SLI\u002FSLO\u002FSLA Framework Design\n- **Service Level Indicators (SLI):** Define measurable signals that indicate service health\n- **Service Level Objectives (SLO):** Set reliability targets based on user experience\n- **Service Level Agreements (SLA):** Establish customer-facing commitments with consequences\n- **Error Budget Management:** Calculate and track error budget consumption\n- **Burn Rate Alerting:** Multi-window burn rate alerts for proactive SLO protection\n\n### Three Pillars of Observability\n\n#### Metrics\n- **Golden Signals:** Latency, traffic, errors, and saturation monitoring\n- **RED Method:** Rate, Errors, and Duration for request-driven services\n- **USE Method:** Utilization, Saturation, and Errors for resource monitoring\n- **Business Metrics:** Revenue, user engagement, and feature adoption tracking\n- **Infrastructure Metrics:** CPU, memory, disk, network, and custom resource metrics\n\n#### Logs\n- **Structured Logging:** JSON-based log formats with consistent fields\n- **Log Aggregation:** Centralized log collection and indexing strategies\n- **Log Levels:** Appropriate use of DEBUG, INFO, WARN, ERROR, FATAL levels\n- **Correlation IDs:** Request tracing through distributed systems\n- **Log Sampling:** Volume management for high-throughput systems\n\n#### Traces\n- **Distributed Tracing:** End-to-end request flow visualization\n- **Span Design:** Meaningful span boundaries and metadata\n- **Trace Sampling:** Intelligent sampling strategies for performance and cost\n- **Service Maps:** Automatic dependency discovery through traces\n- **Root Cause Analysis:** Trace-driven debugging workflows\n\n### Dashboard Design Principles\n\n#### Information Architecture\n- **Hierarchy:** Overview → Service → Component → Instance drill-down paths\n- **Golden Ratio:** 80% operational metrics, 20% exploratory metrics\n- **Cognitive Load:** Maximum 7±2 panels per dashboard screen\n- **User Journey:** Role-based dashboard personas (SRE, Developer, Executive)\n\n#### Visualization Best Practices\n- **Chart Selection:** Time series for trends, heatmaps for distributions, gauges for status\n- **Color Theory:** Red for critical, amber for warning, green for healthy states\n- **Reference Lines:** SLO targets, capacity thresholds, and historical baselines\n- **Time Ranges:** Default to meaningful windows (4h for incidents, 7d for trends)\n\n#### Panel Design\n- **Metric Queries:** Efficient Prometheus\u002FInfluxDB queries with proper aggregation\n- **Alerting Integration:** Visual alert state indicators on relevant panels\n- **Interactive Elements:** Template variables, drill-down links, and annotation overlays\n- **Performance:** Sub-second render times through query optimization\n\n### Alert Design and Optimization\n\n#### Alert Classification\n- **Severity Levels:** \n  - **Critical:** Service down, SLO burn rate high\n  - **Warning:** Approaching thresholds, non-user-facing issues\n  - **Info:** Deployment notifications, capacity planning alerts\n- **Actionability:** Every alert must have a clear response action\n- **Alert Routing:** Escalation policies based on severity and team ownership\n\n#### Alert Fatigue Prevention\n- **Signal vs Noise:** High precision (few false positives) over high recall\n- **Hysteresis:** Different thresholds for firing and resolving alerts\n- **Suppression:** Dependent alert suppression during known outages\n- **Grouping:** Related alerts grouped into single notifications\n\n#### Alert Rule Design\n- **Threshold Selection:** Statistical methods for threshold determination\n- **Window Functions:** Appropriate averaging windows and percentile calculations\n- **Alert Lifecycle:** Clear firing conditions and automatic resolution criteria\n- **Testing:** Alert rule validation against historical data\n\n### Runbook Generation and Incident Response\n\n#### Runbook Structure\n- **Alert Context:** What the alert means and why it fired\n- **Impact Assessment:** User-facing vs internal impact evaluation\n- **Investigation Steps:** Ordered troubleshooting procedures with time estimates\n- **Resolution Actions:** Common fixes and escalation procedures\n- **Post-Incident:** Follow-up tasks and prevention measures\n\n#### Incident Detection Patterns\n- **Anomaly Detection:** Statistical methods for detecting unusual patterns\n- **Composite Alerts:** Multi-signal alerts for complex failure modes\n- **Predictive Alerts:** Capacity and trend-based forward-looking alerts\n- **Canary Monitoring:** Early detection through progressive deployment monitoring\n\n### Golden Signals Framework\n\n#### Latency Monitoring\n- **Request Latency:** P50, P95, P99 response time tracking\n- **Queue Latency:** Time spent waiting in processing queues\n- **Network Latency:** Inter-service communication delays\n- **Database Latency:** Query execution and connection pool metrics\n\n#### Traffic Monitoring\n- **Request Rate:** Requests per second with burst detection\n- **Bandwidth Usage:** Network throughput and capacity utilization\n- **User Sessions:** Active user tracking and session duration\n- **Feature Usage:** API endpoint and feature adoption metrics\n\n#### Error Monitoring\n- **Error Rate:** 4xx and 5xx HTTP response code tracking\n- **Error Budget:** SLO-based error rate targets and consumption\n- **Error Distribution:** Error type classification and trending\n- **Silent Failures:** Detection of processing failures without HTTP errors\n\n#### Saturation Monitoring\n- **Resource Utilization:** CPU, memory, disk, and network usage\n- **Queue Depth:** Processing queue length and wait times\n- **Connection Pools:** Database and service connection saturation\n- **Rate Limiting:** API throttling and quota exhaustion tracking\n\n### Distributed Tracing Strategies\n\n#### Trace Architecture\n- **Sampling Strategy:** Head-based, tail-based, and adaptive sampling\n- **Trace Propagation:** Context propagation across service boundaries\n- **Span Correlation:** Parent-child relationship modeling\n- **Trace Storage:** Retention policies and storage optimization\n\n#### Service Instrumentation\n- **Auto-Instrumentation:** Framework-based automatic trace generation\n- **Manual Instrumentation:** Custom span creation for business logic\n- **Baggage Handling:** Cross-cutting concern propagation\n- **Performance Impact:** Instrumentation overhead measurement and optimization\n\n### Log Aggregation Patterns\n\n#### Collection Architecture\n- **Agent Deployment:** Log shipping agent strategies (push vs pull)\n- **Log Routing:** Topic-based routing and filtering\n- **Parsing Strategies:** Structured vs unstructured log handling\n- **Schema Evolution:** Log format versioning and migration\n\n#### Storage and Indexing\n- **Index Design:** Optimized field indexing for common query patterns\n- **Retention Policies:** Time and volume-based log retention\n- **Compression:** Log data compression and archival strategies\n- **Search Performance:** Query optimization and result caching\n\n### Cost Optimization for Observability\n\n#### Data Management\n- **Metric Retention:** Tiered retention based on metric importance\n- **Log Sampling:** Intelligent sampling to reduce ingestion costs\n- **Trace Sampling:** Cost-effective trace collection strategies\n- **Data Archival:** Cold storage for historical observability data\n\n#### Resource Optimization\n- **Query Efficiency:** Optimized metric and log queries\n- **Storage Costs:** Appropriate storage tiers for different data types\n- **Ingestion Rate Limiting:** Controlled data ingestion to manage costs\n- **Cardinality Management:** High-cardinality metric detection and mitigation\n\n## Scripts Overview\n\nThis skill includes three powerful Python scripts for comprehensive observability design:\n\n### 1. SLO Designer (`slo_designer.py`)\nGenerates complete SLI\u002FSLO frameworks based on service characteristics:\n- **Input:** Service description JSON (type, criticality, dependencies)\n- **Output:** SLI definitions, SLO targets, error budgets, burn rate alerts, SLA recommendations\n- **Features:** Multi-window burn rate calculations, error budget policies, alert rule generation\n\n### 2. Alert Optimizer (`alert_optimizer.py`)\nAnalyzes and optimizes existing alert configurations:\n- **Input:** Alert configuration JSON with rules, thresholds, and routing\n- **Output:** Optimization report and improved alert configuration\n- **Features:** Noise detection, coverage gaps, duplicate identification, threshold optimization\n\n### 3. Dashboard Generator (`dashboard_generator.py`)\nCreates comprehensive dashboard specifications:\n- **Input:** Service\u002Fsystem description JSON\n- **Output:** Grafana-compatible dashboard JSON and documentation\n- **Features:** Golden signals coverage, RED\u002FUSE methods, drill-down paths, role-based views\n\n## Integration Patterns\n\n### Monitoring Stack Integration\n- **Prometheus:** Metric collection and alerting rule generation\n- **Grafana:** Dashboard creation and visualization configuration\n- **Elasticsearch\u002FKibana:** Log analysis and dashboard integration\n- **Jaeger\u002FZipkin:** Distributed tracing configuration and analysis\n\n### CI\u002FCD Integration\n- **Pipeline Monitoring:** Build, test, and deployment observability\n- **Deployment Correlation:** Release impact tracking and rollback triggers\n- **Feature Flag Monitoring:** A\u002FB test and feature rollout observability\n- **Performance Regression:** Automated performance monitoring in pipelines\n\n### Incident Management Integration\n- **PagerDuty\u002FVictorOps:** Alert routing and escalation policies\n- **Slack\u002FTeams:** Notification and collaboration integration\n- **JIRA\u002FServiceNow:** Incident tracking and resolution workflows\n- **Post-Mortem:** Automated incident analysis and improvement tracking\n\n## Advanced Patterns\n\n### Multi-Cloud Observability\n- **Cross-Cloud Metrics:** Unified metrics across AWS, GCP, Azure\n- **Network Observability:** Inter-cloud connectivity monitoring\n- **Cost Attribution:** Cloud resource cost tracking and optimization\n- **Compliance Monitoring:** Security and compliance posture tracking\n\n### Microservices Observability\n- **Service Mesh Integration:** Istio\u002FLinkerd observability configuration\n- **API Gateway Monitoring:** Request routing and rate limiting observability\n- **Container Orchestration:** Kubernetes cluster and workload monitoring\n- **Service Discovery:** Dynamic service monitoring and health checks\n\n### Machine Learning Observability\n- **Model Performance:** Accuracy, drift, and bias monitoring\n- **Feature Store Monitoring:** Feature quality and freshness tracking\n- **Pipeline Observability:** ML pipeline execution and performance monitoring\n- **A\u002FB Test Analysis:** Statistical significance and business impact measurement\n\n## Best Practices\n\n### Organizational Alignment\n- **SLO Setting:** Collaborative target setting between product and engineering\n- **Alert Ownership:** Clear escalation paths and team responsibilities\n- **Dashboard Governance:** Centralized dashboard management and standards\n- **Training Programs:** Team education on observability tools and practices\n\n### Technical Excellence\n- **Infrastructure as Code:** Observability configuration version control\n- **Testing Strategy:** Alert rule testing and dashboard validation\n- **Performance Monitoring:** Observability system performance tracking\n- **Security Considerations:** Access control and data privacy in observability\n\n### Continuous Improvement\n- **Metrics Review:** Regular SLI\u002FSLO effectiveness assessment\n- **Alert Tuning:** Ongoing alert threshold and routing optimization\n- **Dashboard Evolution:** User feedback-driven dashboard improvements\n- **Tool Evaluation:** Regular assessment of observability tool effectiveness\n","# Observability Designer (POWERFUL)\n\n**Category:** Engineering  \n**Tier:** POWERFUL  \n**Description:** Design comprehensive observability strategies for production systems including SLI\u002FSLO frameworks, alerting optimization, and dashboard generation.\n\n## Overview\n\nObservability Designer creates production-ready dashboards, alert configurations, and monitoring strategies across the three pillars (metrics, logs, traces).\n\n**When NOT to use → slo-architect.** For SLO\u002FSLI design with error-budget math, multi-window burn-rate alerting thresholds, and SLO review gates, route to `slo-architect` — it is the authoritative skill for that half. This skill's `slo_designer.py` produces a quick scaffold only. This skill's lane: dashboards (`dashboard_generator.py`) and alert-noise reduction (`alert_optimizer.py`).\n\n## Quick Start\n\n```bash\n# Dashboard spec (Grafana JSON + docs) for a service\npython3 scripts\u002Fdashboard_generator.py --service-type api --name payments --criticality critical --role sre --format grafana -o dashboard.json --doc-output dashboard.md\n\n# Analyze an existing alert config for noise, duplicates, and coverage gaps\npython3 scripts\u002Falert_optimizer.py --input alerts.json --analyze-only --report alert_report.json\n# ...then emit the optimized config once the report is reviewed:\npython3 scripts\u002Falert_optimizer.py --input alerts.json --output alerts_optimized.json\n\n# Quick SLO scaffold (hand off to slo-architect for the real error-budget work)\npython3 scripts\u002Fslo_designer.py --service-type api --criticality high --user-facing true --service-name payments -o slo_scaffold.json\n```\n\n**Verification loop:** after deploying optimized alerts, track the report's noise metrics for one on-call rotation — if the actionable-alert ratio didn't improve, re-run `--analyze-only` against the live config and iterate. Import the generated dashboard into Grafana and confirm every golden-signal panel renders with live data before closing the task.\n\n## Core Competencies\n\n### SLI\u002FSLO\u002FSLA Framework Design\n- **Service Level Indicators (SLI):** Define measurable signals that indicate service health\n- **Service Level Objectives (SLO):** Set reliability targets based on user experience\n- **Service Level Agreements (SLA):** Establish customer-facing commitments with consequences\n- **Error Budget Management:** Calculate and track error budget consumption\n- **Burn Rate Alerting:** Multi-window burn rate alerts for proactive SLO protection\n\n### Three Pillars of Observability\n\n#### Metrics\n- **Golden Signals:** Latency, traffic, errors, and saturation monitoring\n- **RED Method:** Rate, Errors, and Duration for request-driven services\n- **USE Method:** Utilization, Saturation, and Errors for resource monitoring\n- **Business Metrics:** Revenue, user engagement, and feature adoption tracking\n- **Infrastructure Metrics:** CPU, memory, disk, network, and custom resource metrics\n\n#### Logs\n- **Structured Logging:** JSON-based log formats with consistent fields\n- **Log Aggregation:** Centralized log collection and indexing strategies\n- **Log Levels:** Appropriate use of DEBUG, INFO, WARN, ERROR, FATAL levels\n- **Correlation IDs:** Request tracing through distributed systems\n- **Log Sampling:** Volume management for high-throughput systems\n\n#### Traces\n- **Distributed Tracing:** End-to-end request flow visualization\n- **Span Design:** Meaningful span boundaries and metadata\n- **Trace Sampling:** Intelligent sampling strategies for performance and cost\n- **Service Maps:** Automatic dependency discovery through traces\n- **Root Cause Analysis:** Trace-driven debugging workflows\n\n### Dashboard Design Principles\n\n#### Information Architecture\n- **Hierarchy:** Overview → Service → Component → Instance drill-down paths\n- **Golden Ratio:** 80% operational metrics, 20% exploratory metrics\n- **Cognitive Load:** Maximum 7±2 panels per dashboard screen\n- **User Journey:** Role-based dashboard personas (SRE, Developer, Executive)\n\n#### Visualization Best Practices\n- **Chart Selection:** Time series for trends, heatmaps for distributions, gauges for status\n- **Color Theory:** Red for critical, amber for warning, green for healthy states\n- **Reference Lines:** SLO targets, capacity thresholds, and historical baselines\n- **Time Ranges:** Default to meaningful windows (4h for incidents, 7d for trends)\n\n#### Panel Design\n- **Metric Queries:** Efficient Prometheus\u002FInfluxDB queries with proper aggregation\n- **Alerting Integration:** Visual alert state indicators on relevant panels\n- **Interactive Elements:** Template variables, drill-down links, and annotation overlays\n- **Performance:** Sub-second render times through query optimization\n\n### Alert Design and Optimization\n\n#### Alert Classification\n- **Severity Levels:** \n  - **Critical:** Service down, SLO burn rate high\n  - **Warning:** Approaching thresholds, non-user-facing issues\n  - **Info:** Deployment notifications, capacity planning alerts\n- **Actionability:** Every alert must have a clear response action\n- **Alert Routing:** Escalation policies based on severity and team ownership\n\n#### Alert Fatigue Prevention\n- **Signal vs Noise:** High precision (few false positives) over high recall\n- **Hysteresis:** Different thresholds for firing and resolving alerts\n- **Suppression:** Dependent alert suppression during known outages\n- **Grouping:** Related alerts grouped into single notifications\n\n#### Alert Rule Design\n- **Threshold Selection:** Statistical methods for threshold determination\n- **Window Functions:** Appropriate averaging windows and percentile calculations\n- **Alert Lifecycle:** Clear firing conditions and automatic resolution criteria\n- **Testing:** Alert rule validation against historical data\n\n### Runbook Generation and Incident Response\n\n#### Runbook Structure\n- **Alert Context:** What the alert means and why it fired\n- **Impact Assessment:** User-facing vs internal impact evaluation\n- **Investigation Steps:** Ordered troubleshooting procedures with time estimates\n- **Resolution Actions:** Common fixes and escalation procedures\n- **Post-Incident:** Follow-up tasks and prevention measures\n\n#### Incident Detection Patterns\n- **Anomaly Detection:** Statistical methods for detecting unusual patterns\n- **Composite Alerts:** Multi-signal alerts for complex failure modes\n- **Predictive Alerts:** Capacity and trend-based forward-looking alerts\n- **Canary Monitoring:** Early detection through progressive deployment monitoring\n\n### Golden Signals Framework\n\n#### Latency Monitoring\n- **Request Latency:** P50, P95, P99 response time tracking\n- **Queue Latency:** Time spent waiting in processing queues\n- **Network Latency:** Inter-service communication delays\n- **Database Latency:** Query execution and connection pool metrics\n\n#### Traffic Monitoring\n- **Request Rate:** Requests per second with burst detection\n- **Bandwidth Usage:** Network throughput and capacity utilization\n- **User Sessions:** Active user tracking and session duration\n- **Feature Usage:** API endpoint and feature adoption metrics\n\n#### Error Monitoring\n- **Error Rate:** 4xx and 5xx HTTP response code tracking\n- **Error Budget:** SLO-based error rate targets and consumption\n- **Error Distribution:** Error type classification and trending\n- **Silent Failures:** Detection of processing failures without HTTP errors\n\n#### Saturation Monitoring\n- **Resource Utilization:** CPU, memory, disk, and network usage\n- **Queue Depth:** Processing queue length and wait times\n- **Connection Pools:** Database and service connection saturation\n- **Rate Limiting:** API throttling and quota exhaustion tracking\n\n### Distributed Tracing Strategies\n\n#### Trace Architecture\n- **Sampling Strategy:** Head-based, tail-based, and adaptive sampling\n- **Trace Propagation:** Context propagation across service boundaries\n- **Span Correlation:** Parent-child relationship modeling\n- **Trace Storage:** Retention policies and storage optimization\n\n#### Service Instrumentation\n- **Auto-Instrumentation:** Framework-based automatic trace generation\n- **Manual Instrumentation:** Custom span creation for business logic\n- **Baggage Handling:** Cross-cutting concern propagation\n- **Performance Impact:** Instrumentation overhead measurement and optimization\n\n### Log Aggregation Patterns\n\n#### Collection Architecture\n- **Agent Deployment:** Log shipping agent strategies (push vs pull)\n- **Log Routing:** Topic-based routing and filtering\n- **Parsing Strategies:** Structured vs unstructured log handling\n- **Schema Evolution:** Log format versioning and migration\n\n#### Storage and Indexing\n- **Index Design:** Optimized field indexing for common query patterns\n- **Retention Policies:** Time and volume-based log retention\n- **Compression:** Log data compression and archival strategies\n- **Search Performance:** Query optimization and result caching\n\n### Cost Optimization for Observability\n\n#### Data Management\n- **Metric Retention:** Tiered retention based on metric importance\n- **Log Sampling:** Intelligent sampling to reduce ingestion costs\n- **Trace Sampling:** Cost-effective trace collection strategies\n- **Data Archival:** Cold storage for historical observability data\n\n#### Resource Optimization\n- **Query Efficiency:** Optimized metric and log queries\n- **Storage Costs:** Appropriate storage tiers for different data types\n- **Ingestion Rate Limiting:** Controlled data ingestion to manage costs\n- **Cardinality Management:** High-cardinality metric detection and mitigation\n\n## Scripts Overview\n\nThis skill includes three powerful Python scripts for comprehensive observability design:\n\n### 1. SLO Designer (`slo_designer.py`)\nGenerates complete SLI\u002FSLO frameworks based on service characteristics:\n- **Input:** Service description JSON (type, criticality, dependencies)\n- **Output:** SLI definitions, SLO targets, error budgets, burn rate alerts, SLA recommendations\n- **Features:** Multi-window burn rate calculations, error budget policies, alert rule generation\n\n### 2. Alert Optimizer (`alert_optimizer.py`)\nAnalyzes and optimizes existing alert configurations:\n- **Input:** Alert configuration JSON with rules, thresholds, and routing\n- **Output:** Optimization report and improved alert configuration\n- **Features:** Noise detection, coverage gaps, duplicate identification, threshold optimization\n\n### 3. Dashboard Generator (`dashboard_generator.py`)\nCreates comprehensive dashboard specifications:\n- **Input:** Service\u002Fsystem description JSON\n- **Output:** Grafana-compatible dashboard JSON and documentation\n- **Features:** Golden signals coverage, RED\u002FUSE methods, drill-down paths, role-based views\n\n## Integration Patterns\n\n### Monitoring Stack Integration\n- **Prometheus:** Metric collection and alerting rule generation\n- **Grafana:** Dashboard creation and visualization configuration\n- **Elasticsearch\u002FKibana:** Log analysis and dashboard integration\n- **Jaeger\u002FZipkin:** Distributed tracing configuration and analysis\n\n### CI\u002FCD Integration\n- **Pipeline Monitoring:** Build, test, and deployment observability\n- **Deployment Correlation:** Release impact tracking and rollback triggers\n- **Feature Flag Monitoring:** A\u002FB test and feature rollout observability\n- **Performance Regression:** Automated performance monitoring in pipelines\n\n### Incident Management Integration\n- **PagerDuty\u002FVictorOps:** Alert routing and escalation policies\n- **Slack\u002FTeams:** Notification and collaboration integration\n- **JIRA\u002FServiceNow:** Incident tracking and resolution workflows\n- **Post-Mortem:** Automated incident analysis and improvement tracking\n\n## Advanced Patterns\n\n### Multi-Cloud Observability\n- **Cross-Cloud Metrics:** Unified metrics across AWS, GCP, Azure\n- **Network Observability:** Inter-cloud connectivity monitoring\n- **Cost Attribution:** Cloud resource cost tracking and optimization\n- **Compliance Monitoring:** Security and compliance posture tracking\n\n### Microservices Observability\n- **Service Mesh Integration:** Istio\u002FLinkerd observability configuration\n- **API Gateway Monitoring:** Request routing and rate limiting observability\n- **Container Orchestration:** Kubernetes cluster and workload monitoring\n- **Service Discovery:** Dynamic service monitoring and health checks\n\n### Machine Learning Observability\n- **Model Performance:** Accuracy, drift, and bias monitoring\n- **Feature Store Monitoring:** Feature quality and freshness tracking\n- **Pipeline Observability:** ML pipeline execution and performance monitoring\n- **A\u002FB Test Analysis:** Statistical significance and business impact measurement\n\n## Best Practices\n\n### Organizational Alignment\n- **SLO Setting:** Collaborative target setting between product and engineering\n- **Alert Ownership:** Clear escalation paths and team responsibilities\n- **Dashboard Governance:** Centralized dashboard management and standards\n- **Training Programs:** Team education on observability tools and practices\n\n### Technical Excellence\n- **Infrastructure as Code:** Observability configuration version control\n- **Testing Strategy:** Alert rule testing and dashboard validation\n- **Performance Monitoring:** Observability system performance tracking\n- **Security Considerations:** Access control and data privacy in observability\n\n### Continuous Improvement\n- **Metrics Review:** Regular SLI\u002FSLO effectiveness assessment\n- **Alert Tuning:** Ongoing alert threshold and routing optimization\n- **Dashboard Evolution:** User feedback-driven dashboard improvements\n- **Tool Evaluation:** Regular assessment of observability tool effectiveness\n",{"name":5,"description":7},"main","992d25a425dee442a1f6a628d00a4fed33efe839","engineering\u002Fskills\u002Fobservability-designer","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 04:26:20",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill observability-designer",{"tool":37,"command":38},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill observability-designer",{"tool":40,"command":41},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-skills --skill observability-designer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fobservability-designer\u002FSKILL.md",true,[45,51,55,59,65,69,73,77,81,85,91,95],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"assets\u002Fsample_alerts.json","ASSET","资产文件",8197,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fobservability-designer\u002Fassets\u002Fsample_alerts.json",{"path":52,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":53,"sourceHtmlUrl":54},"assets\u002Fsample_service_api.json",1787,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fobservability-designer\u002Fassets\u002Fsample_service_api.json",{"path":56,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":57,"sourceHtmlUrl":58},"assets\u002Fsample_service_web.json",2425,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fobservability-designer\u002Fassets\u002Fsample_service_web.json",{"path":60,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":63,"sourceHtmlUrl":64},"expected_outputs\u002Fsample_dashboard.json","REFERENCE","参考文档",19598,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fobservability-designer\u002Fexpected_outputs\u002Fsample_dashboard.json",{"path":66,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":67,"sourceHtmlUrl":68},"expected_outputs\u002Fsample_slo_framework.json",22072,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fobservability-designer\u002Fexpected_outputs\u002Fsample_slo_framework.json",{"path":70,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":71,"sourceHtmlUrl":72},"README.md",11877,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fobservability-designer\u002FREADME.md",{"path":74,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":75,"sourceHtmlUrl":76},"references\u002Falert_design_patterns.md",11972,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fobservability-designer\u002Freferences\u002Falert_design_patterns.md",{"path":78,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":79,"sourceHtmlUrl":80},"references\u002Fdashboard_best_practices.md",14117,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fobservability-designer\u002Freferences\u002Fdashboard_best_practices.md",{"path":82,"resourceType":61,"resourceTypeDesc":62,"sizeBytes":83,"sourceHtmlUrl":84},"references\u002Fslo_cookbook.md",10608,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fobservability-designer\u002Freferences\u002Fslo_cookbook.md",{"path":86,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":89,"sourceHtmlUrl":90},"scripts\u002Falert_optimizer.py","SCRIPT","脚本",46697,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fobservability-designer\u002Fscripts\u002Falert_optimizer.py",{"path":92,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":93,"sourceHtmlUrl":94},"scripts\u002Fdashboard_generator.py",49538,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fobservability-designer\u002Fscripts\u002Fdashboard_generator.py",{"path":96,"resourceType":87,"resourceTypeDesc":88,"sizeBytes":97,"sourceHtmlUrl":98},"scripts\u002Fslo_designer.py",29444,"https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fengineering\u002Fskills\u002Fobservability-designer\u002Fscripts\u002Fslo_designer.py",[100,107,114,121,128,135],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":19},"01M7ASG5XZVP67CMMRENYFQWPW","syllabus","Generates a curated supplementary reading list from any course syllabus using Consensus academic search. Grill-me intake (syllabus input format + course audience + year range) plus a grouping forcing-options checkpoint before any search runs — so the reading list matches the course's level and recency need. Parses the syllabus to extract topics and learning outcomes, searches Consensus for recent peer-reviewed papers per topic, and produces a professionally formatted .docx with clickable Consensus links, plain-language summaries calibrated to audience level, and Bloom-higher-order discussion questions tied to course learning goals. Use when the user uploads a syllabus, course outline, or curriculum document and wants supplementary readings (e.g., 'create a reading list from this syllabus', 'find recent papers for my course') — even casual mentions with a syllabus attached should trigger this skill.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fsyllabus\u002Fskills\u002Fsyllabus\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":19},"01M7ASFSGJF6G9KM40S1QJPR57","research","Default entry point for any research request — a hybrid router that classifies the question deterministically and either delegates to a specialist research skill (pulse for trends\u002Fsentiment, grants for NIH funding, litreview for academic literature, syllabus for course reading, patent for prior-art + IP landscape, dossier for entity research) or runs its own plan-decompose-multi-source-search-synthesize-cite fallback workflow when no specialist matches. Always surfaces the routing decision so users can override. Use when the user makes any research request that doesn't obviously match a more-specific specialist skill (e.g., \"research [topic]\", \"look into [topic]\", \"what do we know about [topic]\", \"investigate [topic]\", \"find me information on [topic]\", \"do some research on [topic]\", \"I need to understand [topic]\"). Output is a markdown briefing (default) or .docx document (on request) with full citations and an audit log.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fresearch\u002Fskills\u002Fresearch\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":19},"01M7ASFFNCMS1X5X276VE277KW","pulse","Multi-source recency research skill that takes the pulse of any topic across Reddit, Hacker News, the open web, and optionally X\u002FTwitter within a configurable recent window (default 30 days). Forcing intake clarifies topic specificity, angle (trend\u002Fsentiment\u002Fproblems\u002Fopportunities\u002Fcomparison), time window, and platform scope before searching. Returns a synthesized briefing with citations, engagement metrics, and cross-platform pattern analysis. Use when the user requests multi-source recency intelligence on a topic (e.g., 'pulse on [topic]', 'what's happening with [topic]', 'what are people saying about [topic]', 'current conversation about [topic]', 'take the pulse of [topic]', 'trending: [topic]', 'find me info on [topic]'), and for competitor research, trend discovery, tool comparisons, and audience sentiment analysis.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpulse\u002Fskills\u002Fpulse\u002FSKILL.md",[],[],{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":19},"01M7ASF2BM8D9CDRQV1VBV7FV6","patent","Patent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search \u002F freedom-to-operate \u002F competitive landscape \u002F acquisition diligence \u002F litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fpatent\u002Fskills\u002Fpatent\u002FSKILL.md",[],[],{"skillNo":129,"name":130,"nameZh":6,"description":131,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":132,"categories":133,"keywords":134,"publishedAt":19},"01M7ASERRV1ES4S7QJRTTYWK0H","notebooklm","Browser automation skill for controlling Google's NotebookLM. Use when the user wants anything done in NotebookLM (e.g., 'open NotebookLM', 'check my [name] notebook', 'ask my notebook about X', 'add [source] to NotebookLM', 'generate a Video Overview from my notebook', 'use NotebookLM Studio'). Handles reading and querying notebooks, adding sources (URLs, text, files, YouTube links, synthesized content), generating Studio outputs (Audio\u002FVideo Overviews, Mind Maps, Reports incl. Briefing Doc\u002FStudy Guide\u002FFAQ, Flashcards, Quiz, slide decks, infographics — discover the exact set from the live Studio panel; the UI evolves fast), and creating new notebooks. Requires browser automation environment — fails gracefully when unavailable.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Fnotebooklm\u002Fskills\u002Fnotebooklm\u002FSKILL.md",[],[],{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":19},"01M7ASEANH3H547WQBZ7X8W5CX","litreview","Academic literature orientation skill that searches papers via free keyless APIs (PubMed E-utilities + OpenAlex) by default — with the Consensus MCP as an optional enhancement lane when connected — builds a strategic search plan using PICO (default) or SPIDER \u002F Decomposition \u002F hybrid as fallbacks, and synthesizes findings into a formatted Word (.docx) research guide. Grill-me intake (research question specificity + framework hint + tentative depth) before the recon search; a second forcing checkpoint after Phase 2 confirms framework + sub-areas + depth before searches consume budget. Configurable depth (5\u002F10\u002F20 queries) controls coverage vs. speed. Output is a 'launching pad' — an orientation guide that lets a researcher dive in confidently, not a finished review. Use when the user starts literature-oriented research (e.g., 'litreview on [topic]', 'literature review on [topic]', 'I'm starting a literature review on X', 'I'm writing a paper on X', 'help me research X', 'I'm doing research on X', 'can you help me research X'). Do NOT use for single one-off paper searches wanting a quick list — that's a plain PubMed\u002FOpenAlex (or Consensus) query.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-skills\u002Fblob\u002Fmain\u002Fresearch\u002Flitreview\u002Fskills\u002Flitreview\u002FSKILL.md",[],[]]