Lean throughout — it never explains what logging or a Logger is, and lines like "Loggers are passed explicitly via constructor injection... There is no global/ambient logger" and the tight env-var table earn their tokens; not the level below which carries unnecessary explanation.

Two complete, executable TypeScript examples (constructor injection with child logger; createNoOpLogger in tests), exact env-var names/values, and a concrete `logger.error('Failed', { err })` pattern make it copy-paste ready.

A self-contained pattern reference with unambiguous per-context guidance (Pattern, Child loggers, Configuration, In Tests, When Adding Logs); no destructive or batch operations exist that would require validation checkpoints, so the simple-skill allowance applies.

No bundle files exist and none are needed; the body is well-organized into clear single-level sections with no nested references, satisfying the well-organized-sections allowance for a self-contained skill.

Lists multiple specific concrete items — "adding logs, debugging", "constructor-injection pattern, child loggers, env-var configuration, and test mocking" — matching the multiple-concrete-actions anchor; not the level below which only names a domain.

Explicitly answers both: "Use when adding logs, debugging, or working with the Logger..." (when) and "Covers the constructor-injection pattern, child loggers, env-var configuration, and test mocking" (what), matching the explicit-trigger anchor.

Natural terms "adding logs, debugging, ... the Logger" are present, but coverage is diluted by internal jargon ("constructor-injection pattern", "env-var configuration", "test mocking") that users would not say, and common variations like "logging" or "log levels" are missing.

Scoped to "the Logger across the SDK and container runtime" gives a niche, but the broad trigger "debugging" and generic "adding logs" could overlap with other skills, so it is not clearly conflict-free.