Observability Baseline
Scaffold-time observability so a shipped product is not blind in prod from day one — error capture (Sentry), request-id structured logging, and /healthz + /readyz endpoints. stack-baseline pins Sentry but nothing wires it; this is the wiring. Loaded by app-scaffolder (bake into the scaffold), infra-provisioner (prod env + probes), and consumed by l3-support (traces) and devops (deploy gate).
Install
npx skills add jeremybrasher/grokbot-skills --skill observability-baselinegit clone --depth 1 https://github.com/jeremybrasher/grokbot-skills.git /tmp/grokbot-skills
mkdir -p ~/.claude/skills
cp -r /tmp/grokbot-skills/collections/great-cto/skills/observability-baseline ~/.claude/skills/observability-baselinePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# observability-baseline stack-baseline names Sentry and wires it nowhere — so every shipped product's first prod incident is invisible, and l3-support triages blind. This skill makes three things exist at scaffold time. Defaults baked in; no founder question. ## 1. Error capture (Sentry) - `instrumentation.ts` (Next.js) / SDK init at process start; DSN from `SENTRY_DSN` env (never hardcoded). - CI uploads source maps on release so stack traces are readable (release = git sha). - Capture unhandled rejections + a global error boundary on the client. ## 2. Request-id structured logging - A logger that emits **JSON** (not `console.log` prose) with a per-request `request_id` (generate at the edge, propagate via header/async-local-storage). - Levels: error / warn / info / debug — diagnostics go to **stderr**, never mixed into user-facing stdout. (Same discipline as the CLI logging gap, DEEPEN d94.) - One log line per request with: request_id, method, path, status, latency_ms. ## 3. Health endpoints - `GET /healthz` — liveness (process up). `GET /readyz` — readiness (deps reachable: db, cache). Cheap, unauthenticated, no PII. - These are what infra-provisioner probes and what a load balancer checks. ## Wiring (a skill is shelfware unless a consumer loads it) | Consumer | What it does with this skill | |----------|------------------------------|
Details
- Skill name
observability-baseline- Repository
- jeremybrasher/grokbot-skills
- Path
collections/great-cto/skills/observability-baseline/SKILL.md- Repo updated
- 15 September 2026
FAQ
What does the Observability Baseline skill do?
Scaffold-time observability so a shipped product is not blind in prod from day one — error capture (Sentry), request-id structured logging, and /healthz + /readyz endpoints. stack-baseline pins Sentry but nothing wires it; this is the wiring. Loaded by app-scaffolder (bake into the scaffold), infra-provisioner (prod env + probes), and consumed by l3-support (traces) and devops (deploy gate).
How do I install the Observability Baseline skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add jeremybrasher/grokbot-skills --skill observability-baseline. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Observability Baseline popular?
It lives in jeremybrasher/grokbot-skills, which has 38 GitHub stars and 11 forks.
Related skills
Anti Patterns
38jeremybrasher/grokbot-skills
Catalogue of known SDLC anti-patterns that great_cto agents must actively reject when reviewing architecture, plans, code, or post-mortems. Used by architect (pre-impl), pm (planning), senior-dev (impl), l3-support (post-incident).
Anydesign
38jeremybrasher/grokbot-skills
Analyze images, websites, and Figma files to extract their design and generate a `design.md` with token system, component inventory, and reconstruction notes. Use this skill whenever the user wants to understand, document, replicate, or audit the design of something visual: a screenshot, a URL, a Figma link, a Pinterest reference, a mockup, a competitor's site, a component, a dashboard, a landing page. Also when they ask 'extract the design system from X', 'document the style of Y', 'analyze this visually', 'convert this image into tokens', 'help me replicate this design', 'what palette does t
Archetype Review Base
38jeremybrasher/grokbot-skills
Shared review framework that every domain reviewer (pci, oracle, gov, edtech, healthcare, mlops, etc.) MUST follow. Defines the output artifact (TM-{slug}.md), mandatory sections, severity scale, verdict format, the workflow scaffold (when-invoked, Step-0 read-inputs, HANDOFF), and the "domain heuristic vs generic check" boundary. Eliminates duplication across the ~30 reviewer prompts.
5g Deployment Plan
39lionelsimai/claude-skills-collection
Plan 5G network deployment with coverage. TRIGGERS - Use when user needs help with 5g-deployment-plan related tasks.
Vendor Evaluation
48sethdford/claude-skills
Systematically evaluate and select vendors for infrastructure, SaaS, or services.
AI Canary Deployment
39lionelsimai/claude-skills-collection
Design canary deployment strategies for AI. TRIGGERS - Use when user needs help with ai-canary-deployment related tasks.
Browse the most popular Claude skills, all devops & cloud skills, or write your own with the skills generator.