Structured logging
Skill kimtth/agent-skill-100-lines-or-less/skills/structured-logging
🧿 Minimal but effective AI agent skill definitions in 100 lines or less.
npx -y skills add kimtth/agent-skill-100-lines-or-less --skill structured-loggingAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Use when: emit structured, queryable logs with the right levels, context, and no sensitive data.
SKILL.md
1.1 KB, as published. Nobody here has run it
Goal: logs that are machine-queryable and useful during incidents.
Use for:
- adding or cleaning up application logging
- making logs searchable and correlatable
- fixing noisy, unstructured, or leaky logs
Workflow:
- Log structured key-value events, not free-form strings.
- Attach context: request ID, user ID, and trace ID.
- Use levels deliberately: error, warn, info, debug.
- Log at boundaries and on state changes, not every line.
- Redact secrets and PII before they are written.
- Verify logs answer "what happened to this request".
Practices:
- one event per significant action, with fields
- consistent field names across services
- correlation IDs to stitch a request together
- sampling for high-volume debug logs
Rules:
- never log secrets, tokens, or PII
- use levels consistently; do not log everything as info
- prefer structured fields over string interpolation
- make every error log actionable, with context