CtrlK
BlogDocsLog inGet started
Tessl Logo

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).

80

1.25x
Quality

93%

Does it follow best practices?

Impact

100%

1.25x

Average score across 1 eval scenario

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 balances inline executable examples with one-level-deep reference files. Main improvement is tightening the Best Practices Summary's explanatory phrasing and making the default instrumentation workflow's validation steps more explicit.

Suggestions

Trim explanatory padding in the Best Practices Summary bullets (e.g., "Histograms support server-side aggregation and percentile queries") to keep only the directive; the rationale already lives in the reference files.

Convert the default instrumentation workflow from the 13-item summary into a short explicit sequence with a validation checkpoint (e.g., "declare metrics → add spans → wire context → verify via Definition of Done checklist"), mirroring the migration section's numbered steps.

Shorten the opening "Observability is the ability to understand a system's internal state from its external outputs" sentence, which restates a concept Claude already knows.

DimensionReasoningScore

Conciseness

Largely efficient and assumes Claude's competence, but the Best Practices Summary bullets and the opening "Observability is the ability to understand a system's internal state..." sentence include mild explanatory padding that could be trimmed; not verbose enough to warrant a 3.

4 / 5

Actionability

Provides fully executable, copy-paste-ready code for the otelslog bridge, exemplar observation, slog multi-handler, and a concrete 4-step migration strategy, plus ✗/✓ Common Mistakes covering the common cases.

5 / 5

Workflow Clarity

Modes and the migration section give clear numbered sequences, and the Definition of Done checklist acts as a validation checkpoint, but the default instrumentation "sequential guide" is only implied via the summary list rather than an explicit validate→fix→retry loop.

4 / 5

Progressive Disclosure

The body is a concise overview with a clearly signaled "Detailed Guides" section pointing one level deep to seven real reference files (logging.md, metrics.md, tracing.md, profiling.md, rum.md, alerting.md, dashboards.md), each with a one-line description; bulk detail is appropriately split out.

5 / 5

Total

18

/

20

Passed

Description

100%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.

An exemplary description: specific, comprehensive, third-person, with explicit Use-when triggers and a clear not-for boundary. It covers all five observability signals and migration scenarios with natural phrasing.

DimensionReasoningScore

Specificity

Lists multiple specific concrete capabilities — "structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards" — giving comprehensive coverage of the domain's actions.

5 / 5

Completeness

Explicitly answers both what ("Covers structured logging with slog... Grafana dashboards") and when ("Apply when instrumenting Go services for production monitoring...") with concrete trigger phrases, plus an explicit "Not for..." boundary clause.

5 / 5

Trigger Term Quality

Comprehensive natural trigger phrases including synonyms and library names users actually say: "instrumenting Go services", "setting up metrics or alerting", "correlating logs with traces", "migrating legacy loggers (zap/logrus/zerolog) to slog", "GDPR/CCPA-compliant tracking", "Customer Data Platforms (CDP)".

5 / 5

Distinctiveness Conflict Risk

Clear niche (Go production observability) with named tools and an explicit "Not for temporary deep-dive performance investigation" boundary pointing to sibling skills, minimizing conflict risk.

5 / 5

Total

20

/

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

Total

15

/

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.