agentsclimarketplace

Observability bootstrap

Skill vishnujchandran/.agents/skills/observability-bootstrap

A curated collection of reusable AI agent skills, playbooks, and prompts for security audits, engineering workflows, and automation.

Install
npx -y skills add vishnujchandran/.agents --skill observability-bootstrap

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Production observability baseline skill for logs, metrics, traces, alerts, and SLI/SLO definitions with implementation-ready rollout and validation.

SKILL.md

2.8 KB, 591 tokens by cl100k_base, as published. Nobody here has run it

observability-bootstrap (v2.0)

Bootstrap practical, low-noise observability so teams can detect, diagnose, and resolve incidents quickly.

Trigger Signals

Use when user asks to:

  • add observability to a service/system
  • improve telemetry quality (logs/metrics/traces)
  • define baseline alerting and SLI/SLOs
  • remove production blind spots

Modes

  • audit-only (default): assess current telemetry and gaps
  • bootstrap-plan: implementation plan + starter artifacts
  • patch-safe: apply low-risk instrumentation/config updates (with confirmation)

Inputs

  • service type (api, worker, webhook, frontend, mixed)
  • environment tiers (dev/stage/prod)
  • incident priorities / reliability targets (if available)

Coverage Model

  1. Logs: structured, correlated, redacted
  2. Metrics: latency, throughput, errors, saturation
  3. Traces: end-to-end request/dependency visibility
  4. Alerts: actionable and owner-mapped
  5. SLI/SLO: measurable reliability objectives + error budget

Workflow

  1. Identify top critical user/API/background flows.
  2. Audit current telemetry pipeline and instrumentation coverage.
  3. Score maturity and map high-impact gaps.
  4. Define minimum viable observability baseline per flow.
  5. Draft SLI/SLO and alert policy with ownership/runbook mapping.
  6. Produce rollout plan (Phase 1/2/3) + verification checklist.

Minimum Baseline Checklist

  • Request/trace IDs propagated end-to-end
  • Structured logs include service/env/severity/correlation fields
  • PII/secrets redaction policy enforced
  • Golden signals captured for critical services
  • At least one SLI/SLO per critical flow
  • Alerts contain owner + runbook + clear trigger/resolution hints
  • Dashboard exists for top 3 critical flows

Output Contract

Return exactly:

  1. Observability maturity summary
  2. Gap table (priority | area | current | missing | impact | fix)
  3. Phase rollout plan (1/2/3)
  4. SLI/SLO + alert starter recommendations
  5. Verification checklist + next actions

Fail Conditions

Mark as not-operationally-ready if:

  • critical flow has no alertable error signal
  • no correlation ID/trace propagation on key paths
  • no ownership/runbook mapping for high-severity alerts

Templates

Use:

  • templates/sli-slo-template.md
  • templates/alert-policy-template.md

Guardrails

  • Prefer vendor-neutral standards unless user requests specific stack
  • Balance visibility with telemetry cost (sampling/retention guidance)
  • Never log secrets or sensitive personal data
  • Optimize for actionable alerts, not alert volume

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.