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.
Copiez cette demande dans votre Agent. Elle contient la page Skill de référence et le manifeste.
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.Votre Agent doit toujours présenter son plan et demander toute confirmation exigée par la politique de sécurité.
Utilisez ces liens lorsquâun Agent IA, un crawler ou un script a besoin dâun contexte propre au lieu de lire toute la page.
Utilisation de « observability-and-instrumentation ». A payment retry feature needs telemetry for success rate, permanent failures, and provider latency.
RĂ©sultat attendu:
Utilisation de « observability-and-instrumentation ». A team wants to page on CPU usage and label metrics with customer IDs.
RĂ©sultat attendu:
Use user-facing error rate or latency for paging, and move customer identifiers to logs or traces. Keep metric labels bounded.
Utilisation de « observability-and-instrumentation ». A service has alerts but no runbooks or staging verification.
RĂ©sultat attendu:
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.
Partagez le rapport dâĂ©valuation versionnĂ©, le badge neutre, la carte intĂ©grable et les citations. Skillstore prĂ©sente les preuves sans dĂ©cider si ce Skill est sĂ»r.
https://skillstore.io/skills/addyosmani-observability-and-instrumentation/audits/2?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report[](https://skillstore.io/skills/addyosmani-observability-and-instrumentation?utm_source=security_passport_badge)<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>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@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}
}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"
Define the endpoint questions, add structured logs, and select RED metrics with bounded labels.
Add correlation IDs, distributed tracing, and actionable alerts so on-call engineers can follow a failing request.
Use the verification checklist to assess telemetry coverage, secret handling, alert quality, and staging validation.
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 log events for this endpoint. Include stable event names, safe fields, log levels, correlation IDs, and entry-point attribution.
Create an observability plan for this service and its dependencies. Cover RED metrics, bounded labels, OpenTelemetry traces, sampling, and symptom-based alerts.
Review this instrumentation diff against the observability checklist. Identify missing signals, cardinality risks, sensitive data exposure, alert weaknesses, and staging tests.
Auteur
addyosmaniLicence
MIT
RĂ©vision Skillstore
r2
Avis de version
Lâauteur nâa dĂ©clarĂ© aucune version.
RĂ©f
5d5054f8a23586f9b500fece1cb613a9dffc787b
RĂ©cence de maintenance
19/09/2026
Utilisation
1 téléchargements · 0 vues
Structure de fichiers
đ SKILL.md
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.
Examiner le code selon cinq axes de qualité
Les modifications de code peuvent dissimuler des problĂšmes de fiabilitĂ©, de sĂ©curitĂ©, dâarchitecture, de lisibilitĂ© et de performances. Cette compĂ©tence applique un processus dâexamen structurĂ© et produit des retours hiĂ©rarchisĂ©s et exploitables.
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.
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.
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.
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.
Ajouter des patterns dâobservabilitĂ© Python
par 0xDarkMatter
Les services Python manquent souvent de patterns cohérents pour la journalisation, les métriques et le traçage. Cette compétence fournit des exemples pratiques avec structlog, Prometheus et OpenTelemetry pour les applications de production.
Suivre la latence MEV avec des recommandations de spans
par BarisSozen
Les problĂšmes de latence dans les systĂšmes MEV sont difficiles Ă isoler entre les appels et les Ă©tapes de transaction. Cette skill guide la hiĂ©rarchie des spans, lâinstrumentation, lâagrĂ©gation et les seuils dâalerte.
Instrumenter les applications Azure avec Application Insights
par microsoft
Ajouter une tĂ©lĂ©mĂ©trie fiable aux applications hĂ©bergĂ©es sur Azure peut ĂȘtre difficile selon les frameworks et les modĂšles de dĂ©ploiement. Cette compĂ©tence fournit des conseils concis de configuration dâApplication Insights, des rĂ©fĂ©rences SDK et des modĂšles de configuration Azure.
Déployer des charges de travail Kubernetes avec des étapes guidées
par sickn33
Les releases Kubernetes nĂ©cessitent de nombreux artefacts et contrĂŽles coordonnĂ©s. Cette compĂ©tence guide la prĂ©paration des conteneurs, les manifestes, les charts Helm, le service mesh, la sĂ©curitĂ©, lâobservabilitĂ© et la validation du dĂ©ploiement.
RĂ©soudre plus rapidement les incidents DevOps
par sickn33
Les incidents de production nĂ©cessitent un triage rapide entre les journaux, les mĂ©triques, les traces et les plateformes cloud. Cette compĂ©tence guide le dĂ©bogage DevOps structurĂ©, lâanalyse des causes racines et la planification de la reprise.
Optimiser les performances des applications
par sickn33
Les systĂšmes lents nuisent aux utilisateurs, Ă la fiabilitĂ© et aux coĂ»ts cloud. Cette compĂ©tence aide Ă diagnostiquer les goulots dâĂ©tranglement, Ă concevoir des tests et Ă planifier des optimisations mesurĂ©es.