detection-engineering SKILL.md skillA
detection-engineering from annatchijova/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add annatchijova/skills/detection-engineering@git:20260815.2390440Pins git:20260815.2390440 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- annatchijova/skills
- Path
detection-engineering/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260815.2390440, committed Aug 15, 2026
- Size
- 12,997 bytes
- Repository stars
- 9
- License
- a license file GitHub does not identify
Turn a detection requirement into a deployed, tested, versioned rule — with a benign twin that must NOT fire, an explicit false-positive budget, a volume estimate before deploy, and a tuning history that records every silently narrowed scope. Use whenever the user writes or reviews an alert, a Sigma/KQL/SPL/EQL/YARA rule, a SIEM correlation search, a WAF or EDR policy, an anomaly threshold, or a monitor that pages someone; whenever they say "write a rule for this", "alert when X…
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Detection Engineering A rule that has been written is not a detection. A rule that has been deployed is not a detection either. A detection is a rule that has **fired on a known true positive, stayed silent on its benign twin, and produced a volume someone will actually triage**. Everything before that is a hypothesis with YAML around it. This skill exists because the failure mode is invisible by construction: a rule that never fires looks exactly like a rule protecting you from something that never happened. The discipline is to make the silent failure loud *before* it matters. Composes with the library: - **purple-team-exercise** — supplies the detection *requirement*; retests the rule - **attack-surface-triage** — supplies the techniques worth detecting - **falsifiable-testing** — a rule with no failing case is a test that cannot fail - **claim-provenance-discipline** — every tuning exclusion is a scope narrowing that must travel - **versioned-schema-evolution** — log formats change under your rules; version accordingly - **daubert-defensible-writing** — "we have coverage for T1078" is a claim that needs evidence --- ## Step 0 — The input is a requirement, not a vibe …
Read the whole file at its exact version.
How to install
mdr add annatchijova/skills/detection-engineering@sha256:c71be30ff80d9fc9The line at the top of this page pins the label git:20260815.2390440, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_kmmi3jb37jvr6mzb)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Aug 15, 2026.
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (12997 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
annatchijova/skills · 9 stars · license a license file GitHub does not identify · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_kmmi3jb37jvr6mzb GET https://markdownregistry.com/api/v1/resolve?ref=annatchijova/skills/detection-engineering GET https://markdownregistry.com/api/v1/blob/c71be30ff80d9fc90579d61b56afd3777a14b831e362a4216bb06aa7cef288b7
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from annatchijova/skills
Every file in annatchijova/skills