observability-monitor
Comprehensive observability and monitoring workflow that orchestrates metrics collection, logging, distributed tracing, and alerting systems. Handles everything from monitoring architecture design and implementation to APM integration, anomaly detection, and incident response automation.
What this skill does
# Observability Monitor - Complete Observability and Monitoring Workflow ## Overview This skill provides end-to-end observability and monitoring services by orchestrating monitoring architects, SRE specialists, and data analytics experts. It transforms monitoring requirements into comprehensive observability systems with real-time insights, proactive alerting, and intelligent incident response. **Key Capabilities:** - ๐ **Multi-Dimensional Monitoring** - Metrics, logs, traces, and events collection - ๐ค **Intelligent Alerting** - AI-powered anomaly detection and smart alerting - ๐ **Distributed Observability** - End-to-end tracing and system visibility - ๐ **Performance Analytics** - Advanced performance analysis and optimization - ๐จ **Incident Response** - Automated incident detection, correlation, and response ## When to Use This Skill **Perfect for:** - Observability architecture design and implementation - Monitoring system setup and configuration - Application performance monitoring (APM) integration - Log aggregation and analysis systems - Alerting and incident response automation - Performance optimization and bottleneck analysis **Triggers:** - "Set up comprehensive monitoring for [application]" - "Implement observability for microservices architecture" - "Create intelligent alerting and incident response" - "Set up log aggregation and analysis system" - "Implement distributed tracing and performance monitoring" ## Observability Expert Panel ### **Observability Architect** (Monitoring Strategy & Design) - **Focus**: Observability strategy, monitoring architecture, data collection - **Techniques**: Observability patterns, monitoring frameworks, data pipelines - **Considerations**: System visibility, data retention, scalability, cost optimization ### **SRE Specialist** (Reliability & Incident Response) - **Focus**: Site reliability engineering, incident response, SLO management - **Techniques**: SRE practices, incident management, reliability engineering - **Considerations**: System reliability, incident response time, service availability ### **Performance Analyst** (Performance Monitoring & Optimization) - **Focus**: Performance monitoring, bottleneck analysis, optimization strategies - **Techniques**: APM tools, performance profiling, optimization techniques - **Considerations**: Performance metrics, user experience, resource utilization ### **Data Analytics Expert** (Monitoring Analytics & Insights) - **Focus**: Monitoring data analysis, anomaly detection, predictive analytics - **Techniques**: Machine learning, statistical analysis, pattern recognition - **Considerations**: Data accuracy, false positives, predictive accuracy ### **Automation Engineer** (Monitoring Automation & Integration) - **Focus**: Monitoring automation, alerting systems, integration workflows - **Techniques**: Automation frameworks, alerting systems, integration patterns - **Considerations**: Automation reliability, integration complexity, maintenance overhead ## Observability Implementation Workflow ### Phase 1: Observability Requirements Analysis & Strategy **Use when**: Starting observability implementation or monitoring modernization **Tools Used:** ```bash /sc:analyze observability-requirements Observability Architect: observability strategy and requirements analysis SRE Specialist: reliability requirements and SLO definition Performance Analyst: performance monitoring requirements ``` **Activities:** - Analyze observability requirements and visibility needs - Define monitoring strategy and architecture principles - Identify key performance indicators and service level objectives - Assess current monitoring capabilities and gaps - Plan observability implementation roadmap and resource requirements ### Phase 2: Monitoring Architecture & Data Collection Design **Use when**: Designing monitoring infrastructure and data collection systems **Tools Used:** ```bash /sc:design --type monitoring observability-architecture Observability Architect: comprehensive monitoring architecture design Data Analytics Expert: data collection and analysis strategy Automation Engineer: monitoring automation and integration design ``` **Activities:** - Design monitoring architecture and data collection strategy - Plan metrics, logs, and traces collection infrastructure - Design data storage, retention, and processing pipelines - Plan monitoring integration with existing systems - Define monitoring data governance and security policies ### Phase 3: Monitoring Infrastructure Implementation **Use when**: Setting up monitoring tools and infrastructure components **Tools Used:** ```bash /sc:implement monitoring-infrastructure Observability Architect: monitoring tools implementation and configuration Automation Engineer: monitoring automation and integration setup Performance Analyst: performance monitoring implementation ``` **Activities:** - Implement metrics collection and storage systems - Set up log aggregation and analysis infrastructure - Configure distributed tracing and APM systems - Implement monitoring dashboards and visualization - Set up monitoring data backup and disaster recovery ### Phase 4: Alerting & Incident Response Setup **Use when**: Implementing alerting systems and incident response automation **Tools Used:** ```bash /sc:implement alerting-incident-response SRE Specialist: alerting strategy and incident response design Data Analytics Expert: anomaly detection and smart alerting Automation Engineer: incident response automation and workflows ``` **Activities:** - Design intelligent alerting strategies and thresholds - Implement anomaly detection and predictive alerting - Set up incident response workflows and automation - Create escalation procedures and on-call schedules - Implement incident communication and reporting systems ### Phase 5: Performance Monitoring & Optimization **Use when**: Setting up performance monitoring and optimization systems **Tools Used:** ```bash /sc:implement performance-monitoring Performance Analyst: performance monitoring and optimization implementation Observability Architect: performance visibility and analysis setup Data Analytics Expert: performance analytics and insights ``` **Activities:** - Implement application performance monitoring (APM) - Set up performance baselines and benchmarking - Create performance optimization recommendations - Implement user experience monitoring and analysis - Set up capacity planning and resource optimization ### Phase 6: Advanced Analytics & Predictive Monitoring **Use when**: Implementing advanced analytics and predictive monitoring capabilities **Tools Used:** ```bash /sc:implement predictive-monitoring Data Analytics Expert: advanced analytics and machine learning implementation Observability Architect: predictive monitoring architecture SRE Specialist: predictive incident prevention and response ``` **Activities:** - Implement machine learning for anomaly detection - Create predictive failure detection and prevention - Set up advanced analytics and trend analysis - Implement automated root cause analysis - Create predictive capacity planning and scaling ## Integration Patterns ### **SuperClaude Command Integration** | Command | Use Case | Output | |---------|---------|--------| | `/sc:design --type monitoring` | Monitoring design | Complete monitoring architecture | | `/sc:implement observability` | Observability system | Comprehensive observability implementation | | `/sc:implement alerting` | Alerting system | Intelligent alerting and incident response | | `/sc:implement apm` | APM system | Application performance monitoring | | `/sc:implement predictive-monitoring` | Predictive monitoring | Advanced analytics and prediction | ### **Monitoring Tool Integration** | Tool | Role | Capabilities | |------|------|------------| | **Prometheus** | Metrics collection | Time-series metrics collection and storage | | **Grafana** | Visualization | Monitoring dashboa
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context โ no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes โ information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development โ guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.