CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

logging

wellcrafted/logger for library diagnostics: 5 levels, typed errors, injected sinks, and host-owned durability. Use for attach primitives, background errors, durable host logs, or replacing console.* in library code.

Quality

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 high-quality, opinionated skill body: nearly every paragraph carries project-specific rules Claude could not infer, backed by executable code, runnable verification greps, and concrete anti-patterns with real consequences. The only costs are a few anecdotal passages that could be tightened and a 240-line monolith that could offload some deep-dive material to reference files.

DimensionReasoningScore

Conciseness

The body is dense with project-specific, non-inferable rules (level semantics, anti-patterns, DI wiring) and never explains generic concepts Claude already knows. Minor trimmable padding keeps it from a 5: the Whispering incident narrative ("Whispering did exactly this and grew a parallel log..."), and the jsonlFileSink removal history ("This used to be jsonlFileSink; that primitive was removed because...") are longer than the rule they justify. Clearly above the 3 anchor, which flags whole sections of unnecessary explanation.

4 / 5

Actionability

Quotes: the quickstart import block, the level table with exact signatures, the trySync call-site example, `grep -rn "consoleSink({" src/` and `grep -rn "log\.(warn|error)(new Error" src/` as runnable pre-checks, and the memorySink test snippet with assertions. Code is copy-paste ready and the examples cover the common cases (quickstart, branching, sinks, DI wiring), matching the 5 anchor.

5 / 5

Workflow Clarity

For a guidance/reference skill, the decision flow is unambiguous: pick a level from the table, use the dominant branch-on-Result shape, avoid the two named anti-patterns (with grep verification commands as checkpoints), wire sinks via DI. Not a 5 because there is no explicit multi-step sequence with feedback loops, and no validation step for the sink-serialization guidance; comfortably above a 3 since the grep pre-checks and the level table serve as concrete decision checkpoints.

4 / 5

Progressive Disclosure

Well-organized single-file skill with clear section headers, a quickstart up front, and clearly signaled cross-skill references ("error-handling skill: ... the [error variants reference](../error-handling/references/error-variants.md)", "rust-errors skill: full tracing ↔ Logger mapping") that are one level deep. Not a 5 because at ~240 lines with no bundle files, deep-dive material like the anti-pattern incident detail and the variant-naming rules could arguably live in a references/ file; well above a 3 since the inline content is curated guidance rather than an API-reference dump and navigation is easy.

4 / 5

Total

17

/

20

Passed

Description

83%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 description: it states exactly what the skill covers (the wellcrafted/logger surface and its design stances) and gives an explicit 'Use for' clause with concrete, natural trigger phrases. The only softness is feature-list framing rather than action framing and minor keyword variations left unsaid.

DimensionReasoningScore

Specificity

Quotes: "5 levels, typed errors, injected sinks, and host-owned durability" and "replacing console.* in library code" — it lists several concrete capabilities and one concrete action, naming the exact package. It falls short of the 5 anchor ('comprehensive coverage') because it enumerates features rather than a full set of actions the skill performs, and above the 3 anchor ('1-2 concrete actions') on the strength of the feature list plus the console.* replacement action.

4 / 5

Completeness

Quotes: "wellcrafted/logger for library diagnostics: 5 levels, typed errors, injected sinks, and host-owned durability" (clear what) followed by "Use for attach primitives, background errors, durable host logs, or replacing console.* in library code" (explicit when with concrete trigger phrases). This matches the 5 anchor exactly; the 4 anchor requires a 'when' that is less explicit, which does not apply here.

5 / 5

Trigger Term Quality

Quotes: "attach primitives, background errors, durable host logs, or replacing console.*" — these are the natural phrases a developer in this codebase would say, especially "console.*" and "background errors". Not a 5 because common variations like "logging", "log levels", or "sinks" as standalone trigger words are absent; well above a 3 ('some relevant keywords') given multiple distinct natural terms.

4 / 5

Distinctiveness Conflict Risk

Quotes: "wellcrafted/logger for library diagnostics" — tied to a specific package with distinct triggers (console.* replacement, attach primitives), giving a clear niche. Not a 5 because "typed errors" and "background errors" overlap the closely related error-handling skill's territory (the body itself cross-references it), a minor overlap risk.

4 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 1 suspicious

Warning

Total

15

/

16

Passed

Repository

EpicenterHQ/epicenter

Path

.agents/skills/logging/SKILL.md

Reviewed

Table of Contents

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.