Golang Observability
Instrument Go services for production — logging, metrics, tracing, profiling, RUM
- What
- Instrument Go services for production — logging, metrics, tracing, profiling, RUM
- Cost
- Free
- Needs
- a Go project with the Go toolchain installed
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — an always-on production observability playbook for Go: structured logging with slog, Prometheus metrics, OpenTelemetry distributed tracing, continuous profiling with pprof/Pyroscope, server-side RUM event tracking, alerting, and Grafana dashboards. Treats every unobserved production system as a liability: instrument proactively, correlate signals to diagnose, and never consider a feature done until it is observable. Distinct from the published samber-golang-benchmark and samber-golang-troubleshooting skills — those are for deep-dive performance investigation; this one is the everyday production signals layer. By @samber, listed here with credit to its creator. Honest caveats: requires a Go project and toolchain; it guides instrumentation decisions — it doesn't deploy your dashboards or wire your alerting infrastructure for you. Skill Harbor never reviews the code, review it yourself before use.
Version:
Install
Prerequisites: a Go project with the Go toolchain installed Install "Golang Observability" for me. Instrument Go services for production — logging, metrics, tracing, profiling, RUM Repository: https://github.com/samber/cc-skills-golang/blob/main/skills/golang-observability/SKILL.md 1. Fetch the SKILL.md file for the samber-golang-observability skill from the repository into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "samber-golang-observability". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.