- name
SKILL.md
O arquivo da skill permanece no repositório do publicador.
Cole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add first-fluke/oh-my-agent --skill oma-observability -a cursor -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add first-fluke/oh-my-agent --skill oma-observability -a claude-code -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add first-fluke/oh-my-agent --skill oma-observability -a codex -yCole o comando copiado em um terminal. Ele instala este SKILL.md nesse agente.
npx skills add first-fluke/oh-my-agent --skill oma-observability -a grok -yEnvie a mensagem copiada em um chat do Grok Bot. O Bot busca este SKILL.md no GitHub e o adiciona às skills que todos os seus Bots compartilham.
Install this skill: https://github.com/first-fluke/oh-my-agent/tree/HEAD/.agents/skills/oma-observabilityDo publicador
Route, design, tune, and review observability work across MELT+P signals, layers, boundaries, vendor categories, transport choices, meta-observability, and incident forensics.
oma-security (this skill covers security telemetry only: audit trails, WAF signals, PII redaction)Load resources conditionally: start with the execution protocol and the one guide the intent route selects. Read only relevant matrix rows, then add a layer, boundary, signal, or transport guide when its trigger in §References is present. No reference is a mandatory preload.
resources/resources/matrix.md, note coverage gaps, and identify the vendor category when the route needs one.https://landscape.cncf.io.Reads observability config, dashboards, alert rules, instrumentation, and the incident symptoms, logs, metrics, traces, and profiles the user supplies. Output is guidance by default; a requested change may modify observability config, dashboards, alert rules, and instrumentation docs. Network access covers vendor or CNCF status checks and telemetry backends when a check needs them. Vendor-specific implementation is routed to vendor-owned skills or external tools.
resources/vendor-categories.md only when category selection or vendor delegation is needed.resources/boundaries/cross-application.md where required.The 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/matrix.md; N/A cells do not require implementation.
Record the selected intent route, and any vendor category chosen for setup, with subject observability.route-selection per ../_shared/runtime/route-selection.md.
For example: /oma-observability --investigate "5xx spike in checkout".
Other skills pass the intent, system boundary, and evidence; the result returns guidance, checks, and any vendor handoff.
Read resources/execution-protocol.md first. Use the selected route above, add guides by the triggers in §References, then check only the applicable checklist sections before delivery. Do not load all transport, layer, boundary, and signal guides together.
resources/standards.md holds the single statement on spec and semconv currency. Where content depends on an attribute's stability tier, the tier is stated inline; confirm it in the semconv registry when it is load-bearing.resources/standards.md and the affected file.vendor-categories.md (Graduated / Archived / acquired) → update the vendor table.https://landscape.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.Before delivering observability changes, check the items of resources/checklist.md that apply, starting with §1 Setup validation; report checks that were not run.
Each reference loads on its trigger. Paths are relative to the skill root.
Design or troubleshoot telemetry, SLOs, and incident diagnostics. Route to the relevant signal, system boundary, or vendor guide.
---name: oma-observabilitydescription: Design or troubleshoot telemetry, SLOs, and incident diagnostics. Route to the relevant signal, system…---# .agents/skills/oma-observability/SKILL.mdPerguntas frequentes
Baixe .agents/skills/oma-observability/SKILL.md do publicador ou copie o caminho e abra o repositório. O PlugMCP lista a skill e não hospeda o arquivo.
O publicador o mantém em https://github.com/first-fluke/oh-my-agent.
Claude, Cursor, Codex e Grok Build conseguem ler um SKILL.md que você adiciona a partir do repositório do publicador. O Grok Bot o instala quando você envia em um chat o link da pasta da skill no GitHub.
oma-mobile |
resources/layers/L7-application/mobile-rum.md offline-queuing pattern. Back-reference: oma-mobile/SKILL.md §References "Observability handoff" |
oma-db | resources/signals/traces.md §2 DB patterns (N+1, connection pool). Back-reference: oma-db/SKILL.md §References "Observability handoff" |
resources/layers/L4-transport.md |
| Istio, Linkerd, or Envoy telemetry; zero-code instrumentation; trace breaks at a proxy | resources/layers/mesh.md |
| Browser RUM, Core Web Vitals, source maps, session replay | resources/layers/L7-application/web-rum.md |
| Mobile RUM, offline telemetry queue, app start, ANR | resources/layers/L7-application/mobile-rum.md |
| Crash-free rate, symbolication, crash grouping, crash-to-release correlation | resources/layers/L7-application/crash-analytics.md |
| Edge 403 storm, WAF false positives, ruleset rollout, WAF fail-open or fail-closed | resources/layers/L7-application/waf.md |
| Tenant isolation, per-tenant routing or sampling, data residency | resources/boundaries/multi-tenant.md |
Propagators, baggage, cross-cloud or cross-vendor trace continuity, request_id, third-party dependency outage | resources/boundaries/cross-application.md |
| SLI or SLO definition, error budget, burn-rate alerts | resources/boundaries/slo.md |
| Release markers, canary analysis, feature-flag telemetry, GitOps drift | resources/boundaries/release.md |
| Metric naming, histogram buckets, exemplars, label design | resources/signals/metrics.md |
| Log agent or pipeline choice, structured logging, trace-ID injection into logs | resources/signals/logs.md |
| Span design; DB (N+1, connection pool) and messaging span patterns | resources/signals/traces.md |
| Continuous profiling, flame graphs, heap or CPU diff across releases | resources/signals/profiles.md |
| Cost attribution, OpenCost, FinOps unit economics | resources/signals/cost.md |
| Audit trail, compliance evidence, retention schedule, tamper evidence | resources/signals/audit.md |
| PII redaction, pseudonymization, cross-border transfer, backend access control | resources/signals/privacy.md |