[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M718VM4G8WP1ED2TKAMC7ZG3":3,"skill-same:01M718VM4G8WP1ED2TKAMC7ZG3":200},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":44,"commitSha":45,"skillDirectory":46,"forksCount":47,"repositoryHtmlUrl":48,"repositoryHomepageUrl":6,"ownerHtmlUrl":49,"ownerBlogUrl":50,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M718VM4G8WP1ED2TKAMC7ZG3","oma-observability",null,"Intent-based observability + traceability router across layers, boundaries, and signals. Routes to vendor-specific skills via category taxonomy; owns transport tuning, meta-observability, incident forensics. Use for observability, traceability, telemetry, APM, RUM, metrics, logs, traces, profiles, SLO, incident forensics, tracing architecture work.","vasceannie\u002Fslopgate","vasceannie","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20271133?v=4","01M718RGA8VV2EF22XJEMXVQ0Q","Travis Vasceannie","01M718RGB0GWSXBBZBN67Q6NHQ",1,"MIT","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"oma observability","observability","profiles","traceability","layers","for","metrics","apm","tracing","tuning","intent","signals","work","router","across","logs","architecture","Meta","incident","slo","2026-11-10 10:12:30",false,"---\nname: oma-observability\ndescription: Intent-based observability + traceability router across layers,\n  boundaries, and signals. Routes to vendor-specific skills via category\n  taxonomy; owns transport tuning, meta-observability, incident forensics. Use\n  for observability, traceability, telemetry, APM, RUM, metrics, logs, traces,\n  profiles, SLO, incident forensics, tracing architecture work.\n---\n\n# Observability Agent - Intent-based Router\n\n## Scheduling\n\n### Goal\nRoute, design, tune, and review observability work across MELT+P signals, layers, boundaries, vendor categories, transport choices, meta-observability, and incident forensics.\n\n### Intent signature\n- User asks for observability, telemetry, OTel, metrics, logs, traces, profiles, SLOs, RUM, APM, incident forensics, trace propagation, transport tuning, or observability-as-code.\n- User needs vendor\u002Fcategory routing or observability architecture instead of a single vendor's already-covered setup.\n\n### When to use\n- Setting up an observability pipeline (OTel SDK + Collector + vendor backend)\n- Designing traceability across service and domain boundaries (W3C propagators, baggage, multi-tenant, multi-cloud)\n- Tuning transport layer (UDP\u002FMTU, OTLP gRPC vs HTTP, Collector DaemonSet vs sidecar topology)\n- Running incident forensics (6-dimension localization: code \u002F service \u002F layer \u002F host \u002F region \u002F infra)\n- Selecting a vendor category (OSS full-stack vs commercial SaaS vs high-cardinality specialist vs profiling specialist)\n- Implementing observability-as-code (Grafana Jsonnet dashboards, PrometheusRule CRD, OpenSLO YAML, SLO burn-rate alerts)\n- Meta-observability (pipeline self-health, clock skew detection, cardinality guardrails, retention matrix)\n- Covering the MELT+P signal set: metrics, logs, traces, profiles (OTEP 0239), cost (OpenCost), audit (SOC2\u002FISO), privacy (GDPR\u002FPIPA)\n- Evaluating log-pipeline migrations against current upstream support and project requirements\n\n### When NOT to use\n- LLM ops (prompt versioning, evals, gen_ai span deep dive); use Langfuse, Arize Phoenix, LangSmith, or Braintrust directly\n- Data pipeline lineage: use OpenLineage + Marquez, dbt test, or Airflow lineage backends\n- IoT \u002F hardware \u002F datacenter physical-layer telemetry (IPMI, BMC, SNMP); use vendor DCIM tooling (Nlyte, Sunbird, Device42)\n- Chaos engineering orchestration: use Chaos Mesh, Litmus, Gremlin, or ChaosToolkit (this skill consumes their telemetry; it does not orchestrate chaos)\n- GPU \u002F TPU infrastructure observability: use NVIDIA DCGM Exporter + Prometheus\n- Software supply chain (SBOM, attestation): use sigstore (cosign \u002F rekor), in-toto framework, SLSA level attestations\n- Incident response workflow (on-call rotation, paging, escalation); use PagerDuty, OpsGenie, or Grafana OnCall\n- Full TLS packet inspection: use packet-analysis or vendor TLS inspection tooling\n- Single-vendor setup already fully covered by that vendor's own published skill; invoke the vendor skill directly\n\n### Expected inputs\n- Observability intent, target system, architecture boundary, signals, vendor context, and incident symptoms if any\n- Existing OTel\u002Fcollector\u002Fvendor configs, dashboards, SLOs, trace\u002Flog\u002Fmetric examples, or deployment topology\n\n### Expected outputs\n- Routed observability guidance, setup\u002Fmigration\u002Ftuning plan, incident-forensics path, alerting\u002FSLO guidance, or observability-as-code recommendations\n- Transport, meta-observability, privacy, audit, and retention checks\n- Vendor delegation target when appropriate\n\n### Dependencies\nLoad resources conditionally: start with the execution protocol and one intent guide. Read only relevant matrix rows, then add a boundary, signal, or transport section when evidence requires it. The reference list is an index, not a preload list.\n\n- OTel\u002FW3C\u002FCNCF references and resources under `resources\u002F`\n- Vendor categories, matrix, standards, incident forensics, meta-observability, transport, layers, boundaries, and signal guides\n\n### Control-flow features\n- Branches by intent, vendor category, layer\u002Fboundary\u002Fsignal matrix, transport topology, privacy\u002Faudit risk, and incident localization dimension\n- May read\u002Fwrite observability config and docs; generally delegates vendor-specific implementation\n- Requires live status verification for load-bearing CNCF\u002Fvendor currency\n\n## Structural Flow\n\n### Entry\n1. Classify the intent: setup, migrate, investigate, alert, trace, tune, or route.\n2. Identify layers, boundaries, signals, and vendor category.\n3. Load only the relevant resource guide(s).\n\n### Scenes\n1. **PREPARE**: Classify intent and matrix coverage.\n2. **ACQUIRE**: Read configs, topology, telemetry examples, or incident signals.\n3. **REASON**: Route vendor\u002Fcategory, tune transport, assess meta-observability, or localize incident.\n4. **ACT**: Produce setup\u002Fmigration\u002Ftuning\u002Falert\u002Ftrace\u002Fforensics guidance or config changes.\n5. **VERIFY**: Check pipeline health, clock skew, cardinality, retention, privacy, and audit concerns.\n6. **FINALIZE**: Report route, evidence, risks, and handoff references.\n\n### Transitions\n- If a vendor-owned skill fully covers setup, delegate instead of duplicating docs.\n- If migration is requested, verify upstream support and compatibility before choosing a replacement.\n- If incident investigation is requested, use 6-dimensional localization.\n- If transport tuning appears, load transport-specific resources.\n\n### Failure and recovery\n- If live CNCF\u002Fvendor status is load-bearing, verify current status.\n- If telemetry samples are missing, provide instrumentation\u002Fcollection steps before analysis.\n- If scope belongs to out-of-scope domains, route to external authoritative tools.\n\n### Exit\n- Success: observability path is routed, evidence-backed, and checks are explicit.\n- Partial success: missing telemetry, stale vendor status, or external-domain handoff is explicit.\n\n## Logical Operations\n\n### Actions\n| Action | SSL primitive | Evidence |\n|--------|---------------|----------|\n| Classify observability intent | `SELECT` | Intent rules |\n| Read telemetry\u002Fconfig evidence | `READ` | OTel\u002Fvendor configs, dashboards, samples |\n| Route vendor\u002Fcategory | `SELECT` | Vendor categories |\n| Infer coverage gaps | `INFER` | Matrix and signal\u002Fboundary mapping |\n| Validate meta-observability | `VALIDATE` | Clock, cardinality, retention, health |\n| Write guidance\u002Fconfig | `WRITE` | OaC\u002Fconfig\u002Fdocs when requested |\n| Notify result | `NOTIFY` | Routed recommendation |\n\n### Tools and instruments\n- OTel\u002FCNCF\u002FW3C standards references\n- Vendor categories, matrix, incident forensics, meta-observability, transport and signal guides\n- Optional CLI\u002Fconfig tooling from the target stack\n\n### Canonical workflow path\n```text\n1. Classify intent: setup, migrate, investigate, alert, trace, tune, or route.\n2. Select layer\u002Fboundary\u002Fsignal coverage from `resources\u002Fmatrix.md`.\n3. Load the specific vendor, transport, incident, or signal guide before producing guidance.\n```\n\nWhen CNCF\u002Fvendor status is load-bearing, verify live state at `https:\u002F\u002Flandscape.cncf.io`.\n\n### Resource scope\n| Scope | Resource target |\n|-------|-----------------|\n| `CODEBASE` | Observability config, dashboards, alert rules, instrumentation |\n| `LOCAL_FS` | Resource guides and generated docs |\n| `NETWORK` | Vendor\u002FCNCF status and telemetry backends when checked |\n| `USER_DATA` | Incident symptoms, logs, metrics, traces, profiles |\n\n### Preconditions\n- Observability intent and system boundary are identifiable.\n- Relevant telemetry\u002Fconfig evidence is available or missing evidence is stated.\n\n### Effects and side effects\n- May recommend or modify observability config, dashboards, alerts, and instrumentation docs.\n- May route to vendor-owned skills or external tools.\n\n### Guardrails\n1. Classify intent and use `resources\u002Fvendor-categories.md` only when category selection or vendor delegation is needed.\n2. Load the transport guide matching the observed problem: UDP\u002FMTU, OTLP protocol, Collector topology, or sampling.\n3. Before declaring a setup complete, verify pipeline health, clock synchronization, cardinality limits, and retention against the project's requirements. Record checks that could not run.\n4. Verify current upstream support, attribute stability, and migration guidance when they affect the recommendation. Use official project documentation and CNCF status; stored versions are assumptions, not proof of current status.\n5. Use W3C Trace Context by default, with cloud translations from `resources\u002Fboundaries\u002Fcross-application.md` where required.\n6. Apply PII redaction and sampling-aware baggage controls at collection. Check retention, erasure, and audit requirements for the target system.\n7. Deliver working configuration or explicitly labeled proposals. Scaffolds and unverified checks cannot count as completed setup.\n\nThe coverage matrix has four layers (L3, L4, mesh, L7), four boundaries (multi-tenant, cross-application, SLO, release), and seven signals (metrics, logs, traces, profiles, cost, audit, privacy). Read matching rows in `resources\u002Fmatrix.md`; N\u002FA cells do not require implementation.\n\n### Routes (Intent)\n\n| Intent | Primary target | Fallback |\n|--------|---------------|----------|\n| `setup` | `resources\u002Fvendor-categories.md` → vendor-owned skill | Generic OTel semconv in `resources\u002Fstandards.md` |\n| `migrate` | Current upstream migration docs + `resources\u002Fvendor-categories.md` log-pipeline section | OTel Collector bridge config |\n| `investigate` | `resources\u002Fincident-forensics.md` (MRA + 6-dim localization) | `resources\u002Fsignals\u002Ftraces.md` + `resources\u002Fsignals\u002Flogs.md` |\n| `alert` | `resources\u002Fboundaries\u002Fslo.md` (burn-rate alert rules) | `resources\u002Fobservability-as-code.md` |\n| `trace` | `resources\u002Fboundaries\u002Fcross-application.md` (propagator matrix) | `resources\u002Flayers\u002Fmesh.md` (zero-code auto-instrumentation) |\n| `tune` | `resources\u002Ftransport\u002F` (4 files: UDP\u002FMTU, OTLP, topology, sampling) | `resources\u002Fmeta-observability.md` (cardinality guardrails) |\n| `route` | `resources\u002Fboundaries\u002Fmulti-tenant.md` + `resources\u002Ftransport\u002Fcollector-topology.md` | `resources\u002Fboundaries\u002Fcross-application.md` (data residency) |\n\n### Invocation and loading\nFor example: `\u002Foma-observability --investigate \"5xx spike in checkout\"`.\nOther skills pass the intent, system boundary, and evidence; the result returns guidance, checks, and any vendor handoff.\n\nRead `resources\u002Fexecution-protocol.md` first. Use the selected route above, then only relevant checklist sections before delivery. Load `resources\u002Fexamples.md` for an unfamiliar output shape and `resources\u002Fanti-patterns.md` only for the affected category. Do not load all transport, layer, boundary, and signal guides together.\n\n### Integrations with OMA Ecosystem\n\n| Skill | Integration point |\n|-------|------------------|\n| `oma-debug` | On failure: pull traces + logs by `request_id` → trigger `resources\u002Fincident-forensics.md` 6-dim localization playbook |\n| `oma-qa` | Canary post-deploy loop via chrome-devtools MCP: console errors + Core Web Vitals trend; INP\u002FLCP\u002FCLS from `resources\u002Flayers\u002FL7-application\u002Fweb-rum.md` |\n| `oma-tf-infra` | Terraform modules for OTel Collector, Grafana, and Loki stack provisioning |\n| `oma-scm` | Deployment SHA → `service.version` OTel attribute + release marker events; see `resources\u002Fboundaries\u002Frelease.md` |\n| `oma-backend` | Propagator and baggage rules; DB N+1 + Kafka patterns in `resources\u002Fsignals\u002Ftraces.md`. Back-reference: `oma-backend\u002FSKILL.md` §References \"Observability handoff\" |\n| `oma-frontend` | `resources\u002Flayers\u002FL7-application\u002Fweb-rum.md` INP\u002FLCP\u002FCLS checklist. Back-reference: `oma-frontend\u002FSKILL.md` §References \"Observability handoff\" |\n| `oma-mobile` | `resources\u002Flayers\u002FL7-application\u002Fmobile-rum.md` offline-queuing pattern. Back-reference: `oma-mobile\u002FSKILL.md` §References \"Observability handoff\" |\n| `oma-db` | `resources\u002Fsignals\u002Ftraces.md` DB patterns (N+1, connection pool). Back-reference: `oma-db\u002FSKILL.md` §References \"Observability handoff\" |\n\n### Versioning & Deprecation\n\n- **Spec version pinning**: `otel_spec` \u002F `otel_semconv` keys in each file's frontmatter document the assumed version. If content depends on a specific attribute stability tier, the tier is stated inline.\n- **Update triggers** (not scheduled):\n  - OTel semconv promotion (Development → RC → Stable) affecting attributes cited in this skill → update `resources\u002Fstandards.md` and the affected file, bump minor version.\n  - Attribute deprecation → replace across all citing files; migration note in `resources\u002Fstandards.md`.\n  - CNCF status change for a vendor\u002Fproject named in `vendor-categories.md` (Graduated \u002F Archived \u002F acquired) → update the vendor table.\n- **Authoritative live state**: `https:\u002F\u002Flandscape.cncf.io` for CNCF project status. This skill does not promise to track it on any schedule; verify at use time if the information is load-bearing.\n- **No per-file review stamps**: earlier drafts carried `last_reviewed` \u002F `next_review` frontmatter. Those were removed because no automated enforcement exists; relying on voluntary manual review produces stale stamps that misrepresent currency. Git history (`git log path\u002Fto\u002Ffile`) is the source of truth for when a file was last changed.\n\n### Contribution Protocol\n\n- Do NOT pre-declare future OMA skill names in user-facing documentation. If OMA-native coverage becomes warranted for an out-of-scope domain, evaluate and name it at that point.\n- File edits follow the ownership matrix in `docs\u002Fplans\u002Fdesigns\u002F005-oma-observability.md §Ownership`. CTO co-signs changes to `standards.md`, `matrix.md`, `anti-patterns.md`.\n- Run `resources\u002Fchecklist.md §1 Setup validation` before merging.\n\n## References\n- Execution steps: `resources\u002Fexecution-protocol.md`\n- Intent classification: `resources\u002Fintent-rules.md`\n- Coverage matrix: `resources\u002Fmatrix.md`\n- Standards (OTel spec, W3C, ISO): `resources\u002Fstandards.md`\n- Vendor categories: `resources\u002Fvendor-categories.md`\n- Incident forensics: `resources\u002Fincident-forensics.md`\n- Meta-observability: `resources\u002Fmeta-observability.md`\n- Observability-as-code: `resources\u002Fobservability-as-code.md`\n- Anti-patterns catalog (72 entries): `resources\u002Fanti-patterns.md`\n- Checklist: `resources\u002Fchecklist.md`\n- Examples: `resources\u002Fexamples.md`\n- Transport:\n  - `resources\u002Ftransport\u002Fudp-statsd-mtu.md`\n  - `resources\u002Ftransport\u002Fotlp-grpc-vs-http.md`\n  - `resources\u002Ftransport\u002Fcollector-topology.md`\n  - `resources\u002Ftransport\u002Fsampling-recipes.md`\n- Layers:\n  - `resources\u002Flayers\u002FL3-network.md`\n  - `resources\u002Flayers\u002FL4-transport.md`\n  - `resources\u002Flayers\u002Fmesh.md`\n  - `resources\u002Flayers\u002FL7-application\u002Fweb-rum.md`\n  - `resources\u002Flayers\u002FL7-application\u002Fmobile-rum.md`\n  - `resources\u002Flayers\u002FL7-application\u002Fcrash-analytics.md`\n  - `resources\u002Flayers\u002FL7-application\u002Fwaf.md`\n- Boundaries:\n  - `resources\u002Fboundaries\u002Fmulti-tenant.md`\n  - `resources\u002Fboundaries\u002Fcross-application.md`\n  - `resources\u002Fboundaries\u002Fslo.md`\n  - `resources\u002Fboundaries\u002Frelease.md`\n- Signals:\n  - `resources\u002Fsignals\u002Fmetrics.md`\n  - `resources\u002Fsignals\u002Flogs.md`\n  - `resources\u002Fsignals\u002Ftraces.md`\n  - `resources\u002Fsignals\u002Fprofiles.md`\n  - `resources\u002Fsignals\u002Fcost.md`\n  - `resources\u002Fsignals\u002Faudit.md`\n  - `resources\u002Fsignals\u002Fprivacy.md`","# Observability Agent - Intent-based Router\n\n## Scheduling\n\n### Goal\nRoute, design, tune, and review observability work across MELT+P signals, layers, boundaries, vendor categories, transport choices, meta-observability, and incident forensics.\n\n### Intent signature\n- User asks for observability, telemetry, OTel, metrics, logs, traces, profiles, SLOs, RUM, APM, incident forensics, trace propagation, transport tuning, or observability-as-code.\n- User needs vendor\u002Fcategory routing or observability architecture instead of a single vendor's already-covered setup.\n\n### When to use\n- Setting up an observability pipeline (OTel SDK + Collector + vendor backend)\n- Designing traceability across service and domain boundaries (W3C propagators, baggage, multi-tenant, multi-cloud)\n- Tuning transport layer (UDP\u002FMTU, OTLP gRPC vs HTTP, Collector DaemonSet vs sidecar topology)\n- Running incident forensics (6-dimension localization: code \u002F service \u002F layer \u002F host \u002F region \u002F infra)\n- Selecting a vendor category (OSS full-stack vs commercial SaaS vs high-cardinality specialist vs profiling specialist)\n- Implementing observability-as-code (Grafana Jsonnet dashboards, PrometheusRule CRD, OpenSLO YAML, SLO burn-rate alerts)\n- Meta-observability (pipeline self-health, clock skew detection, cardinality guardrails, retention matrix)\n- Covering the MELT+P signal set: metrics, logs, traces, profiles (OTEP 0239), cost (OpenCost), audit (SOC2\u002FISO), privacy (GDPR\u002FPIPA)\n- Evaluating log-pipeline migrations against current upstream support and project requirements\n\n### When NOT to use\n- LLM ops (prompt versioning, evals, gen_ai span deep dive); use Langfuse, Arize Phoenix, LangSmith, or Braintrust directly\n- Data pipeline lineage: use OpenLineage + Marquez, dbt test, or Airflow lineage backends\n- IoT \u002F hardware \u002F datacenter physical-layer telemetry (IPMI, BMC, SNMP); use vendor DCIM tooling (Nlyte, Sunbird, Device42)\n- Chaos engineering orchestration: use Chaos Mesh, Litmus, Gremlin, or ChaosToolkit (this skill consumes their telemetry; it does not orchestrate chaos)\n- GPU \u002F TPU infrastructure observability: use NVIDIA DCGM Exporter + Prometheus\n- Software supply chain (SBOM, attestation): use sigstore (cosign \u002F rekor), in-toto framework, SLSA level attestations\n- Incident response workflow (on-call rotation, paging, escalation); use PagerDuty, OpsGenie, or Grafana OnCall\n- Full TLS packet inspection: use packet-analysis or vendor TLS inspection tooling\n- Single-vendor setup already fully covered by that vendor's own published skill; invoke the vendor skill directly\n\n### Expected inputs\n- Observability intent, target system, architecture boundary, signals, vendor context, and incident symptoms if any\n- Existing OTel\u002Fcollector\u002Fvendor configs, dashboards, SLOs, trace\u002Flog\u002Fmetric examples, or deployment topology\n\n### Expected outputs\n- Routed observability guidance, setup\u002Fmigration\u002Ftuning plan, incident-forensics path, alerting\u002FSLO guidance, or observability-as-code recommendations\n- Transport, meta-observability, privacy, audit, and retention checks\n- Vendor delegation target when appropriate\n\n### Dependencies\nLoad resources conditionally: start with the execution protocol and one intent guide. Read only relevant matrix rows, then add a boundary, signal, or transport section when evidence requires it. The reference list is an index, not a preload list.\n\n- OTel\u002FW3C\u002FCNCF references and resources under `resources\u002F`\n- Vendor categories, matrix, standards, incident forensics, meta-observability, transport, layers, boundaries, and signal guides\n\n### Control-flow features\n- Branches by intent, vendor category, layer\u002Fboundary\u002Fsignal matrix, transport topology, privacy\u002Faudit risk, and incident localization dimension\n- May read\u002Fwrite observability config and docs; generally delegates vendor-specific implementation\n- Requires live status verification for load-bearing CNCF\u002Fvendor currency\n\n## Structural Flow\n\n### Entry\n1. Classify the intent: setup, migrate, investigate, alert, trace, tune, or route.\n2. Identify layers, boundaries, signals, and vendor category.\n3. Load only the relevant resource guide(s).\n\n### Scenes\n1. **PREPARE**: Classify intent and matrix coverage.\n2. **ACQUIRE**: Read configs, topology, telemetry examples, or incident signals.\n3. **REASON**: Route vendor\u002Fcategory, tune transport, assess meta-observability, or localize incident.\n4. **ACT**: Produce setup\u002Fmigration\u002Ftuning\u002Falert\u002Ftrace\u002Fforensics guidance or config changes.\n5. **VERIFY**: Check pipeline health, clock skew, cardinality, retention, privacy, and audit concerns.\n6. **FINALIZE**: Report route, evidence, risks, and handoff references.\n\n### Transitions\n- If a vendor-owned skill fully covers setup, delegate instead of duplicating docs.\n- If migration is requested, verify upstream support and compatibility before choosing a replacement.\n- If incident investigation is requested, use 6-dimensional localization.\n- If transport tuning appears, load transport-specific resources.\n\n### Failure and recovery\n- If live CNCF\u002Fvendor status is load-bearing, verify current status.\n- If telemetry samples are missing, provide instrumentation\u002Fcollection steps before analysis.\n- If scope belongs to out-of-scope domains, route to external authoritative tools.\n\n### Exit\n- Success: observability path is routed, evidence-backed, and checks are explicit.\n- Partial success: missing telemetry, stale vendor status, or external-domain handoff is explicit.\n\n## Logical Operations\n\n### Actions\n| Action | SSL primitive | Evidence |\n|--------|---------------|----------|\n| Classify observability intent | `SELECT` | Intent rules |\n| Read telemetry\u002Fconfig evidence | `READ` | OTel\u002Fvendor configs, dashboards, samples |\n| Route vendor\u002Fcategory | `SELECT` | Vendor categories |\n| Infer coverage gaps | `INFER` | Matrix and signal\u002Fboundary mapping |\n| Validate meta-observability | `VALIDATE` | Clock, cardinality, retention, health |\n| Write guidance\u002Fconfig | `WRITE` | OaC\u002Fconfig\u002Fdocs when requested |\n| Notify result | `NOTIFY` | Routed recommendation |\n\n### Tools and instruments\n- OTel\u002FCNCF\u002FW3C standards references\n- Vendor categories, matrix, incident forensics, meta-observability, transport and signal guides\n- Optional CLI\u002Fconfig tooling from the target stack\n\n### Canonical workflow path\n```text\n1. Classify intent: setup, migrate, investigate, alert, trace, tune, or route.\n2. Select layer\u002Fboundary\u002Fsignal coverage from `resources\u002Fmatrix.md`.\n3. Load the specific vendor, transport, incident, or signal guide before producing guidance.\n```\n\nWhen CNCF\u002Fvendor status is load-bearing, verify live state at `https:\u002F\u002Flandscape.cncf.io`.\n\n### Resource scope\n| Scope | Resource target |\n|-------|-----------------|\n| `CODEBASE` | Observability config, dashboards, alert rules, instrumentation |\n| `LOCAL_FS` | Resource guides and generated docs |\n| `NETWORK` | Vendor\u002FCNCF status and telemetry backends when checked |\n| `USER_DATA` | Incident symptoms, logs, metrics, traces, profiles |\n\n### Preconditions\n- Observability intent and system boundary are identifiable.\n- Relevant telemetry\u002Fconfig evidence is available or missing evidence is stated.\n\n### Effects and side effects\n- May recommend or modify observability config, dashboards, alerts, and instrumentation docs.\n- May route to vendor-owned skills or external tools.\n\n### Guardrails\n1. Classify intent and use `resources\u002Fvendor-categories.md` only when category selection or vendor delegation is needed.\n2. Load the transport guide matching the observed problem: UDP\u002FMTU, OTLP protocol, Collector topology, or sampling.\n3. Before declaring a setup complete, verify pipeline health, clock synchronization, cardinality limits, and retention against the project's requirements. Record checks that could not run.\n4. Verify current upstream support, attribute stability, and migration guidance when they affect the recommendation. Use official project documentation and CNCF status; stored versions are assumptions, not proof of current status.\n5. Use W3C Trace Context by default, with cloud translations from `resources\u002Fboundaries\u002Fcross-application.md` where required.\n6. Apply PII redaction and sampling-aware baggage controls at collection. Check retention, erasure, and audit requirements for the target system.\n7. Deliver working configuration or explicitly labeled proposals. Scaffolds and unverified checks cannot count as completed setup.\n\nThe coverage matrix has four layers (L3, L4, mesh, L7), four boundaries (multi-tenant, cross-application, SLO, release), and seven signals (metrics, logs, traces, profiles, cost, audit, privacy). Read matching rows in `resources\u002Fmatrix.md`; N\u002FA cells do not require implementation.\n\n### Routes (Intent)\n\n| Intent | Primary target | Fallback |\n|--------|---------------|----------|\n| `setup` | `resources\u002Fvendor-categories.md` → vendor-owned skill | Generic OTel semconv in `resources\u002Fstandards.md` |\n| `migrate` | Current upstream migration docs + `resources\u002Fvendor-categories.md` log-pipeline section | OTel Collector bridge config |\n| `investigate` | `resources\u002Fincident-forensics.md` (MRA + 6-dim localization) | `resources\u002Fsignals\u002Ftraces.md` + `resources\u002Fsignals\u002Flogs.md` |\n| `alert` | `resources\u002Fboundaries\u002Fslo.md` (burn-rate alert rules) | `resources\u002Fobservability-as-code.md` |\n| `trace` | `resources\u002Fboundaries\u002Fcross-application.md` (propagator matrix) | `resources\u002Flayers\u002Fmesh.md` (zero-code auto-instrumentation) |\n| `tune` | `resources\u002Ftransport\u002F` (4 files: UDP\u002FMTU, OTLP, topology, sampling) | `resources\u002Fmeta-observability.md` (cardinality guardrails) |\n| `route` | `resources\u002Fboundaries\u002Fmulti-tenant.md` + `resources\u002Ftransport\u002Fcollector-topology.md` | `resources\u002Fboundaries\u002Fcross-application.md` (data residency) |\n\n### Invocation and loading\nFor example: `\u002Foma-observability --investigate \"5xx spike in checkout\"`.\nOther skills pass the intent, system boundary, and evidence; the result returns guidance, checks, and any vendor handoff.\n\nRead `resources\u002Fexecution-protocol.md` first. Use the selected route above, then only relevant checklist sections before delivery. Load `resources\u002Fexamples.md` for an unfamiliar output shape and `resources\u002Fanti-patterns.md` only for the affected category. Do not load all transport, layer, boundary, and signal guides together.\n\n### Integrations with OMA Ecosystem\n\n| Skill | Integration point |\n|-------|------------------|\n| `oma-debug` | On failure: pull traces + logs by `request_id` → trigger `resources\u002Fincident-forensics.md` 6-dim localization playbook |\n| `oma-qa` | Canary post-deploy loop via chrome-devtools MCP: console errors + Core Web Vitals trend; INP\u002FLCP\u002FCLS from `resources\u002Flayers\u002FL7-application\u002Fweb-rum.md` |\n| `oma-tf-infra` | Terraform modules for OTel Collector, Grafana, and Loki stack provisioning |\n| `oma-scm` | Deployment SHA → `service.version` OTel attribute + release marker events; see `resources\u002Fboundaries\u002Frelease.md` |\n| `oma-backend` | Propagator and baggage rules; DB N+1 + Kafka patterns in `resources\u002Fsignals\u002Ftraces.md`. Back-reference: `oma-backend\u002FSKILL.md` §References \"Observability handoff\" |\n| `oma-frontend` | `resources\u002Flayers\u002FL7-application\u002Fweb-rum.md` INP\u002FLCP\u002FCLS checklist. Back-reference: `oma-frontend\u002FSKILL.md` §References \"Observability handoff\" |\n| `oma-mobile` | `resources\u002Flayers\u002FL7-application\u002Fmobile-rum.md` offline-queuing pattern. Back-reference: `oma-mobile\u002FSKILL.md` §References \"Observability handoff\" |\n| `oma-db` | `resources\u002Fsignals\u002Ftraces.md` DB patterns (N+1, connection pool). Back-reference: `oma-db\u002FSKILL.md` §References \"Observability handoff\" |\n\n### Versioning & Deprecation\n\n- **Spec version pinning**: `otel_spec` \u002F `otel_semconv` keys in each file's frontmatter document the assumed version. If content depends on a specific attribute stability tier, the tier is stated inline.\n- **Update triggers** (not scheduled):\n  - OTel semconv promotion (Development → RC → Stable) affecting attributes cited in this skill → update `resources\u002Fstandards.md` and the affected file, bump minor version.\n  - Attribute deprecation → replace across all citing files; migration note in `resources\u002Fstandards.md`.\n  - CNCF status change for a vendor\u002Fproject named in `vendor-categories.md` (Graduated \u002F Archived \u002F acquired) → update the vendor table.\n- **Authoritative live state**: `https:\u002F\u002Flandscape.cncf.io` for CNCF project status. This skill does not promise to track it on any schedule; verify at use time if the information is load-bearing.\n- **No per-file review stamps**: earlier drafts carried `last_reviewed` \u002F `next_review` frontmatter. Those were removed because no automated enforcement exists; relying on voluntary manual review produces stale stamps that misrepresent currency. Git history (`git log path\u002Fto\u002Ffile`) is the source of truth for when a file was last changed.\n\n### Contribution Protocol\n\n- Do NOT pre-declare future OMA skill names in user-facing documentation. If OMA-native coverage becomes warranted for an out-of-scope domain, evaluate and name it at that point.\n- File edits follow the ownership matrix in `docs\u002Fplans\u002Fdesigns\u002F005-oma-observability.md §Ownership`. CTO co-signs changes to `standards.md`, `matrix.md`, `anti-patterns.md`.\n- Run `resources\u002Fchecklist.md §1 Setup validation` before merging.\n\n## References\n- Execution steps: `resources\u002Fexecution-protocol.md`\n- Intent classification: `resources\u002Fintent-rules.md`\n- Coverage matrix: `resources\u002Fmatrix.md`\n- Standards (OTel spec, W3C, ISO): `resources\u002Fstandards.md`\n- Vendor categories: `resources\u002Fvendor-categories.md`\n- Incident forensics: `resources\u002Fincident-forensics.md`\n- Meta-observability: `resources\u002Fmeta-observability.md`\n- Observability-as-code: `resources\u002Fobservability-as-code.md`\n- Anti-patterns catalog (72 entries): `resources\u002Fanti-patterns.md`\n- Checklist: `resources\u002Fchecklist.md`\n- Examples: `resources\u002Fexamples.md`\n- Transport:\n  - `resources\u002Ftransport\u002Fudp-statsd-mtu.md`\n  - `resources\u002Ftransport\u002Fotlp-grpc-vs-http.md`\n  - `resources\u002Ftransport\u002Fcollector-topology.md`\n  - `resources\u002Ftransport\u002Fsampling-recipes.md`\n- Layers:\n  - `resources\u002Flayers\u002FL3-network.md`\n  - `resources\u002Flayers\u002FL4-transport.md`\n  - `resources\u002Flayers\u002Fmesh.md`\n  - `resources\u002Flayers\u002FL7-application\u002Fweb-rum.md`\n  - `resources\u002Flayers\u002FL7-application\u002Fmobile-rum.md`\n  - `resources\u002Flayers\u002FL7-application\u002Fcrash-analytics.md`\n  - `resources\u002Flayers\u002FL7-application\u002Fwaf.md`\n- Boundaries:\n  - `resources\u002Fboundaries\u002Fmulti-tenant.md`\n  - `resources\u002Fboundaries\u002Fcross-application.md`\n  - `resources\u002Fboundaries\u002Fslo.md`\n  - `resources\u002Fboundaries\u002Frelease.md`\n- Signals:\n  - `resources\u002Fsignals\u002Fmetrics.md`\n  - `resources\u002Fsignals\u002Flogs.md`\n  - `resources\u002Fsignals\u002Ftraces.md`\n  - `resources\u002Fsignals\u002Fprofiles.md`\n  - `resources\u002Fsignals\u002Fcost.md`\n  - `resources\u002Fsignals\u002Faudit.md`\n  - `resources\u002Fsignals\u002Fprivacy.md`",{"name":5,"description":7},"master","5fab8004af1390aa17b3447f2780766c8bf2482c",".agents\u002Fskills\u002Foma-observability",0,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate","https:\u002F\u002Fgithub.com\u002Fvasceannie","thingswithstuff.io","2026-11-10 23:25:49",{"source":8,"skillName":5,"commands":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add vasceannie\u002Fslopgate --skill oma-observability",{"tool":58,"command":59},"bunx","bunx skills add vasceannie\u002Fslopgate --skill oma-observability",{"tool":61,"command":62},"pnpm","pnpm dlx skills add vasceannie\u002Fslopgate --skill oma-observability","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002FSKILL.md",true,[66,72,76,80,84,88,92,96,100,104,108,112,116,120,124,128,132,136,140,144,148,152,156,160,164,168,172,176,180,184,188,192,196],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"resources\u002Fanti-patterns.md","REFERENCE","参考文档",46754,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fanti-patterns.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"resources\u002Fboundaries\u002Fcross-application.md",19919,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fboundaries\u002Fcross-application.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"resources\u002Fboundaries\u002Fmulti-tenant.md",18334,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fboundaries\u002Fmulti-tenant.md",{"path":81,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":82,"sourceHtmlUrl":83},"resources\u002Fboundaries\u002Frelease.md",12723,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fboundaries\u002Frelease.md",{"path":85,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":86,"sourceHtmlUrl":87},"resources\u002Fboundaries\u002Fslo.md",6607,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fboundaries\u002Fslo.md",{"path":89,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":90,"sourceHtmlUrl":91},"resources\u002Fchecklist.md",15309,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fchecklist.md",{"path":93,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":94,"sourceHtmlUrl":95},"resources\u002Fexamples.md",16049,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fexamples.md",{"path":97,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":98,"sourceHtmlUrl":99},"resources\u002Fexecution-protocol.md",9729,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fexecution-protocol.md",{"path":101,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":102,"sourceHtmlUrl":103},"resources\u002Fincident-forensics.md",23881,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fincident-forensics.md",{"path":105,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":106,"sourceHtmlUrl":107},"resources\u002Fintent-rules.md",12058,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fintent-rules.md",{"path":109,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":110,"sourceHtmlUrl":111},"resources\u002Flayers\u002FL3-network.md",18018,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Flayers\u002FL3-network.md",{"path":113,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":114,"sourceHtmlUrl":115},"resources\u002Flayers\u002FL4-transport.md",14944,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Flayers\u002FL4-transport.md",{"path":117,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":118,"sourceHtmlUrl":119},"resources\u002Flayers\u002FL7-application\u002Fcrash-analytics.md",18022,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Flayers\u002FL7-application\u002Fcrash-analytics.md",{"path":121,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":122,"sourceHtmlUrl":123},"resources\u002Flayers\u002FL7-application\u002Fmobile-rum.md",16209,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Flayers\u002FL7-application\u002Fmobile-rum.md",{"path":125,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":126,"sourceHtmlUrl":127},"resources\u002Flayers\u002FL7-application\u002Fwaf.md",17044,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Flayers\u002FL7-application\u002Fwaf.md",{"path":129,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":130,"sourceHtmlUrl":131},"resources\u002Flayers\u002FL7-application\u002Fweb-rum.md",17763,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Flayers\u002FL7-application\u002Fweb-rum.md",{"path":133,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":134,"sourceHtmlUrl":135},"resources\u002Flayers\u002Fmesh.md",20487,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Flayers\u002Fmesh.md",{"path":137,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":138,"sourceHtmlUrl":139},"resources\u002Fmatrix.md",21579,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fmatrix.md",{"path":141,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":142,"sourceHtmlUrl":143},"resources\u002Fmeta-observability.md",24076,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fmeta-observability.md",{"path":145,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":146,"sourceHtmlUrl":147},"resources\u002Fobservability-as-code.md",22352,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fobservability-as-code.md",{"path":149,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":150,"sourceHtmlUrl":151},"resources\u002Fsignals\u002Faudit.md",14260,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fsignals\u002Faudit.md",{"path":153,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":154,"sourceHtmlUrl":155},"resources\u002Fsignals\u002Fcost.md",17601,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fsignals\u002Fcost.md",{"path":157,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":158,"sourceHtmlUrl":159},"resources\u002Fsignals\u002Flogs.md",10431,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fsignals\u002Flogs.md",{"path":161,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":162,"sourceHtmlUrl":163},"resources\u002Fsignals\u002Fmetrics.md",20045,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fsignals\u002Fmetrics.md",{"path":165,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":166,"sourceHtmlUrl":167},"resources\u002Fsignals\u002Fprivacy.md",17955,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fsignals\u002Fprivacy.md",{"path":169,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":170,"sourceHtmlUrl":171},"resources\u002Fsignals\u002Fprofiles.md",15523,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fsignals\u002Fprofiles.md",{"path":173,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":174,"sourceHtmlUrl":175},"resources\u002Fsignals\u002Ftraces.md",19557,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fsignals\u002Ftraces.md",{"path":177,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":178,"sourceHtmlUrl":179},"resources\u002Fstandards.md",13028,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fstandards.md",{"path":181,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":182,"sourceHtmlUrl":183},"resources\u002Ftransport\u002Fcollector-topology.md",12144,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Ftransport\u002Fcollector-topology.md",{"path":185,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":186,"sourceHtmlUrl":187},"resources\u002Ftransport\u002Fotlp-grpc-vs-http.md",7807,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Ftransport\u002Fotlp-grpc-vs-http.md",{"path":189,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":190,"sourceHtmlUrl":191},"resources\u002Ftransport\u002Fsampling-recipes.md",11302,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Ftransport\u002Fsampling-recipes.md",{"path":193,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":194,"sourceHtmlUrl":195},"resources\u002Ftransport\u002Fudp-statsd-mtu.md",6425,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Ftransport\u002Fudp-statsd-mtu.md",{"path":197,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":198,"sourceHtmlUrl":199},"resources\u002Fvendor-categories.md",18159,"https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002F.agents\u002Fskills\u002Foma-observability\u002Fresources\u002Fvendor-categories.md",[201,233,260,297,322,343],{"skillNo":202,"name":203,"nameZh":6,"description":204,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":205,"categories":206,"keywords":212,"publishedAt":39},"01M71951JDWCYMS8GDC2C7395D","type-strictness","Enforce strict type compliance by eliminating `Any` types and `# type: ignore` comments. Use when:\n(1) Editing code that contains `Any` as a type annotation\n(2) Code has `# type: ignore` or `# pyright: ignore` comments\n(3) User requests type fixes or type strictness enforcement\n(4) Importing from untyped third-party libraries\n(5) User asks to \"fix types\", \"remove Any\", or \"add proper typing\"\n(6) Pyrefly or mypy reports type errors that need resolution\n(7) Code review reveals weak typing patterns\nFollows hierarchical resolution: codebase inference → type stubs → library inspection → type guards → casting (last resort).","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Ftype-strictness\u002FSKILL.md",[207],{"categoryNo":208,"categoryName":209,"taxonomyType":210,"taxonomyTypeDesc":211},"01JBSEEDCAT000000000000007","代码审查","SCENARIO","使用场景",[213,214,215,216,217,218,219,220,221,222,223,224,225,226,227,228,229,230,231,232],"type","type strictness","typing","types","remove","code review","fix","errors","inspection","when","code","review","reports","libraries","casting","pyrefly","mypy","pyright","library","patterns",{"skillNo":234,"name":235,"nameZh":6,"description":236,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":237,"categories":238,"keywords":243,"publishedAt":39},"01M7194XGBQXSE7Y5BZ4K5CSTK","slopgate-test-extender","Extend Python test suites with parametrization, fixture reuse, and quality enforcement. Use when asked to add tests, extend existing tests, improve test coverage, consolidate duplicate tests, fix test quality issues, or when Slopgate reports untested-production-code, missing test references, or coverage gaps. Triggers on requests like \"add tests for X\", \"extend these tests\", \"parametrize tests\", \"consolidate tests\", \"fix test quality\", \"improve test coverage\", \"write tests for this function\", \"test this module\", \"behavior tests\", \"integration tests\", \"missing tests\", \"coverage holes\", \"untested code\", or when a hook denies with test-related findings.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-test-extender\u002FSKILL.md",[239,240],{"categoryNo":208,"categoryName":209,"taxonomyType":210,"taxonomyTypeDesc":211},{"categoryNo":241,"categoryName":242,"taxonomyType":210,"taxonomyTypeDesc":211},"01JBSEEDCAT000000000000008","测试与质量",[244,245,246,247,248,219,249,250,251,252,253,254,222,223,255,256,225,257,258,259],"slopgate test extender","test","coverage","fixture","testing","issues","write tests","improve","only","cleanup","loop","candidate","consolidate","references","opencode","orchestrator",{"skillNo":261,"name":262,"nameZh":6,"description":263,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":264,"categories":265,"keywords":281,"publishedAt":39},"01M7194RMVQS5YJJ4ZEFXX20VS","slopgate-intelligent-coding-patterns","Pattern-selection playbook for agents editing code with complex branching, stateful parsers\u002Fworkflows, duplicated skeletons, policy checks, or ordered transforms. Load before refactoring if\u002Felif dispatch chains, boolean-flag state machines, repeated validation predicates, parallel provider\u002Flanguage implementations, or regex\u002Fcontent transformation pipelines. Also load when asked to \"apply a design pattern\", \"which pattern should I use here\", \"refactor this switch statement\", \"replace if-elif chain\", \"state machine pattern\", \"strategy pattern\", \"template method\", \"pipeline pattern\", \"specification pattern\", \"dispatch table\", \"guard clause refactor\", \"reduce cyclomatic complexity\", or when Slopgate fires PY-CODE-014, PY-CODE-017, PY-CODE-018, QUALITY-LINT-001, or PY-QUALITY-010. Use with behavior-locking tests and avoid pattern theater for simple one-off code.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-intelligent-coding-patterns\u002FSKILL.md",[266,267,270,273,278],{"categoryNo":208,"categoryName":209,"taxonomyType":210,"taxonomyTypeDesc":211},{"categoryNo":268,"categoryName":269,"taxonomyType":210,"taxonomyTypeDesc":211},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":271,"categoryName":272,"taxonomyType":210,"taxonomyTypeDesc":211},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":274,"categoryName":275,"taxonomyType":276,"taxonomyTypeDesc":277},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",{"categoryNo":279,"categoryName":280,"taxonomyType":276,"taxonomyTypeDesc":277},"01JBSEEDCAT000000000000032","设计师",[282,283,232,284,285,286,287,288,289,290,291,292,293,252,253,294,295,222,296,223],"coding patterns","slopgate intelligent coding patterns","coding","stateful","complexity","branch","which","chain","parsers","pipeline","selection","design","utility","workflows","reduce",{"skillNo":298,"name":299,"nameZh":6,"description":300,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":301,"categories":302,"keywords":305,"publishedAt":39},"01M7194KTXBM85GB0W7JKFQD55","slopgate-hygiene-orchestrator","Orchestrate systematic elimination of linter warnings and errors across Python, TypeScript, and Rust codebases. Use when asked to \"clean up lints\", \"fix all warnings\", \"run hygiene\", \"eliminate type errors\", \"orchestrate code quality fixes\", \"fix lint errors\", \"resolve quality gate failures\", \"pass CI checks\", \"reduce tech debt\", \"refactor to pass hooks\", or when a Slopgate hook denies with QUALITY-LINT-001, PY-CODE-017, PY-CODE-018, or any collector finding. This skill coordinates multiple code-hygiene-enforcer agents working in parallel on non-conflicting file groupings, tracks progress persistently via JSON exports, and loops until all issues are resolved. CRITICAL: Never run linters directly—always use `slopgate lint check` as the primary gate, discover project-specific tools from config files, and export findings to JSON for tracking.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-hygiene-orchestrator\u002FSKILL.md",[303,304],{"categoryNo":208,"categoryName":209,"taxonomyType":210,"taxonomyTypeDesc":211},{"categoryNo":271,"categoryName":272,"taxonomyType":210,"taxonomyTypeDesc":211},[306,307,259,308,219,309,310,311,312,313,253,296,314,315,316,317,318,319,320,321],"slopgate hygiene orchestrator","hygiene","project","ci","local","clean","never run","files","run","lint check","systematic","config","typescript","debt","quality-gates","hook",{"skillNo":323,"name":324,"nameZh":6,"description":325,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":326,"categories":327,"keywords":330,"publishedAt":39},"01M7194G50FZYXXT8VNK360RPA","slopgate-code-smell-utility-locator","Autoactivate when code-smell hooks or reviews mention feature envy, thin wrappers, duplicate helpers, duplicate code,\nscattered helpers, builders\u002Ffactories\u002Fconfig\u002Fconstants\u002Fdataclass reuse, PY-CODE-012, PY-CODE-013, QUALITY-LINT-001,\nor repeated slopgate code-quality denials. Also load when asked to \"find existing helpers\", \"consolidate utilities\",\n\"search for duplicate code\", \"where is this already implemented\", \"reuse existing logic\", \"don't duplicate this\",\n\"find similar functions\", \"utility inventory\", \"code smell radar\", or before adding new helpers\u002Fwrappers so agents can\nfind existing shared utilities and consolidate instead of duplicating.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-code-smell-utility-locator\u002FSKILL.md",[328,329],{"categoryNo":208,"categoryName":209,"taxonomyType":210,"taxonomyTypeDesc":211},{"categoryNo":274,"categoryName":275,"taxonomyType":276,"taxonomyTypeDesc":277},[294,331,223,332,246,333,334,335,336,252,337,222,338,256,258,339,340,317,341,342],"slopgate code smell utility locator","shared","reviews","inventory","search","hooks","new","coordination","radar","code-quality","Utilities","dataclass",{"skillNo":344,"name":345,"nameZh":6,"description":346,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":347,"categories":348,"keywords":351,"publishedAt":39},"01M7194AWG1Q37F9756H4SFDH9","slopgate-code-hygiene-refactor","Recovery playbook for Slopgate and project quality failures. Load after hook\u002Flint denials such as PY-CODE-017 flat sibling modules, PY-CODE-018 oversized modules, QUALITY-LINT-001 post-edit quality backstops, PY-QUALITY-010 magic numbers \u002F repeated literals, PY-CODE-012\u002FPY-CODE-013 smell findings, type-suppression bans, duplicate helpers, or repeated hygiene retry loops. Also load when asked to \"refactor this module\", \"split this file\", \"extract a class\", \"reduce complexity\", \"fix god class\", \"flatten module hierarchy\", \"move code to a package\", \"extract helpers\", \"consolidate duplicates\", \"replace magic numbers with constants\", or when a hook blocks an edit with structural complaints. Focuses on preserving public APIs while refactoring toward packages, cohesive modules, typed seams, and focused tests.","https:\u002F\u002Fgithub.com\u002Fvasceannie\u002Fslopgate\u002Fblob\u002Fmaster\u002Fbundle\u002Fshared\u002Fskills\u002Fslopgate-code-hygiene-refactor\u002FSKILL.md",[349,350],{"categoryNo":208,"categoryName":209,"taxonomyType":210,"taxonomyTypeDesc":211},{"categoryNo":274,"categoryName":275,"taxonomyType":276,"taxonomyTypeDesc":277},[352,353,223,354,307,355,286,356,357,308,358,334,359,219,252,294,222,296,338,256],"code hygiene","slopgate code hygiene refactor","refactor","modules","duplicates","retry","move","structural"]