Individual skill
engineering-detections
Build, test, and tune detection content — Sigma, YARA, Suricata, and EDR/SIEM queries — mapped to MITRE ATT&CK with explicit false-positive analysis and detection-as-code practices. Use when writing or reviewing a detection rule, converting IOCs or TTPs into alerts, measuring detection coverage, or reducing alert fatigue.
secskills-defense/skills/engineering-detections/SKILL.md
Source commit ca53957bcd8e3b83b5d4d190bb3ad008a4f15c84
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 6, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 188
- Repository last updated
- Sep 4, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- security Repository topic
- skills Repository topic
- writing Derived category
- engineering Derived category
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
Read excerpt
# Engineering Detections
A detection is a hypothesis about attacker behaviour, expressed as a query,
that a human will be paged for. Two properties decide whether it is worth
deploying: does it fire on the behaviour, and does it stay quiet otherwise.
Most rules fail the second test, and the cost is paid by whoever is on call.
## When to Use
- Writing a new detection rule from a TTP, a sample, or an incident
- Reviewing or tuning an existing rule that is noisy or silent
- Converting threat intelligence into deployable detection content
- Assessing detection coverage against ATT&CK
- Setting up detection-as-code: repo layout, testing, CI, deployment