detection-explorer
/detection-explorer
Browse and inspect the ADEF detection catalog (read-only). Use when the user asks which detections exist or wants to find/filter them (by platform, ATT&CK tactic, engine, status, stage, origin, or review state), asks what needs MITRE tagging or review, or wants one detection's record, query, tactics, and journal history. For coverage or gap analysis, use the coverage-review skill.
- Author
- nebulock-inc ↗
- Licence
- MIT
- Last repository change
- 14.10.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
Browse and inspect the ADEF detection catalog (read-only). Use when the user asks which detections exist or wants to find/filter them (by platform, ATT&CK tactic, engine, status, stage, origin, or review state), asks what needs MITRE tagging or review, or wants one detection's record, query, tactics, and journal history. For coverage or gap analysis, use the coverage-review skill.
Original author description
Browse and inspect the ADEF detection catalog (read-only). Use when the user asks which detections exist or wants to find/filter them (by platform, ATT&CK tactic, engine, status, stage, origin, or review state), asks what needs MITRE tagging or review, or wants one detection's record, query, tactics, and journal history. For coverage or gap analysis, use the coverage-review skill.
How it works
- Rules
- Query — map the question to adef detection list (filters combine)
- Inspect
- Notes
SKILL.md preview
---
name: detection-explorer
description: Browse and inspect the ADEF detection catalog (read-only). Use when the user asks which detections exist or wants to find/filter them (by platform, ATT&CK tactic, engine, status, stage, origin, or review state), asks what needs MITRE tagging or review, or wants one detection's record, query, tactics, and journal history. For coverage or gap analysis, use the coverage-review skill.
---
# Detection Explorer
Translate a "what do we have?" question into the right `adef detection list` /
`show` call, run it, and summarize.
## Rules
- **Read-only.** `list`/`show` only read; never edit records, journals, or rule files.
- **Orchestrate**, don't reimplement — never hand-parse `catalog/*.yml` or the INDEX.
- Report only what the commands return. Empty result → check the catalog exists
(`adef catalog <rule-root>`) before assuming zero coverage.
- Hand off writes: onboarding → `catalog-onboarding`, authoring → `detection-author`,
MITRE tagging → `mitre-tagger`, coverage/gaps → `coverage-review`.
## Query — map the question to `adef detection list` (filters combine)
| Question | Filter |
|----------|--------|
| Windows detections | `--platform windows` |
| covers a tactic / lateral movement | `--tactic lateral-movement` (shortname or display name) |
| Sigma / SQL rules | `--engine sigma` (of `sigma\|sql\|sch_sql\|composite`) |
| a specific source format | `--rule-format sigma\|spl\|panther\|<profile>` |
| draft / deprecated | `--status draft` |
| at a FORGE stage | `--stage refine` |
| authored in ADEF vs from a repo | `--origin authored\|catalogued` |
| needs review / still needs MITRE | `--needs-review` (bare = structural) / `--needs-review no_mitre` |
Add `--report json` to count, group, or pick precisely — it includes a derived
`tactics` array. Parse the JSON; don't eyeball the table.
## Inspect
`adef detection show D-XXXX` → record, query, derived tactics, a `support` line
for recognized-but-unsupported formats, and the paired-journal tail (the "why" a
list can't show). Summarize — especially the journal.
When the question is topical rather than a filter ("detections about credential
dumping on Windows"), reach for `adef detection search "<query>"` — BM25 over
the journals *and* catalog records, so a detection is findable by what it
detects even when its journal is sparse. `--limit N` widens the default 10 hits.
## Notes
- Both accept `--workspace PATH` (default: `ADEF_WORKSPACE` env or cwd).
- Tactic names track the shipped ATT&CK snapshot (e.g. 19.1 renamed "Defense
Evasion" → "Stealth"); confirm a surprising name with `adef attack show <ID>`.
Files in this package (2)
- EVALS.md 2 KB
- SKILL.md 3 KB
Versions
The database has no other skills named detection-explorer.
Database snapshot: 13.11.2026 · package version b2adacf0d258 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 90coverage-review
Assess MITRE ATT&CK coverage from the ADEF catalog (read-only) and turn it into a work plan. Use when the user asks how good their detection coverage is, where the gaps or blind spots are, which techniques are single points of failure or ride one log source, what to build or… - 90detection-coverage-review
Assess detection coverage against the MITRE ATT&CK matrix: which tactics/techniques are covered, partially covered, or blind, weighted by data-source availability and threat relevance. Use to find and prioritize detection gaps for a SOC/program. - 90catalog-sync
Keep the ADEF catalog current after the source rules repo changes, using `adef sync`. Use when the user says their rules repo changed and the catalog needs refreshing, asks to reconcile / re-sync / "what's new, modified, or orphaned since we catalogued", wants a CI staleness… - 100attack-coverage-mapping
Map detections and telemetry to MITRE ATT&CK, build ATT&CK Navigator layers, distinguish tested vs. claimed coverage, and prioritize gaps by threat relevance (threat-informed defense). Use when reporting detection coverage, planning a detection roadmap, or assessing readiness… - 100siem-detection
Engineer and audit SIEM detection rules — log source coverage, Sigma / KQL / SPL / Elastic query authoring, MITRE ATT&CK mapping, false-positive tuning, and detection-as-code workflows. Use when the user mentions 'SIEM,' 'detection engineering,' 'detection rules,' 'Sigma,'… - 93detection-engineering
Guides creation of detection rules using Sigma rule specification and the Palantir Alerting and Detection Strategy (ADS) framework, mapped to MITRE ATT&CK v16 techniques. Auto-invoked when the user discusses detection logic, Sigma rules, ATT&CK coverage gaps, or asks "how do I…