forensic-logging-design SKILL.md skillA
forensic-logging-design 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/forensic-logging-design@git:20260815.52bfd00Pins git:20260815.52bfd00 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- annatchijova/skills
- Path
forensic-logging-design/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260815.52bfd00, committed Aug 15, 2026
- Size
- 12,101 bytes
- Repository stars
- 9
- License
- a license file GitHub does not identify
Decide what to record today so that tomorrow's reconstruction is possible — derive fields from the questions someone will have to answer under pressure, log the inputs to decisions rather than only their outcomes, correlate across services, keep the event schema a versioned interface, and make silence distinguishable from outage. Use whenever logging, telemetry, or an audit trail is designed, changed, trimmed, or found wanting: "add logging", "what should we log", "observability…
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
# Forensic Logging Design Logs are written for a reader who does not exist yet: a stranger, under time pressure, answering a question nobody anticipated, with no access to the person who wrote the line. Almost all logging advice optimizes for the author — readability, levels, tidiness. This skill optimizes for that stranger. The design move is to work **backwards from the questions**. Not "what events happen here" but "what will someone need to prove, and does any record let them". A log line that nobody's question maps onto is cost; a question with no line that answers it is a visibility gap you will discover at the worst moment. Composes with: `incident-timeline-reconstruction` (the downstream consumer), `detection-engineering` (rules can only see what is recorded), `secret-lifecycle-discipline` (logs are the top leak channel), `versioned-schema-evolution` (an event schema is a persisted format), `tamper-evident-audit-chain` (for the audit-grade subset), `agent-trust-boundaries` (record what motivated a privileged action). --- ## Part 1 — Start from the reconstruction requirement Before adding a field, write the questions. They are remarkably stable across systems: …
Read the whole file at its exact version.
How to install
mdr add annatchijova/skills/forensic-logging-design@sha256:01026b17833efbabThe line at the top of this page pins the label git:20260815.52bfd00, 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_sejfvjd5nsg2jott)
1 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 (12101 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_sejfvjd5nsg2jott GET https://markdownregistry.com/api/v1/resolve?ref=annatchijova/skills/forensic-logging-design GET https://markdownregistry.com/api/v1/blob/01026b17833efbabd01fb9ce761ad9c89ca7449fc546df7429b9a658561c86c9
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.