golang-observability Skill for Claude Code: Go Logging, Metrics and Tracing

Makes Claude instrument Go services with slog logging, Prometheus metrics, OpenTelemetry traces, profiling and alerts.

Installs: 40.8K; on skills.sh
Stars: 3.7K; on GitHub
Files: 8; besides SKILL.md
Updated: Nov 2026; last repo commit

golang-observability makes Claude treat a feature as unfinished until it is observable. It covers five signals: logs with slog, metrics with the Prometheus client, traces with OpenTelemetry, profiles with pprof or Pyroscope, and server-side RUM event tracking, plus alerting and Grafana dashboards.

It runs in three modes: instrumentation, review and audit. Audit mode can launch up to five sub-agents, one per signal. It bundles seven reference guides and no scripts. Its frontmatter lets Claude fetch web pages and search the web.

Good for

Go developers who ship services and want them observable from day one
Reviewers checking that a pull request exports the signals it should
Teams auditing how well a codebase is monitored

Install golang-observability

Claude Code

Copy this prompt.

Install the golang-observability skill in Claude Code. Run this command:

/plugin marketplace add samber/cc
/plugin install cc-skills-golang@samber

Then check that it loaded and tell me how to use it.

2
Paste it into Claude Code. It shows the change and asks before running it.

Pick one route, not several. The README says the skills cross-reference each other and a subset gives a partial and potentially inconsistent view, so the plugin or the whole-set CLI command is the better choice. The plugin installs the repo's 46 skill folders; its manifest declares no hooks, commands or MCP servers. Claude Code names plugin skills /plugin-name:skill-name, so after the plugin install the full name is /cc-skills-golang:golang-observability. The samber/cc marketplace lists seven plugins; the second command installs only cc-skills-golang.

From the project README. Source.

What's in the skill

When it loads

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

Sections in SKILL.md

Best Practices Summary
Cross-References
Go 1.26+: slog multi-handler
The Five Signals
Detailed Guides
Correlating Signals
Logs + Traces: otelslog bridge
Metrics + Traces: Exemplars
Migrating Legacy Loggers
Definition of Done for Observability
Common Mistakes

Key facts

Author: samber (metadata.author in SKILL.md)
License: MIT (license field in SKILL.md)
Version: 1.3.2 (metadata.version in SKILL.md)
Installs on skills.sh: 40,790 as of 2026-11-02
GitHub stars: 3,749 for the whole samber/cc-skills-golang repo, 2026-11-02
Last repo commit: 2026-11-01
What is inside: 9 files including SKILL.md: 7 reference guides, an evals file. No scripts.
Needs: Programs named in the SKILL.md frontmatter: go
Works in: Designed for Claude Code, Codex or similar harness, and for projects using Golang (compatibility field in SKILL.md)

What it includes

Add metrics, spans, structured logs and pprof toggles
The default mode, following a sequential instrumentation guide.
Write · Coding and instrumentation mode
Check that a PR exports the expected signals
Looks for declared metrics, opened and closed spans and consistent log fields.
Read · Review mode
Up to 5 sub-agents check metrics, logging, tracing, profiling and RUM
Used to audit observability coverage across a codebase, then merge findings.
Runs code · Audit mode
Thirteen rules, such as slog in JSON and low label cardinality
Includes preferring Histograms over Summaries for latency and propagating context everywhere.
Read · Best practices summary
Logs, metrics, traces, profiles and RUM, each with its tool
A table of the question each signal answers and when to use it.
Read · The five signals
Seven guides: logging, metrics, tracing, profiling, rum, alerting, dashboards
One deep dive per topic with code and configuration patterns.
Read · references/
Move from zap, logrus or zerolog to log/slog
A four-step strategy using bridge handlers.
Write · Legacy logger migration
Checklist: metrics, logging, spans, dashboards and alerts, RUM events
A feature is not production-ready until each item is covered.
Read · Definition of done

From the official docs

Permissions

Low risk

Claude can edit your Go files and run go and git commands while this skill is active. Work on a branch and read the diff before you commit.

What it can do

Read your data
Create and change things
Delete things
Read-only mode

Watch out for

It edits files and runs commands in your project
The frontmatter lists Edit, Write and these shell commands: go:*, golangci-lint:*, git:*. Work on a branch and read the diff before you commit. github.com
The RUM guide covers user tracking and consent
The skill includes server-side event tracking with PostHog or Segment, and its reference covers GDPR and CCPA consent checks and user deletion endpoints. Decide with your privacy owner what to track before Claude adds events. github.com
The recommended plugin route installs the whole repo
The plugin route and the --all skills CLI command add all 46 skill folders in the repo, not only this one. The plugin manifest (.claude-plugin/plugin.json, version 2.0.1) declares a name, description, author, license and keywords, and lists no hooks, commands or MCP servers. The skills CLI docs say --all installs every skill into every agent it supports without prompts. github.com

Technical details

Talks to	Web fetch/search through your assistant (WebFetch, WebSearch)
Sign-in and keys	SKILL.md names no account or API key.
Scopes	Reads and edits files in your Go project Runs the shell commands listed in the allowed-tools field: go:, golangci-lint:, git:*

Questions

What does golang-observability do?

It makes Claude add and review the signals a Go service needs in production: structured logs with slog, Prometheus metrics, OpenTelemetry traces, profiling, server-side user event tracking, alerts and Grafana dashboards.

How do I install golang-observability?

Install the whole golang set, not only this skill. The README calls the skills atomic, cross-referencing units and says a partial install gives a potentially inconsistent view. The install box lists the Claude Code plugin (/plugin marketplace add samber/cc, then /plugin install cc-skills-golang@samber), the skills CLI for the whole set or for this skill alone, and the README's Codex, Gemini CLI, Cursor and OpenCode routes. The README documents no Claude app route, so none is listed.

Do I need the other golang skills with golang-observability?

Installing the set is the safer choice. SKILL.md hands neighboring topics to other skills: golang-error-handling, golang-troubleshooting, golang-security, golang-context, samber/cc-skills@promql-cli (a skill in a different repo). The README says to install the general-purpose skills together, and the whole-set install does that.

What does golang-observability need on my machine?

The frontmatter names these programs: go. SKILL.md names no API key or account.

Is golang-observability safe?

It is instruction text and reference files, and the folder bundles no scripts. When you use it, Claude can edit files and run go, golangci-lint and git commands in your project, as its frontmatter allows. The frontmatter also lists WebFetch and WebSearch, so pages Claude opens are read into your conversation. Work on a branch, read the diff and approve commands you do not recognize.

golang-observability vs golang-troubleshooting?

golang-observability sets up the always-on signals. SKILL.md points to golang-troubleshooting for using those signals to diagnose production issues.

Does golang-observability work in Codex, Cursor or the Claude app?

The SKILL.md compatibility field says it is designed for Claude Code, Codex or a similar harness, and the README says the skills are built for Claude Code, Codex, Gemini, Copilot, Antigravity and Cursor. The install box covers Claude Code, Codex, Gemini CLI, Cursor, OpenCode and the skills CLI. The README documents no Claude app route.

Information

updated Nov 2, 2026

Repository: samber/cc-skills-golang
Folder: skills/golang-observability

samber/cc-skills-golang skills.sh

Sources

Docs, issue trackers and discussions this page is built from.

Show all 7

cc-skills-golang README · github.com
skills CLI commands · github.com
cc-skills-golang plugin.json · github.com
samber/cc marketplace.json · github.com
Claude Code skills · code.claude.com
golang-observability SKILL.md · github.com
golang-observability rum.md · github.com