SKILL-031 Security, testing, and operations Locked skill

Error handling and logging

A log line is forever and often less protected than your database. Never write a password, token, or full PII into it — redact at the boundary.

01

What this skill helps you build

Logs that let you debug an incident at 3am — structured, correlated by request id, reporting exceptions — without ever leaking a secret or a customer's data.

The production takeaway

A log line is forever and often less protected than your database. Never write a password, token, or full PII into it — redact at the boundary.

02

Inside this skill

The full skill expands these implementation areas with decisions, edge cases, prompts, tests, and framework-specific code.

Security, testing, and operations
What this helps you build

Operational visibility you can actually use: structured logs you can filter and search, a correlation id that ties every line of one request together, exceptions reported to a trac

🔒
Security, testing, and operations
When to use this

Set this up before your first real users, and revisit it whenever you add a sensitive data flow. You need it when: An error in production is currently invisible until a user compla

🔒
Security, testing, and operations
The core idea

Two disciplines, applied at the boundary: 1. Structured + correlated. Logs are key/value or JSON , and every line of a request carries the same request id , so you can pull the who

🔒
03

Unlock the full implementation

Paid access includes the complete skill body, implementation prompt, common mistakes, production checklist, and code examples where this skill includes them.