Habilidades observability-and-instrumentation
📦

observability-and-instrumentation

Revisão do conteúdo r2 Seguro ⚙️ Comandos externos📁 Acesso ao sistema de arquivos🔑 Variáveis de ambiente

Instrument Production Systems with Clear Telemetry

Production teams need reliable evidence when services fail, slow down, or behave unexpectedly. This skill helps design useful logs, metrics, traces, alerts, and verification steps.

Suporta: Claude Codex Code(CC)
🥉 78 Bronze

Instalar com meu Agente

Copie esta solicitação para o seu Agente. Ela inclui a página canônica do Skill e o manifesto.

Solicitação do agente
Review the Skillstore skill "observability-and-instrumentation" from https://skillstore.io/skills/addyosmani-observability-and-instrumentation.md and its manifest at https://skillstore.io/api/skills/addyosmani-observability-and-instrumentation/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.

Seu Agente ainda deve apresentar o plano e solicitar qualquer confirmação exigida pela política de segurança.

Testar

Usando "observability-and-instrumentation". A payment retry feature needs telemetry for success rate, permanent failures, and provider latency.

Resultado esperado:

  • Use structured events for payment outcomes and provider error codes.
  • Add a latency histogram with percentiles for provider calls.
  • Trace a sampled checkout request and retain error traces.

Usando "observability-and-instrumentation". A team wants to page on CPU usage and label metrics with customer IDs.

Resultado esperado:

Use user-facing error rate or latency for paging, and move customer identifiers to logs or traces. Keep metric labels bounded.

Usando "observability-and-instrumentation". A service has alerts but no runbooks or staging verification.

Resultado esperado:

  • Link every alert to a short runbook with meaning, first check, and escalation path.
  • Test induced failures and confirm telemetry reaches the correct channel.

Auditoria de segurança

Seguro

All 41 static findings are false positives caused by Markdown backticks, documentation syntax, benign example code, or a relative reference. The reviewed skill contains no executable commands, credential exfiltration, unsafe file access, or prompt injection.

1
Arquivos analisados
239
Linhas analisadas
0
Itens de revisão
0
Falsos positivos ignorados
A auditoria estática e semântica concluída mais recente não detectou achados de segurança confirmados. Isso não comprova que a skill não tenha efeitos colaterais.
Compartilhar e citar este relatório

Compartilhe o relatório de avaliação versionado, o badge neutro, o cartão incorporável e as citações. A Skillstore apresenta evidências sem decidir se este Skill é seguro.

Abrir o relatório versionado
Avaliação de Segurança

Copiar link do relatório

https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Badge Markdown

[![Skillstore security assessment](https://skillstore.io/badges/skills/addyosmani-observability-and-instrumentation/security.svg)](https://skillstore.io/skills/addyosmani-observability-and-instrumentation?utm_source=security_passport_badge)

Badge HTML

<a href="https://skillstore.io/skills/addyosmani-observability-and-instrumentation?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/addyosmani-observability-and-instrumentation/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Cartão incorporável

<iframe src="https://skillstore.io/embed/skills/addyosmani-observability-and-instrumentation.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Citações acadêmicas (APA · BibTeX · CFF)

Citação APA

addyosmani. (2026). observability-and-instrumentation security audit report (audit version 2) [Author version unspecified]. Skillstore. https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/2

Citação BibTeX

@techreport{addyosmani-addyosmani-observability-and-instrumentation-2026, author = {addyosmani}, title = {observability-and-instrumentation security audit report (audit version 2)}, institution = {Skillstore}, year = {2026}, number = {2}, url = {https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/2}, note = {Author version unspecified} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "observability-and-instrumentation security audit report (audit version 2)" version: "unspecified" type: report authors: - name: "addyosmani" date-released: "2026-09-19" url: "https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/2" identifiers: - type: other value: "skillstore:addyosmani-observability-and-instrumentation:audit:2" description: "Skillstore immutable audit report identifier"

Pontuação do Skillstore

Por que esta pontuação Confiança das evidências: Médio
55
Arquitetura
85
Manutenibilidade
87
Conteúdo
65
Comunidade
91
Conformidade com a especificação

O que você pode criar

Instrument a New Endpoint

Define the endpoint questions, add structured logs, and select RED metrics with bounded labels.

Improve Incident Diagnosis

Add correlation IDs, distributed tracing, and actionable alerts so on-call engineers can follow a failing request.

Review Production Readiness

Use the verification checklist to assess telemetry coverage, secret handling, alert quality, and staging validation.

Teste estes prompts

Start with Observability Questions
Review this feature description and list two to four questions an on-call engineer must answer. Map each question to a log, metric, or trace.
Design Structured Logging
Design structured log events for this endpoint. Include stable event names, safe fields, log levels, correlation IDs, and entry-point attribution.
Plan Service Telemetry
Create an observability plan for this service and its dependencies. Cover RED metrics, bounded labels, OpenTelemetry traces, sampling, and symptom-based alerts.
Audit an Instrumentation Change
Review this instrumentation diff against the observability checklist. Identify missing signals, cardinality risks, sensitive data exposure, alert weaknesses, and staging tests.

Boas práticas

  • Start from concrete on-call questions and map every signal to one question.
  • Allowlist telemetry fields and exclude secrets, tokens, passwords, and full PII.
  • Verify telemetry and alert delivery in staging before calling the work complete.

Evitar

  • Adding unstructured logs without a stable event name or correlation ID.
  • Using user IDs, raw URLs, or error text as metric labels.
  • Paging on infrastructure causes without a user-facing symptom or runbook.

Perguntas frequentes

What does this skill help me instrument?
It guides logging, metrics, distributed tracing, alerting, runbooks, and telemetry verification for production features.
Does it recommend a specific monitoring vendor?
No. It favors vendor-neutral OpenTelemetry concepts and explains how to adapt them to common backends.
Why are structured logs important?
Structured fields make events searchable, consistent, and easier to correlate during incidents.
How should I choose metric labels?
Use small fixed sets such as route templates, status classes, and provider names. Keep unbounded values in logs or traces.
Should every alert page an engineer?
No. Page only for actionable user-facing symptoms. Use tickets for degradations that can wait.
How do I validate new telemetry?
Induce a staging failure, inspect structured logs, send test traffic, follow a trace, and test each alert and runbook link.

Detalhes do desenvolvedor

Licença

MIT

Revisão da Skillstore

r2

Aviso de versão

O autor não declarou uma versão.

Referência

5d5054f8a23586f9b500fece1cb613a9dffc787b

Atualidade da manutenção

19/09/2026

Uso

1 downloads · 0 visualizações

Estrutura de arquivos

📄 SKILL.md

Mais de addyosmani

Ver tudo
Ver tudo