Update to Vibe Coding

{
  "description": "Audit, fix or verify Prometheus, Grafana or VictoriaLogs signal semantics, alert rules, dashboards, correlation, tenant scope and cardinality costs in a repository.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 230
    },
    {
      "relative_path": "references/observability-semantics-cost-check.md",
      "size_in_bytes": 934
    },
    {
      "relative_path": "references/observability-stack-audit.md",
      "size_in_bytes": 2959
    },
    {
      "relative_path": "references/observability-stack-polish.md",
      "size_in_bytes": 1555
    }
  ],
  "name": "vibe-observability",
  "skill_md_contents": "---\nname: vibe-observability\ndescription: \"Audit, fix or verify Prometheus, Grafana or VictoriaLogs signal semantics, alert rules, dashboards, correlation, tenant scope and cardinality costs in a repository.\"\n---\n\n# Metrics, logs & alerts\n\nRead [the shared workflow](../../references/workflow.md) once per task, then the one recipe matching the requested operation and boundary. Do not load every recipe. The user's request controls scope and whether edits are allowed.\n\n## Recipes\n\n| Recipe | Operation |\n|---|---|\n| [Observability Semantics & Cost Check](references/observability-semantics-cost-check.md) | check |\n| [Observability Stack Audit](references/observability-stack-audit.md) | audit |\n| [Observability Stack Polish](references/observability-stack-polish.md) | implement |\n\nFor an explicit multi-stage request, follow the necessary stages without discarding requested work. For a single stage, deliver that result and stop. Use [the catalog](../../references/catalog.md) only if the requested boundary belongs elsewhere.\n"
}