meltedinhex/analyst-ai-pack / skills/building-a-threat-hunt-hypothesis
building-a-threat-hunt-hypothesis
VerifiedFrames a structured, testable threat-hunting hypothesis: grounding it in adversary behavior and available telemetry, defining the data sources and detection logic, and setting success criteria and outcomes. Activates for requests to start a threat hunt, write a hunt hypothesis, or plan a hypothesis-driven hunt.
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 340 B |
| SKILL.md | skill md | 3.4 KB |
| references/api-reference.md | markdown | 1.1 KB |
| scripts/analyst.py | script | 2.0 KB |
scripts/analyst.py
View on GitHub#!/usr/bin/env python3
"""Generate a structured threat-hunt plan from a hypothesis.
Takes an ATT&CK technique, a data source, and a lookback window and emits a plan skeleton:
hypothesis statement, data requirements, baseline questions, scope, and the three outcome
branches. This is a planning aid that emits text; it queries no systems.
"""
from __future__ import annotations
import argparse
import json
import sys
def plan(technique: str, datasource: str, window: str, behavior: str) -> dict:
return {
"technique": technique,
"hypothesis": f"If an adversary performs {behavior or '<behavior>'} ({technique}), "
f"then I expect to observe related evidence in {datasource}.",
"data_requirements": {
"source": datasource,
"lookback": window,
"checks": ["source exists", "retention covers window", "fields needed are present"],
},
"baseline_questions": [
"What does normal activity look like for this behavior?",
"Which hosts/users legitimately exhibit it?",
],
"scope": {"hosts": "<scope>", "time_window": window},
"outcomes": {
"finding": "escalate to incident response",
"detection_gap": "hand to detection engineering",
"confident_negative": "document hunt and queries for reuse",
},
}
def main(argv: list[str] | None = None) -> int:
parser = argparse.ArgumentParser(description="Generate a hunt plan")
sub = parser.add_subparsers(dest="cmd", required=True)
p = sub.add_parser("plan")
p.add_argument("--technique", required=True)
p.add_argument("--datasource", required=True)
p.add_argument("--window", default="14d")
p.add_argument("--behavior", default="")
args = parser.parse_args(argv)
print(json.dumps(plan(args.technique, args.datasource, args.window, args.behavior),
indent=2))
return 0
if __name__ == "__main__":
sys.exit(main())
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first. | Stars: 194k | Updated | Claude CodeCodex | Verified | Install |