Observability and Instrumentation
Make production diagnosable — structured logs, metrics, traces, written alongside the feature
- What
- Make production diagnosable — structured logs, metrics, traces, written alongside the feature
- Cost
- Free
- Needs
- none
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — instrument code so production behavior is visible and diagnosable: define what "working" means before adding any instrumentation (telemetry without a question is noise — write down the 2–4 questions on-call will ask), pick the right signal per question (metrics tell you THAT something is wrong, traces tell you WHERE, logs tell you WHY), and write structured logs as JSON with stable event names and machine-readable fields. Instrumentation is not a post-launch add-on — it's written alongside the feature, the same way tests are; a feature shipped without telemetry turns the first user-reported bug into archaeology. Distinct from its sibling debugging-and-error-recovery: debugging diagnoses a failure happening right now; this skill builds the instrumentation that makes that skill fast next time. Complements the Go-specific samber-golang-observability already listed (that one is slog/Go-specific; this one is language-agnostic). Launch-day monitoring checklists belong to the sibling shipping-and-launch. By @addyosmani, listed here with credit to its creator. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Observability and Instrumentation is a free Muse skill that makes production diagnosable, with structured logs, metrics and traces written alongside the feature, so when something breaks in production you can trace what happened, where it started and why, instead of guessing from symptoms alone.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 1401c8bStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: none Install "Observability and Instrumentation" for me. Make production diagnosable — structured logs, metrics, traces, written alongside the feature Repository: https://raw.githubusercontent.com/addyosmani/agent-skills/1401c8b8030e023baeebb31781a6653fe8e93026/skills/observability-and-instrumentation/SKILL.md Pinned version: install the code at commit 1401c8b8030e023baeebb31781a6653fe8e93026 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the addyosmani-observability-and-instrumentation skill from the repository into a temporary folder 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 "addyosmani-observability-and-instrumentation". 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 1401c8b · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.