logging-and-monitoring-evidence-pack SKILL.md skillA
logging-and-monitoring-evidence-pack from better-isms/grcskills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add better-isms/grcskills/logging-and-monitoring-evidence-pack@git:20261027.690016cPins git:20261027.690016c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- better-isms/grcskills
- Path
skills/tristan-roth/logging-and-monitoring-evidence-pack/SKILL.md- Versions recorded
- 4
- Latest version
- git:20261027.690016c, committed Oct 27, 2026
- First version recorded
- Oct 19, 2026
- Size
- 7,570 bytes
- Repository stars
- 56
- License
- MIT
Use this skill when an auditor, customer or regulator will ask how security events are logged and watched, and someone says "prepare logging evidence", "show we monitor alerts", "what do we log and for how long", "who looks at the SIEM", "prove an alert was handled" or "our monitoring evidence is just dashboard screenshots". Maps log coverage and retention per system, lists the alert rules that matter and where they go, traces real alerts end to end with timestamps, and writes an evidence pack…
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
Use this before an audit or a customer review, and again after any change to the logging stack. You get an evidence pack in a new folder, `./logging-and-monitoring-evidence-pack/`: a spreadsheet you can open in Excel showing, per system, what is logged, where, for how long and who can delete it (`coverage.csv`); a short list of the alert rules that matter and who receives them (`alert-rules.md`); one page per real alert traced from firing to closure, with times (`walkthroughs/<n>.md`); and a list of gaps with an owner and a fix each (`gaps.md`). This skill drafts for a human to review and sign; this skill never marks a control effective. End `gaps.md` with `## Not checked`: what this run did not read or could not open, what it assumed and what it did not verify, specific to this run. ## Inputs to gather …
Read the whole file at its exact version.
How to install
mdr add better-isms/grcskills/logging-and-monitoring-evidence-pack@sha256:50106fa44e1248deThe line at the top of this page pins the label git:20261027.690016c, 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_beswcuzsnbovrycl)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 4 versions of this file, between Oct 19, 2026 and Oct 27, 2026, about one every 3 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.690016c latest | 2026-10-27 | 690016c | 7,570 B | A | view · diff |
| git:20261027.94f7f3e | 2026-10-27 | 94f7f3e | 7,537 B | A | view · diff |
| git:20261019.20937b5 | 2026-10-19 | 20937b5 | 7,309 B | A | view · diff |
| git:20261019.3c6cd53 | 2026-10-19 | 3c6cd53 | 7,158 B | A | view |
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 (7570 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
better-isms/grcskills · 56 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_beswcuzsnbovrycl GET https://markdownregistry.com/api/v1/resolve?ref=better-isms/grcskills/logging-and-monitoring-evidence-pack GET https://markdownregistry.com/api/v1/blob/50106fa44e1248de44f25523d6371e7cb44f84e04c4c49111f0626dacb85b4a9
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.