Name: golang-observability
Rating: 90.6 (1 reviews)
Author: samber

golang-observability

Golang everyday observability — the always-on signals in production. Covers structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Apply when instrumenting Go services for production monitoring, setting up metrics or alerting, adding OpenTelemetry tracing, correlating logs with traces, migrating legacy loggers (zap/logrus/zerolog) to slog, adding observability to new features, or implementing GDPR/CCPA-compliant tracking with Customer Data Platforms (CDP). Not for temporary deep-dive performance investigation (→ See `samber/cc-skills-golang@golang-benchmark` and `samber/cc-skills-golang@golang-performance` skills).

1.38x

Quality

89%

Does it follow best practices?

Impact

93%

1.38x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

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 body with executable Go examples, good/bad pairs, and clean one-level-deep references. The skill is strong overall; the main improvement is tightening a few editorial sentences and surfacing an explicit inline validation loop for the instrumentation workflow.

Suggestions

Trim editorial rationale (e.g., 'the ecosystem has consolidated around it') that restates what Claude already knows about slog.

Add an explicit validate-fix-retry feedback loop to the inline instrumentation workflow rather than only in the Definition of Done checklist.

Consolidate the two separate mentions of awesome-prometheus-alerts (summary item 13 and alerting reference summary) to reduce redundancy.

Dimension	Reasoning	Score
Conciseness	Mostly lean and assumes Claude's competence — concise best-practices summary and code without over-explanation — with minor editorial padding (e.g., 'It is the standard library logger since Go 1.21, has a stable API, and the ecosystem has consolidated around it') that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready Go snippets (otelslog bridge, exemplar observe, slog multi-handler), concrete ✗/✓ common-mistake pairs, numbered migration steps, and a Definition of Done checklist covering the common cases.	5 / 5
Workflow Clarity	Clear sequenced modes (instrumentation, review, audit) and a numbered migration strategy plus a Definition of Done checklist provide most checkpoints, but the core instrumentation step-by-step with explicit validate-fix-retry feedback is partly deferred to the references rather than stated inline.	4 / 5
Progressive Disclosure	SKILL.md is an overview pointing to seven signal-specific references/*.md files, each linked with a one-line summary and verified to exist exactly one level deep, making navigation easy and content appropriately split.	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 precise, well-scoped description that states concrete capabilities, explicit use-when triggers, and a clear not-for boundary. It is among the strongest descriptions; the only minor gap is slight redundancy in trigger-term synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'instrumenting Go services for production monitoring', 'adding OpenTelemetry tracing', 'correlating logs with traces', 'migrating legacy loggers (zap/logrus/zerolog) to slog', 'implementing GDPR/CCPA-compliant tracking' — giving comprehensive coverage.	5 / 5
Completeness	Explicitly answers both what ('the always-on signals in production', with the covered signal list) and when ('Apply when instrumenting Go services for production monitoring, setting up metrics or alerting...'), with concrete trigger phrases and a 'Not for' boundary.	5 / 5
Trigger Term Quality	Good coverage of natural terms users would say ('metrics or alerting', 'OpenTelemetry tracing', 'correlating logs with traces', tool names zap/logrus/zerolog), but a few common-synonym phrasings are absent, sitting clearly above the 3 anchor but short of fully comprehensive.	4 / 5
Distinctiveness Conflict Risk	Clear niche (Go always-on production observability), distinct triggers, and explicit disambiguation ('Not for temporary deep-dive performance investigation -> See golang-benchmark/golang-performance') minimizes conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_field	'metadata' should map string keys to string values	Warning

	Total	15 / 16 Passed

Repository: samber/cc-skills-golang
Path: skills/golang-observability/SKILL.md
Commit: 19a0626

Reviewed: 1 day 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.