splunk-analyzer
Automate Splunk queries and analyze results using Chrome DevTools MCP. Use when the user wants to run Splunk searches, export log data, or analyze Splunk results. Triggers on requests like "check error rates", "search Splunk for X", "run a Splunk query", "analyze logs from Splunk", or "find errors in payment-service".
Best use case
splunk-analyzer is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Automate Splunk queries and analyze results using Chrome DevTools MCP. Use when the user wants to run Splunk searches, export log data, or analyze Splunk results. Triggers on requests like "check error rates", "search Splunk for X", "run a Splunk query", "analyze logs from Splunk", or "find errors in payment-service".
Teams using splunk-analyzer should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/splunk-analyzer/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How splunk-analyzer Compares
| Feature / Agent | splunk-analyzer | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Automate Splunk queries and analyze results using Chrome DevTools MCP. Use when the user wants to run Splunk searches, export log data, or analyze Splunk results. Triggers on requests like "check error rates", "search Splunk for X", "run a Splunk query", "analyze logs from Splunk", or "find errors in payment-service".
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Splunk Analyzer
Automate Splunk searches via browser and analyze exported results.
## Configuration
```
SPLUNK_URL: https://your-splunk-instance.com
```
## Workflow
### 1. Navigate to Splunk
```
Navigate to: {SPLUNK_URL}/en-US/app/search/search
```
If login page appears, inform user: "Please authenticate in the browser. Let me know when you're logged in."
### 2. Build SPL Query
Convert natural language to SPL. See [references/spl-patterns.md](references/spl-patterns.md) for patterns.
**Query structure:**
```spl
index=<index> sourcetype=<sourcetype> <filters> | <transformations>
```
If user provides raw SPL, use it directly.
### 3. Execute Search
See [references/splunk-ui.md](references/splunk-ui.md) for UI selectors.
1. Find search bar (textarea with `data-test="search-bar"` or class `ace_text-input`)
2. Clear existing text, enter SPL query
3. Click search button (button with `data-test="search-button"` or "Search" text)
4. Wait for results (watch for "X events" or results table)
### 4. Export Results
1. Click "Export" button above results
2. Select "Raw" format
3. Set filename, click "Export"
4. Wait for download to complete
### 5. Analyze Results
Run analysis script on exported file:
```bash
python3 scripts/analyze_splunk.py <exported_file> [--charts]
```
**Analysis includes:**
- Event count and time range
- Top error patterns / log levels
- Field value distributions
- Anomaly detection (spikes, unusual values)
- Trend visualization (with `--charts`)
## Quick Reference
| User Request | Action |
|--------------|--------|
| "Check errors in service X" | `index=* "error" source="*X*" \| stats count by message` |
| "Show me logs from last hour" | `index=* earliest=-1h` |
| "Find slow requests" | `index=* duration>1000 \| stats avg(duration) by endpoint` |
| "Summarize today's exceptions" | Run query + full analysis with charts |Related Skills
xrd-crystallography-analyzer
X-ray Diffraction skill for crystal structure, phase identification, and crystallite size analysis of nanomaterials
claude-code-analyzer
Analyzes Claude Code usage patterns and provides comprehensive recommendations. Runs usage analysis, discovers GitHub community resources, suggests CLAUDE.md improvements, and fetches latest docs on-demand. Use when user wants to optimize their Claude Code workflow, create configurations (agents/skills/commands), or set up project documentation.
ac-stop-hook-analyzer
Analyze context and decide on continuation via Stop hook. Use when determining if work should continue, analyzing completion status, making continuation decisions, or implementing the Two-Claude pattern.
ai-analyzer
AI驱动的综合健康分析系统，整合多维度健康数据、识别异常模式、预测健康风险、提供个性化建议。支持智能问答和AI健康报告生成。
terraform-azurerm-set-diff-analyzer
Wave 5 migration placeholder for `awesome-copilot/terraform-azurerm-set-diff-analyzer` imported from antigravity-awesome-skills manifest.
terraform-analyzer
Specialized skill for analyzing Terraform configurations. Supports parsing, security scanning (tfsec, checkov), cost estimation (infracost), drift detection, and plan visualization across AWS, Azure, and GCP.
asciinema-analyzer
Semantic analysis of asciinema recordings. TRIGGERS - analyze cast, keyword extraction, find patterns in recordings.
workflow-analyzer
作業フローや手順を分析し、自動化可能な要素を特定する。ワークフロー分析時、自動化検討時、業務プロセス改善時、またはユーザーが作業フロー分析、自動化要素、業務手順、プロセス最適化に言及した際に使用する。
springboot-architecture-analyzer
系統化分析 Spring Boot 專案並生成完整的企業級架構文件,涵蓋系統概述、架構視圖、技術細節、部署策略等所有關鍵面向。
repository-analyzer
Comprehensive repository analysis using Explore agents, web search, and Context7 to investigate codebase structure, technology stack, configuration, documentation quality, and provide actionable insights. Use this skill when asked to analyze, audit, investigate, or report on a repository or codebase. | Exploreエージェント、Web検索、Context7を用いた包括的なリポジトリ分析。コードベース構造、技術スタック、設定、ドキュメント品質を調査し、実用的な洞察を提供。リポジトリやコードベースの分析、監査、調査、レポート作成を依頼された場合に使用。
project-analyzer
Automated brownfield codebase analysis. Detects project type, frameworks, dependencies, architecture patterns, and generates comprehensive project profile. Essential for Conductor integration and onboarding existing projects.
product-appeal-analyzer
Evaluate product desirability, market positioning, and emotional resonance—the complement to friction analysis. Assess whether users will WANT a product (not just use it), identity fit, trust signals, and value proposition clarity. Activate on "will they like it", "market positioning", "appeal analysis", "product desirability", "value proposition", "why would someone choose this", "landing page review", "conversion optimization", "messaging strategy". NOT for UX friction analysis (use ux-friction-analyzer), visual design implementation (use web-design-expert), or A/B test setup (use frontend-developer).