Detect Anomalies Aiops
Implement AI-powered anomaly detection for operational metrics using time series analysis (Isolation Forest, Prophet, LSTM), alert correlation, and root cause analysis. Reduce alert fatigue by intelligently identifying true anomalies in system metrics, logs, and traces. Use when operations teams are overwhelmed by alert volume, when detecting complex multi-metric anomalies beyond static thresholds, when seasonal patterns make thresholds ineffective, or when needing to predict issues proactively before they impact users.
Install
npx skills add pjt222/agent-almanac --skill detect-anomalies-aiopsgit clone --depth 1 https://github.com/pjt222/agent-almanac.git /tmp/agent-almanac
mkdir -p ~/.claude/skills
cp -r /tmp/agent-almanac/i18n/caveman-lite/skills/detect-anomalies-aiops ~/.claude/skills/detect-anomalies-aiopsPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Detect Anomalies for AIOps > See [Extended Examples](references/EXAMPLES.md) for complete configuration files and templates. Apply machine learning to detect anomalies in operational metrics, correlate alerts, and reduce false positives. ## When to Use - Operations team overwhelmed by alert volume (>100 alerts/day) - Need to detect complex multi-metric anomalies (not threshold breaches) - Seasonal patterns make static thresholds ineffective - Want to predict issues before they impact users (proactive detection) - Need to correlate related alerts to identify root cause - Monitoring system generates too many false positives - Want to detect subtle performance degradation trends ## Inputs - **Required**: Time series metrics from monitoring system (CPU, memory, latency, error rate) - **Required**: Historical data (30-90 days minimum) - **Optional**: Alert history with labels (true positive / false positive) - **Optional**: System topology (service dependencies) - **Optional**: Log data for correlation - **Optional**: Deployment/change events for context ## Procedure ### Step 1: Set Up Environment and Load Data Install dependencies and prepare time series data for analysis.
Details
- Skill name
detect-anomalies-aiops- Repository
- pjt222/agent-almanac
- Path
i18n/caveman-lite/skills/detect-anomalies-aiops/SKILL.md- License
- MIT
- Repo updated
- 18 November 2026
- Listed in
- BehiSecc/awesome-claude-skills
FAQ
What does the Detect Anomalies Aiops skill do?
Implement AI-powered anomaly detection for operational metrics using time series analysis (Isolation Forest, Prophet, LSTM), alert correlation, and root cause analysis. Reduce alert fatigue by intelligently identifying true anomalies in system metrics, logs, and traces. Use when operations teams are overwhelmed by alert volume, when detecting complex multi-metric anomalies beyond static thresholds, when seasonal patterns make thresholds ineffective, or when needing to predict issues proactively before they impact users.
How do I install the Detect Anomalies Aiops skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add pjt222/agent-almanac --skill detect-anomalies-aiops. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Detect Anomalies Aiops popular?
It lives in pjt222/agent-almanac, which has 45 GitHub stars and 4 forks, and is included in 1 curated skill list.
Related skills
Adapt Architecture
45pjt222/agent-almanac
Execute structural metamorphosis using strangler fig migration, chrysalis phases, and interface preservation. Covers transformation planning, parallel running, progressive cutover, rollback design, and post-metamorphosis stabilization for system architecture evolution. Use when assess-form has classified the system as READY for transformation, when migrating from monolith to microservices, when replacing a core subsystem while dependents continue operating, or when any architectural change must be gradual rather than big-bang.
Adaptic
45pjt222/agent-almanac
Master skill composing the 5-step synoptic cycle for panoramic synthesis across multiple domains. Orchestrates meditate, expand-awareness, observe, awareness, integrate-gestalt, and express-insight into a coherent process that produces unified understanding rather than sequential compromise. Use when a problem genuinely spans 3+ domains and the interactions between domains matter more than depth in any one, when sequential analysis feels like compromise rather than integration, or before major architectural decisions affecting multiple stakeholders.
Add Puzzle Type
45pjt222/agent-almanac
Scaffold a new puzzle type across all 10+ pipeline integration points in jigsawR. Creates the core puzzle module, wires it into the unified pipeline (generation, positioning, rendering, adjacency), adds ggpuzzle geom/stat layers, updates DESCRIPTION and config.yml, extends the Shiny app, and creates a comprehensive test suite. Use when adding a completely new puzzle type to the package or following the 10-point integration checklist to ensure nothing is missed end-to-end.
Dream
45pjt222/agent-almanac
AI unconstrained creative exploration — drop structure to let associations form freely. The one skill that inverts standard procedure format: instead of inputs, steps, and validation, dream opens space for emergence without evaluation. Use before design work, before naming things, before choosing between approaches, or anywhere premature structure kills the best option.
Design A2a Agent Card
45pjt222/agent-almanac
Design an A2A Agent Card (.well-known/agent.json) manifest describing agent capabilities, skills, authentication requirements, and supported content types. Use when building an agent that must be discoverable by other A2A-compliant agents, exposing capabilities for multi-agent orchestration, migrating an existing agent to the A2A protocol, defining the public contract for an agent before implementation, or integrating with agent registries that consume Agent Cards.
Du Dum
45pjt222/agent-almanac
Separate expensive observation from cheap decision-making in autonomous agent loops using a two-clock architecture. A fast clock accumulates data into a digest file; a slow clock reads the digest and acts only when something is pending. Idle cycles cost nothing because the action clock returns immediately after reading an empty digest. Use when building autonomous agents that must observe continuously but can only afford to act occasionally, when API or LLM costs dominate and most cycles have nothing to do, when designing cron-based agent architectures with observation and action phases, or wh
Browse the most popular Claude skills, all ai, llms & agents skills, or write your own with the skills generator.