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.
95
96%
Does it follow best practices?
Impact
98%
1.22xAverage score across 3 eval scenarios
Passed
No known issues
Quality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is an excellent skill description that clearly defines its niche in the samber/slog-* Go logging ecosystem. It lists specific capabilities and packages, includes abundant natural trigger terms that users would encounter in their codebases, and provides an explicit 'Apply when' clause with both intent-based and codebase-detection triggers. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and capabilities: multi-handler pipelines, log sampling, attribute formatting, HTTP middleware (with specific frameworks), and backend routing (with specific backends like Datadog, Sentry, Loki, etc.). | 3 / 3 |
Completeness | Clearly answers both 'what' (structured logging extensions with specific capabilities listed) and 'when' ('Apply when using or adopting slog, or when the codebase already imports any github.com/samber/slog-* package'). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms: 'slog', 'Golang', 'structured logging', specific package names like 'slog-multi', 'slog-fiber', 'slog-gin', 'slog-chi', 'slog-echo', 'slog-datadog', 'slog-sentry', and the import path 'github.com/samber/slog-*'. Users working with these packages would naturally use these terms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific ecosystem (samber/slog-* packages for Go's slog). The explicit package names and import paths make it extremely unlikely to conflict with general logging or Go skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that efficiently covers a complex ecosystem of 20+ packages with clear pipeline ordering, concrete code examples, and well-structured tables. The common mistakes and performance warnings sections add significant practical value. The main weakness is that all four referenced detail files are missing from the bundle, making the progressive disclosure structure incomplete in practice.
Suggestions
Provide the referenced bundle files (references/pipeline-patterns.md, references/sampling-strategies.md, references/http-middlewares.md, references/backend-handlers.md) to fulfill the progressive disclosure promises made in the skill body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is dense and efficient. Tables replace prose, code examples are minimal but complete, and it avoids explaining what slog is or how Go logging works. The persona line is slightly unnecessary but brief. Nearly every token earns its place. | 3 / 3 |
Actionability | Provides executable Go code for routing, sampling, formatting, and HTTP middleware. Constructor names, config struct fields, built-in predicates, and shutdown patterns are all concrete and copy-paste ready. | 3 / 3 |
Workflow Clarity | The pipeline model establishes a clear canonical ordering (sample → format → route → sink) with explicit rationale for why order matters. The 'Common Mistakes' table serves as a validation checklist, and the performance warnings section provides diagnostic guidance. The shutdown flush requirement for batch handlers is explicitly called out as a critical step. | 3 / 3 |
Progressive Disclosure | The skill references four detailed files (pipeline-patterns.md, sampling-strategies.md, http-middlewares.md, backend-handlers.md) with clear navigation signals, which is good structure. However, no bundle files are provided, so these references are unverifiable dead links. The cross-references to other skills are well-signaled. The main content is appropriately scoped as an overview. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_field | 'metadata' should map string keys to string values | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- samber/cc-skills-golang
- Commit
e9761db
- 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.