network-monitoring
Monitor UniFi network infrastructure including sites, devices, and system health. Diagnose connectivity issues, track device performance, and generate network diagnostics.
What this skill does
# Network Monitoring Skill Monitor and diagnose your UniFi network infrastructure with comprehensive site, device, and health monitoring. ## What this skill does This skill enables you to: - Monitor all configured UniFi sites and their health status - Track device status and performance metrics - Diagnose network connectivity issues - Generate network diagnostic reports - Compare infrastructure across multiple sites ## When to use this skill Use this skill when you need to: - Check overall network health and status - Identify offline or underperforming devices - Diagnose connectivity problems - Get device-specific statistics (CPU, memory, uptime) - Compare site health across your infrastructure - Generate diagnostic reports for troubleshooting ## Available Tools - `get_network_sites` - List all configured sites - `get_site_health` - Get comprehensive health status for a site - `get_network_devices` - List all devices in a site - `get_network_device_stats` - Get detailed device statistics - `get_network_info` - Get system information and metrics ## Typical Workflows ### Site Health Check 1. Use `get_network_sites` to list all sites 2. Use `get_site_health` for each site to check status 3. Identify any sites with degraded health 4. Drill down with `get_network_devices` to find the issue ### Device Performance Analysis 1. Use `get_network_devices` to list devices 2. Use `get_network_device_stats` to get detailed metrics 3. Identify devices with high CPU/memory usage 4. Look for patterns of underperformance ### Network Troubleshooting 1. Start with `get_site_health` to identify problems 2. Use `get_network_devices` to list all devices 3. Use `get_network_device_stats` to analyze performance 4. Check `get_network_info` for system-level issues ## Example Questions - "What's the health status of all my sites?" - "Which devices in my network are offline?" - "Get device statistics for high CPU usage" - "Compare health across all my sites" - "Diagnose why connectivity is slow" - "Generate a network diagnostic report" ## Response Format When using this skill, I provide: - Health status indicators (excellent, good, minor issues, major issues) - Device counts and status breakdowns - Performance metrics (CPU, memory, uptime) - Specific problem identification with recommendations - Actionable diagnostics for troubleshooting ## Best Practices - Check site health first before diving into individual devices - Correlate device statistics with reported issues - Use multiple data points to identify root causes - Document patterns for trend analysis over time - Escalate hardware issues when performance metrics indicate failure
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.