Skip to content
Skill

Building threat intelligence enrichment in splunk

Build automated threat intelligence enrichment pipelines in Splunk Enterprise Security using lookup tables, modular inputs, and the Threat I

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

When your agent uses it

Build automated threat intelligence enrichment pipelines in Splunk Enterprise Security using lookup tables, modular inputs, and the Threat Intelligence Framework.

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 (10 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/building-threat-intelligence-enrichment-in-splunk:

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

For one project only, put the folder in .claude/skills/building-threat-intelligence-enrichment-in-splunk inside it instead.

Claude Code docs on skills

Copy the skill folder to ~/.agents/skills/building-threat-intelligence-enrichment-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/building-threat-intelligence-enrichment-in-splunk &&
cp -R "$tmp/plugins/asi/skills/building-threat-intelligence-enrichment-in-splunk" ~/.agents/skills/building-threat-intelligence-enrichment-in-splunk &&
rm -rf "$tmp"

For one repository only, put the folder in .agents/skills/building-threat-intelligence-enrichment-in-splunk inside it instead.

Codex docs on skills

Copy the skill folder to ~/.cursor/skills/building-threat-intelligence-enrichment-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/building-threat-intelligence-enrichment-in-splunk &&
cp -R "$tmp/plugins/asi/skills/building-threat-intelligence-enrichment-in-splunk" ~/.cursor/skills/building-threat-intelligence-enrichment-in-splunk &&
rm -rf "$tmp"

For one project only, put the folder in .cursor/skills/building-threat-intelligence-enrichment-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/building-threat-intelligence-enrichment-in-splunk

Or copy the folder to ~/.gemini/skills/building-threat-intelligence-enrichment-in-splunk yourself.

Gemini CLI docs on skills

For GitHub Copilot in VS Code, copy the skill folder to ~/.copilot/skills/building-threat-intelligence-enrichment-in-splunk:

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

For one project only, put the folder in .github/skills/building-threat-intelligence-enrichment-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/building-threat-intelligence-enrichment-in-splunk into your agent's skills folder as building-threat-intelligence-enrichment-in-splunk. Agents that support SKILL.md read one folder per skill.

The SKILL.md format

Building threat intelligence enrichment in splunk FAQ

How do I install Building threat intelligence enrichment in splunk in Claude Code?

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

Does Building threat intelligence enrichment 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 Building threat intelligence enrichment 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.

What are the best alternatives to Building threat intelligence enrichment in splunk?

The closest alternatives to Building threat intelligence enrichment in splunk are Security audit, Audit integrity, MCP security audit, MCP implementation security review and Threat model analyst.

More from plurigrid/asi

  1. Building effective fuzzing dictionaries for improved fuzzer performance.

    • Open source
    • 72 GitHub stars
  2. Overcoming fuzzing obstacles and improving fuzzer effectiveness.

    • Open source
    • 72 GitHub stars
  3. GAP (Groups, Algorithms, Programming) system integration for computational discrete algebra

    • Open source
    • 72 GitHub stars
  4. Gay.jl integration for bisimulation games with proper hue-based trit derivation and GF(3) conservation

    • Open source
    • 72 GitHub stars
  5. Wide-gamut color sampling with splittable determinism using Pigeons.jl

    • Open source
    • 72 GitHub stars

Alternatives to Building threat intelligence enrichment in splunk

  1. Security guidance and vulnerability review for codebases, APIs, services, CLI tools, libraries, and daemons

    • Open source
    • 74.4K GitHub stars
    • Security
  2. Enforce output quality, evidence verification, and quality gates across security audits

    • Open source
    • 41.3K GitHub stars
    • Security
  3. Audit MCP (Model Context Protocol) server configurations for security issues

    • Open source
    • 41.3K GitHub stars
    • Security
  4. Review the implementation source code of MCP (Model Context Protocol) servers, clients, and tool handlers against a security baseline — auth

    • Open source
    • 41.3K GitHub stars
    • Security
  5. Full STRIDE-A threat model analysis and incremental update skill for repositories and systems

    • Open source
    • 41.3K GitHub stars
    • Security
  6. Guide for configuring and managing GitHub secret scanning, push protection, custom patterns, and secret alert remediation

    • Open source
    • 41.3K GitHub stars
    • Security