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

88%

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

90%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, highly actionable reference with executable examples and a coherent decision model for library logging. Its main weakness is progressive disclosure: the monolithic body could offload API detail to a reference bundle, and the pattern-catalog structure lacks explicit linear sequencing.

Suggestions

Move the Event shape / sink API reference (LogEvent fields, consoleSink/memorySink/composeSinks signatures) into a references/ file and keep SKILL.md as an overview pointing to it, improving progressive disclosure.

Add an explicit ordered decision flow (e.g. 1. mint a defineErrors variant, 2. branch on Result, 3. log warn/error inside the branch, 4. verify with grep) so the workflow reads as a sequenced procedure rather than separate patterns.

Provide a short validation/checklist step for the two anti-patterns (the grep commands) framed as a single 'before you add a log call' checkpoint to strengthen workflow clarity.

Dimension	Reasoning	Score
Conciseness	Lean and dense throughout, assuming competence ('No file sink in-process: durability is a host concern'); no basic-concept padding and every section earns its place.	5 / 5
Actionability	Provides copy-paste-ready, executable TypeScript across quickstart, level table with signatures, .catch tails, composeSinks, and a memorySink test pattern covering common cases.	5 / 5
Workflow Clarity	Clear decision flow (branch-on-Result then log, warn vs error by context) with a grep-before-adding verification checkpoint, but organized as a pattern catalog rather than a linearly sequenced workflow.	4 / 5
Progressive Disclosure	Well-sectioned with clear headers and a one-level 'See also' pointer to peer skills, but no bundle files exist and the ~247-line body inlines API-level detail that could be split into a reference file.	4 / 5
	Total	18 / 20 Passed

Description

87%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 well-scoped, third-person description that pairs concrete capabilities with an explicit 'Use for' trigger clause, covering both what and when. Slightly technical phrasing in the triggers is the only thing keeping trigger-term and specificity scores off the top anchor.

Dimension	Reasoning	Score
Specificity	Lists several concrete attributes ('5 levels, typed errors, injected sinks, host-owned durability'), though framed as capabilities rather than discrete actions, leaving minor gaps in action-level coverage.	4 / 5
Completeness	Explicitly answers what it does (a logger with named capabilities) and when to use it via a concrete 'Use for attach primitives, background errors...' trigger clause.	5 / 5
Trigger Term Quality	The 'Use for...' clause surfaces several natural trigger phrases ('background errors, durable host logs, replacing console.*'), with good coverage but a few common user phrasings missing.	4 / 5
Distinctiveness Conflict Risk	Scoped narrowly to wellcrafted/logger for library diagnostics with distinct triggers, giving it a clear niche and minimal conflict risk with other skills.	5 / 5
	Total	18 / 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: EpicenterHQ/epicenter
Path: .agents/skills/logging/SKILL.md
Commit: 9e1f9d2

Reviewed: ~8 hours 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.