Deep Dive Ioc

Community

dandye

deep-dive-ioc

Perform exhaustive analysis of a critical IOC. Use when an IOC needs Tier 2+ investigation beyond basic enrichment - includes GTI pivoting, deep SIEM searches, correlation with related entities, and threat attribution. For escalated IOCs requiring comprehensive investigation.

Overview

Publisher	dandye
Repository	`ai-runbooks`
Skill name	`deep-dive-ioc`
Stars	126
Forks	34
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by dandye on GitHub. Read the source before you install it.

Installation

Install the Deep Dive Ioc AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
Enable the skill in any chat where you want it available.

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/dandye/ai-runbooks.git /tmp/ai-runbooks
mkdir -p .claude/skills
cp -r /tmp/ai-runbooks/skills/deep-dive-ioc .claude/skills/deep-dive-ioc

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Deep Dive Ioc in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Deep Dive Ioc on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Deep Dive Ioc is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Deep Dive IOC Analysis Skill

Perform exhaustive analysis of a single, potentially critical Indicator of Compromise escalated from Tier 1 or identified during an investigation.

Inputs

IOC_VALUE - The IOC to analyze (IP, domain, hash, or URL)
IOC_TYPE - The type: "IP Address", "Domain", "File Hash", or "URL"
CASE_ID - case ID for documentation (optional)
TIME_FRAME_HOURS - Lookback period (default: 168 = 7 days)

Workflow

Step 1: Get Case Context (if CASE_ID provided)


secops-soar.get_case_full_details(case_id=CASE_ID)

Step 2: Detailed GTI Report

Get comprehensive threat intelligence:

IOC Type	Tool
IP	`gti-mcp.get_ip_address_report(ip_address=IOC_VALUE)`
Domain	`gti-mcp.get_domain_report(domain=IOC_VALUE)`
Hash	`gti-mcp.get_file_report(hash=IOC_VALUE)`
URL	`gti-mcp.get_url_report(url=IOC_VALUE)`

Record:

Reputation and classifications
First/last seen dates
Associated threats (malware families, actors) → ASSOCIATED_THREAT_IDS
Key behaviors (for file hashes)

Step 3: GTI Pivoting

Use /pivot-on-ioc or directly call GTI relationship tools:

Recommended relationships by type:

IP: communicating_files, downloaded_files, resolutions
Domain: resolutions, communicating_files, subdomains
Hash: contacted_domains, contacted_ips, dropped_files
URL: communicating_files, downloaded_files

For file hashes, also get behavior summary:


gti-mcp.get_file_behavior_summary(hash=IOC_VALUE)

Step 4: Deep SIEM Search

Search for activity involving the IOC and its related entities:


secops-mcp.search_security_events(
    text="UDM query for IOC_VALUE",
    hours_back=TIME_FRAME_HOURS
)

Identify OBSERVED_RELATED_IOCS - IOCs from GTI pivoting that actually appear in SIEM results.

Step 5: SIEM Enrichment & Correlation

For the IOC and each OBSERVED_RELATED_IOC:

Use /enrich-ioc for enrichment
Use /correlate-ioc for alert/case correlation
Use /find-relevant-case for broader case search

Step 6: Enrich Associated Threats (Optional)

If ASSOCIATED_THREAT_IDS were found (malware families, actors):


gti-mcp.get_collection_report(id=THREAT_ID)

Step 7: Synthesize & Report

Combine all findings:

GTI report details
Related entities from pivoting
SIEM search results
Observed related IOCs with enrichment
Related alerts and cases
Associated threat context

Document in Case (if CASE_ID provided):


Use /document-in-case with comprehensive findings summary

Or generate standalone report:


Use /generate-report with REPORT_TYPE="deep_dive_ioc"

Required Outputs

After completing this skill, you MUST report these outputs:

Output	Description
`GTI_DEEP_FINDINGS`	Comprehensive GTI analysis (reputation, classification, behaviors)
`SIEM_DEEP_CONTEXT`	Extended SIEM event context (hosts, users, timelines)
`RELATED_ENTITIES`	Related IOCs from GTI pivoting (infrastructure connections)
`DISCOVERED_IOCS`	All IOCs discovered during analysis
`THREAT_ATTRIBUTION`	Threat actor/campaign attribution if found

Additionally provide:

Impact assessment and scope identification
Recommendations (escalate, contain, monitor)
Documentation in case or standalone report

When to Use This vs Basic Enrichment

Use `/enrich-ioc`	Use `/deep-dive-ioc`
Initial triage	Escalated from Tier 1
Quick context needed	Comprehensive investigation
Single IOC lookup	Full infrastructure mapping
Tier 1 workflow	Tier 2+ investigation

Frequently asked questions

What does the Deep Dive Ioc AI skill do?

Why use Deep Dive Ioc on TypingMind?

Because you install it once and use it with any model. Deep Dive Ioc is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Deep Dive Ioc in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/dandye/ai-runbooks/tree/main/skills/deep-dive-ioc. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Deep Dive Ioc?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Deep Dive Ioc?

As many as you like. As long as a model supports skills, you can use Deep Dive Ioc with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Deep Dive Ioc AI skill free?

Yes. It is published on GitHub by dandye under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Claude Opus 4 5 Migration

anthropics

OrganizationPopular

Migrate prompts and code from Claude Sonnet 4.0, Sonnet 4.5, or Opus 4.1 to Opus 4.5. Use when the user wants to update their codebase, prompts, or API calls to use Opus 4.5. Handles model string…

Canary

Post-deploy canary monitoring. (gstack)

Land And Deploy

Land and deploy workflow. (gstack)

Setup Deploy

Configure deployment settings for /land-and-deploy.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Deep Dive IOC Analysis Skill

Inputs

Workflow

Step 1: Get Case Context (if CASE_ID provided)

Step 2: Detailed GTI Report

Step 3: GTI Pivoting

Step 4: Deep SIEM Search

Step 5: SIEM Enrichment & Correlation

Step 6: Enrich Associated Threats (Optional)

Step 7: Synthesize & Report

Required Outputs

When to Use This vs Basic Enrichment

Frequently asked questions

Related AI Skills

Set up your own AI workspace now