logging-standards skillA
logging-standards is agent-read markdown (skill) from komluk/scaffolding: Structured logging standards: log levels, structured fields, correlation IDs, PII masking, and event naming. TRIGGER when: adding log statements, configuring loggers, or reviewing log output. SKIP: metrics and alerting (use monitoring-observability); error control flow (use error-handling). (Examples use structlog + an OTLP sink.).
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# Logging Standards Skill
## Purpose
Standards for consistent, useful logging across all application layers.
## Auto-Invoke Triggers
- Adding log statements
- Configuring logging infrastructure
- Debugging issues
- Setting up monitoring
---
## Log Levels
| Level | Use Case | Example |
|-------|----------|---------|
| **TRACE** | Detailed debugging | Variable values, loop iterations |
| **DEBUG** | Diagnostic info | Method entry/exit, state changes |
| **INFO** | Normal operations | Request completed, job started |
| **WARN** | Potential issues | Retry attempt, deprecated usage |
| **ERROR** | Failures | Exception caught, operation failed |
| **FATAL** | System failure | Cannot start, out of memory |
### Level Selection Rules
- Production default: INFO
- Development default: DEBUG
- Never log TRACE in production
- ERROR should always have context
---
## Log Message Format
### Structure
```
[timestamp] [level] [correlation-id] [logger] - message {structured-data}
```
### Example
```
2024-01-15T10:30:45.123Z INFO abc-123-def UserService - User created {"userId": 42, "email": "user@example.com"}
```
### Message Guidelines
…Read the whole file at its exact version.
How to install
mdr add komluk/scaffolding/logging-standards@git:20260627.c37d831mdr add komluk/scaffolding/logging-standards@sha256:27170ffe27691486Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_2dihj3p5flukuhvc)
1 badge views in 30 days
Versions
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260627.c37d831 latest | 2026-06-27 | c37d831 | 9,117 B | A | view · diff |
| git:20260614.9d809af | 2026-06-14 | 9d809af | 9,080 B | A | view · diff |
| git:20260520.3aa374b | 2026-05-20 | 3aa374b | 8,512 B | A | view · diff |
| git:20260409.25dc3ca | 2026-04-09 | 25dc3ca | 8,407 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 (9117 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
komluk/scaffolding · 15 stars · license MIT · pushed 2026-09-21 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_2dihj3p5flukuhvc GET https://markdownregistry.com/api/v1/resolve?ref=komluk/scaffolding/logging-standards GET https://markdownregistry.com/api/v1/blob/27170ffe27691486721b0c8047cb0eea49eadbd81e29a3d6baf298dc6eced4c9
Your agent 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.