incident-timeline SKILL.md skillA
incident-timeline from gensecaihq/wazuh-autopilot is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gensecaihq/wazuh-autopilot/incident-timeline@v1.1Pins v1.1 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gensecaihq/wazuh-autopilot
- Path
backend/app/skills/incident-timeline/SKILL.md- Versions recorded
- 1
- Latest version
- v1.1, committed Sep 24, 2026
- Size
- 4,053 bytes
- Repository stars
- 63
- License
- MIT
Build an ordered, evidence-linked incident timeline with first/last seen, dwell time and pivot points; use when a case spans multiple alerts, hosts or stages and needs a clear narrative.
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
# Incident Timeline
A timeline turns a pile of alerts into a story a responder or executive can act on.
NIST SP 800-61r3 expects incident documentation of what happened, when, and how it was
detected; the timeline is the backbone of that record.
## Procedure
1. `get_case` — gather attached alerts, entities, findings, actions.
2. Pull supporting events for the key entities over the incident window
(`search_security_events`, `get_wazuh_alerts` filtered by agent/user/ip).
3. Normalize every timestamp to UTC ISO 8601. A Wazuh alert's `timestamp` is when the
manager processed the event. The original event time is in the log itself
(`predecoder.timestamp`, or the time at the start of `full_log`, or
`data.win.system.systemTime` for Windows). Use the event time when they differ by more
than a few seconds, and note clock skew or delayed delivery (e.g. an agent reconnecting
and flushing its buffer).
4. Order events; collapse repetitive ones ("38 sshd failures 09:02–09:12"). Wazuh
composite rules summarize bursts: one rule 5763 or rule 5712 alert stands for several
single failures (rules 5716, 5760, 5710), so count the underlying failures, not the
composites.
…Read the whole file at its exact version.
How to install
mdr add gensecaihq/wazuh-autopilot/incident-timeline@sha256:8afb3a9e6485519eThe line at the top of this page pins the label v1.1, 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_io3cjik5fvizq36p)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Sep 24, 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 (4053 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
gensecaihq/wazuh-autopilot · 63 stars · license MIT · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_io3cjik5fvizq36p GET https://markdownregistry.com/api/v1/resolve?ref=gensecaihq/wazuh-autopilot/incident-timeline GET https://markdownregistry.com/api/v1/blob/8afb3a9e6485519ecb338c61671bf00e8647d9631366b95c44a0dd85de7786f0
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.