CtrlK
BlogDocsLog inGet started
Tessl Logo

golang-samber-slog

Structured logging extensions for Golang using samber/slog-**** packages — multi-handler pipelines (slog-multi), log sampling (slog-sampling), attribute formatting (slog-formatter), HTTP middleware (slog-fiber, slog-gin, slog-chi, slog-echo), and backend routing (slog-datadog, slog-sentry, slog-loki, slog-syslog, slog-logstash, slog-graylog...). Apply when using or adopting slog, or when the codebase already imports any github.com/samber/slog-* package.

91

1.00x
Quality

89%

Does it follow best practices?

Impact

95%

1.00x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 well-structured, actionable skill body that uses tables and executable Go examples to convey the pipeline model, offloads detail to four clearly signaled reference files, and surfaces common mistakes and shutdown requirements. Slight conciseness gains are possible by pruning restated rationale.

Suggestions

Trim restatements of the pipeline ordering rationale (e.g., 'Order matters: sampling before formatting saves CPU') since the canonical diagram already conveys it.

Consider adding an explicit validate/retry checkpoint for pipeline assembly (e.g., build-then-run-a-test-record-then-inspect) to lift workflow clarity to a full feedback loop.

A couple of inline examples show only the handler construction; pairing them with the surrounding slog.New setup consistently would remove a minor execution gap.

DimensionReasoningScore

Conciseness

Lean, table-driven, and assumes Go/slog competence without explaining basics; minor restating of the pipeline rationale ('sampling before formatting saves CPU') could be trimmed.

4 / 5

Actionability

Multiple executable Go snippets (Router, Pipe+ThresholdSamplingOption, formatter middleware, Gin config) with concrete constructor and predicate names plus shutdown calls, covering the common cases copy-paste ready.

5 / 5

Workflow Clarity

The canonical 'record → Sampling → Pipe → Router → Sinks' ordering plus 'Common Mistakes' and 'Best Practices' provide a clear sequenced model with implicit checkpoints; no explicit validate-fix-retry loop, though the skill is design guidance rather than a destructive operation workflow.

4 / 5

Progressive Disclosure

SKILL.md is an overview with well-signaled, one-level-deep inline links to four real reference files (pipeline-patterns.md, sampling-strategies.md, http-middlewares.md, backend-handlers.md), each placed at its relevant section; content is appropriately split and easy to navigate.

5 / 5

Total

18

/

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, specific description that concretely lists capabilities by package and gives an explicit 'Apply when...' trigger tied to slog adoption and package imports. Minor room to add a few more natural synonyms for trigger terms.

DimensionReasoningScore

Specificity

Names multiple concrete capabilities — 'multi-handler pipelines (slog-multi)', 'log sampling (slog-sampling)', 'attribute formatting (slog-formatter)', 'HTTP middleware', 'backend routing' — with specific package names, giving comprehensive coverage.

5 / 5

Completeness

Explicitly states both what it does (structured logging extensions with named packages) and when to use it ('Apply when using or adopting slog, or when the codebase already imports any github.com/samber/slog-* package').

5 / 5

Trigger Term Quality

Includes natural terms like 'structured logging', 'log sampling', 'HTTP middleware', 'slog', and the import path 'github.com/samber/slog-*'; a few common synonyms (e.g. 'log shipping', 'log routing') are absent, so just short of comprehensive.

4 / 5

Distinctiveness Conflict Risk

Highly specific niche anchored to samber/slog-* packages with an explicit import-path trigger, giving a clear niche and minimal conflict risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

14

/

16

Passed

Repository
samber/cc-skills-golang
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.