Skip to content
Skill

Analyzing windows event logs in splunk

Analyzes Windows Security, System, and Sysmon event logs in Splunk to detect authentication attacks, privilege escalation, persistence mecha

Install
Scripts
None
Platforms
Claude Code, Codex, Cursor
GitHub stars
72
Last commit
18 days ago
License
Apache-2.0
Listing updated
today

When your agent uses it

Analyzes Windows Security, System, and Sysmon event logs in Splunk to detect authentication attacks, privilege escalation, persistence mechanisms, and lateral movement using SPL queries mapped to MITRE ATT&CK techniques. Use when SOC analysts need to investigate Windows-based threats, build detection queries, or perform forensic timeline analysis of Windows endpoints and domain controllers.

From the skill's SKILL.md. Your agent reads this description to decide when to load the skill.

What it can access

From a static check of its 1 file (11 KB) on GitHub on 17 November 2026. Nothing was run. Read the files before you install a skill: it can tell your agent to run anything its tools allow.

Install

This skill ships in the asi plugin. In Claude Code, add the marketplace and install the plugin (it may include other skills too):

/plugin marketplace add plurigrid/asi
/plugin install asi@asi

Or copy only this skill to ~/.claude/skills/analyzing-windows-event-logs-in-splunk:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/plurigrid/asi.git "$tmp" &&
mkdir -p ~/.claude/skills &&
rm -rf ~/.claude/skills/analyzing-windows-event-logs-in-splunk &&
cp -R "$tmp/plugins/asi/skills/analyzing-windows-event-logs-in-splunk" ~/.claude/skills/analyzing-windows-event-logs-in-splunk &&
rm -rf "$tmp"

For one project only, put the folder in .claude/skills/analyzing-windows-event-logs-in-splunk inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/analyzing-windows-event-logs-in-splunk to use it in every repository:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/plurigrid/asi.git "$tmp" &&
mkdir -p ~/.agents/skills &&
rm -rf ~/.agents/skills/analyzing-windows-event-logs-in-splunk &&
cp -R "$tmp/plugins/asi/skills/analyzing-windows-event-logs-in-splunk" ~/.agents/skills/analyzing-windows-event-logs-in-splunk &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/analyzing-windows-event-logs-in-splunk inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/analyzing-windows-event-logs-in-splunk to use it in every project:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/plurigrid/asi.git "$tmp" &&
mkdir -p ~/.cursor/skills &&
rm -rf ~/.cursor/skills/analyzing-windows-event-logs-in-splunk &&
cp -R "$tmp/plugins/asi/skills/analyzing-windows-event-logs-in-splunk" ~/.cursor/skills/analyzing-windows-event-logs-in-splunk &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/analyzing-windows-event-logs-in-splunk inside it instead.

Cursor docs on skills

Run in a terminal (add --scope workspace to install it for the current workspace only):

gemini skills install https://github.com/plurigrid/asi.git --path plugins/asi/skills/analyzing-windows-event-logs-in-splunk

Or copy the folder to ~/.gemini/skills/analyzing-windows-event-logs-in-splunk yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/analyzing-windows-event-logs-in-splunk:

tmp=$(mktemp -d) &&
git clone --depth 1 https://github.com/plurigrid/asi.git "$tmp" &&
mkdir -p ~/.copilot/skills &&
rm -rf ~/.copilot/skills/analyzing-windows-event-logs-in-splunk &&
cp -R "$tmp/plugins/asi/skills/analyzing-windows-event-logs-in-splunk" ~/.copilot/skills/analyzing-windows-event-logs-in-splunk &&
rm -rf "$tmp"

For one project only, put the folder in .github/skills/analyzing-windows-event-logs-in-splunk inside it instead.

VS Code docs on skills

Get the folder:

git clone --depth 1 https://github.com/plurigrid/asi.git

Then copy asi/plugins/asi/skills/analyzing-windows-event-logs-in-splunk into your agent's skills folder as analyzing-windows-event-logs-in-splunk. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Analyzing windows event logs in splunk FAQ

How do I install Analyzing windows event logs in splunk in Claude Code?

Copy the skill folder from GitHub to ~/.claude/skills/analyzing-windows-event-logs-in-splunk to use it in all your projects, or to .claude/skills/analyzing-windows-event-logs-in-splunk in one project. Or install the asi plugin, which includes it: /plugin marketplace add plurigrid/asi, then /plugin install asi@asi.

Does Analyzing windows event logs in splunk run scripts?

No. It is instructions only, with no scripts. This comes from a static check of the files on GitHub; nothing was run. Read the files before you install it.

Which AI agents can use Analyzing windows event logs in splunk?

Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, Windsurf and Goose. Each reads skills in the SKILL.md format from its own folder; the install steps on this page list them.

More from plurigrid/asi

  1. Org-agenda-like transient views for ASI skill orchestration via nbb/squint + Emacs hydra

    • Open source
    • 72 GitHub stars
  2. Connect and stream from OpenBCI Cyton/Daisy via USB dongle, including first-time radio channel pairing

    • Open source
    • 72 GitHub stars
  3. Hypothesis-Test Loops via REPL for Exploratory Abductive Inference with Gay.jl colors

    • Open source
    • 72 GitHub stars
  4. Layer 4 Learning and Pattern Extraction for Cognitive Surrogate Systems

    • Open source
    • 72 GitHub stars
  5. Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration

    • Open source
    • 72 GitHub stars
  6. Automated code review for pull requests using specialized review patterns

    • Open source
    • 72 GitHub stars
    • Developer tools