logging

Use when adding logs, debugging, or working with the Logger across the SDK and container runtime. Covers the constructor-injection pattern, child loggers, env-var configuration, and test mocking. (project)

Quality

93%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

93%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tight, actionable reference that assumes Claude's competence and gives executable patterns for the core logging concerns. The only soft spot is workflow clarity, which is inherently limited because this is a patterns reference rather than a sequenced procedure.

Suggestions

If a destructive or batch logging scenario exists (e.g., redacting secrets before logging), add an explicit validate-then-retry checkpoint so workflow clarity can reach 5.

Optionally split the env-var table and per-level rules into a reference file and link to it, which would let progressive disclosure demonstrate one-level-deep navigation.

Dimension	Reasoning	Score
Conciseness	The body is lean and code-driven with no padding of concepts Claude already knows; statements like 'There is no global/ambient logger' and the env-var table each earn their place.	5 / 5
Actionability	Provides copy-paste-ready TypeScript for constructor injection, child loggers, and no-op test mocking, plus a concrete env-var table and explicit per-level logging rules — fully executable guidance covering the common cases.	5 / 5
Workflow Clarity	Content is clearly organized into labeled sections (Pattern, Child loggers, Configuration, In Tests, When Adding Logs), but as a patterns reference rather than a multi-step process it has no explicit sequence or validation checkpoints, keeping it just below 5.	4 / 5
Progressive Disclosure	The skill is self-contained with no bundle files and well-organized section headers; content is appropriately inline with no nested or buried references, matching the simple-skill exception for well-structured skills.	5 / 5
	Total	19 / 20 Passed

Description

92%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, third-person description that clearly states both the trigger conditions and the specific patterns covered, with minimal conflict risk. It would only benefit from a few more natural synonyms to round out trigger-term coverage.

Suggestions

Add natural synonyms such as 'log messages', 'logging', or 'observability' to broaden trigger-term coverage toward comprehensive.

Consider naming the env vars (e.g., SANDBOX_LOG_LEVEL) in the description to make the 'env-var configuration' coverage even more concrete.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions/patterns — 'adding logs, debugging, or working with the Logger' plus coverage of 'constructor-injection pattern, child loggers, env-var configuration, and test mocking' — giving comprehensive coverage of the skill's scope.	5 / 5
Completeness	Explicitly answers both 'what' ('Covers the constructor-injection pattern, child loggers, env-var configuration, and test mocking') and 'when' ('Use when adding logs, debugging, or working with the Logger'), matching the level-5 anchor with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural user-facing phrases like 'adding logs' and 'debugging' are present alongside the specific entity 'the Logger', but a few common synonyms (e.g., 'logging', 'log messages', 'observability') are missing, keeping it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	Scoping to 'the Logger across the SDK and container runtime' carves out a clear niche with distinct triggers and minimal overlap with unrelated skills.	5 / 5
	Total	19 / 20 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: cloudflare/sandbox-sdk
Path: .agents/skills/logging/SKILL.md
Commit: 6abf639

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.