スキル observability-and-instrumentation

📦

observability-and-instrumentation

Name: observability-and-instrumentation
Author: addyosmani

コンテンツリビジョン r2 安全 ⚙️ 外部コマンド📁 ファイルシステムへのアクセス🔑 環境変数

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.

対応: Claude Codex Code(CC)

🥉 78 ブロンズ

Maintain this Skill? Claim it 🥉 78 ブロンズ

自分のエージェントでインストール

このリクエストをエージェントにコピーしてください。正規の Skill ページとマニフェストが含まれています。

エージェントリクエスト

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.

エージェントは引き続き計画を提示し、セキュリティポリシーで必要な確認を求める必要があります。

エージェントが読めるリソース

AI エージェント、クローラー、スクリプトがページ全体ではなく整理されたコンテキストを必要とする場合は、これらのリンクを使ってください。

Markdown詳細 GET /skills/addyosmani-observability-and-instrumentation.md 署名済み manifest GET /api/skills/addyosmani-observability-and-instrumentation/manifest 署名済み lockfile GET /api/skills/addyosmani-observability-and-instrumentation/lockfile

テストする

「observability-and-instrumentation」を使用しています。 A payment retry feature needs telemetry for success rate, permanent failures, and provider latency.

期待される結果:

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.

「observability-and-instrumentation」を使用しています。 A team wants to page on CPU usage and label metrics with customer IDs.

期待される結果:

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

「observability-and-instrumentation」を使用しています。 A service has alerts but no runbooks or staging verification.

期待される結果:

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

セキュリティ監査

安全

v2 • 2026/9/19 バージョン別レポートを開く

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.

スキャンされたファイル

239

解析済み行数

レビュー項目

誤検知を無視

リスク要因

⚙️ 外部コマンド (34)

📁 ファイルシステムへのアクセス (1)

SKILL.md:238

🔑 環境変数 (2)

SKILL.md:101 SKILL.md:101

最新の完了済み静的・セマンティック監査では、確認済みのセキュリティ検出事項は見つかりませんでした。これは、スキルに副作用がないことを証明するものではありません。

監査者: codex 監査履歴を表示 →

このレポートを共有・引用

バージョン付き評価レポート、中立的なバッジ、埋め込みカード、引用を共有できます。Skillstore は証拠を報告しますが、この Skill が安全かどうかは判断しません。

バージョン別レポートを開く

レポートリンクをコピー

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

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)

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>

埋め込みカード

<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>

学術引用 (APA · BibTeX · CFF)

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

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"

Skillstore スコア

このスコアの理由証拠の信頼度: 中

アーキテクチャ

保守性

コンテンツ

コミュニティ

仕様準拠

作成できるもの

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.

これらのプロンプトを試す

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.

ベストプラクティス

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.

回避

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.

よくある質問

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.

開発者情報

作成者

addyosmani

ライセンス

MIT

Skillstore リビジョン

バージョンに関する注意

作者はバージョンを宣言していません。

リポジトリ

https://github.com/addyosmani/agent-skills/tree/c004a74784a08295d52749b04cda634125b9a581/skills/observability-and-instrumentation

参照

5d5054f8a23586f9b500fece1cb613a9dffc787b

メンテナンスの新しさ

2026/9/19

利用状況

1 ダウンロード · 0 閲覧

ファイル構成

📄 SKILL.md

addyosmani のその他のスキル

すべて表示

📦

interview-me

Clarify User Intent Before You Build

Underspecified requests cause teams to build the wrong outcome and discover misalignment late. This skill runs a focused, one-question interview that turns ambiguity into confirmed intent.

コミュニケーション表示

📦

code-review-and-quality

依五大品質面向審查程式碼

程式碼變更可能隱藏正確性、安全性、架構、可讀性與效能問題。此 skill 採用結構化的審查流程，並產出依優先順序排列且可採取行動的意見。

コーディング＆開発表示

📦

planning-and-task-breakdown

Plan Work Into Verifiable Tasks

Large or vague software work can hide dependencies, missing acceptance criteria, and verification gaps. This skill converts a specification into ordered task slices with checkpoints, scope guidance, and clear completion conditions.

生産性表示

📦

documentation-and-adrs

Document Decisions and Architecture Clearly

Teams lose context when important technical decisions remain in chat, code comments, or individual memory. This skill turns architectural reasoning, API guidance, project instructions, and release changes into structured documentation.

ドキュメント表示

📦

frontend-ui-engineering

Build Accessible, Production-Ready Frontends

Frontend work can become inconsistent, inaccessible, or difficult to maintain. This skill guides component architecture, responsive layouts, state handling, and polished user experiences.

デザイン＆クリエイティブ表示

📦

using-agent-skills

Discover and Apply Agent Skills

Teams often lose time choosing the right workflow for a software task. This skill maps task context to focused agent skills and a practical development sequence.

コーディング＆開発表示

すべて表示

📦