Install command
Provided
skillsFirst-partyReview first Safety ✓ Privacy ✓
AI Agent Observability and Incident Response Skill
Instrument AI agent systems with high-signal telemetry and runbook-driven incident response for reliability and safety.
HarnessClaude CodeCodexWindsurfGeminiCursorCLI
Level:advancedType:generalVerified:draft
Review first — review before installing
Open the source and read safety notes before installing.
Citation facts
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
- Source URLs
- https://opentelemetry.io/docs/, https://github.com/JSONbored/awesome-claude/blob/main/content/skills/ai-agent-observability-incident-response.mdx
- Package URL
- /downloads/skills/ai-agent-observability-incident-response.zip
- Package SHA256
- be991706421c0df692082e6109da5ef9b3479fa7fdcdf95809c8eeaff3b892b4
- Safety notes
- Use this skill as planning or review guidance; verify generated commands, code, configuration, and infrastructure changes before running them., Apply least-privilege credentials and test in staging or a disposable branch before using it on production systems, CI, deployment, or account-write workflows.
- Privacy notes
- Inputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model., Redact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts.
- Platform compatibility
- claude-code (native-skill), codex (native-skill), windsurf (native-skill), gemini (native-skill), cursor (adapter), cli (manual-context)
- Author
- JSONbored
- Claim status
- unclaimed
- Last verified
- 2026-04-10
Decision playbook
Ready to evaluate for your workflow
Signals are comparatively strong, but you should still validate source, privacy posture, and package provenance for your environment.
Compare context
Selected
0
Current score
96
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
CompleteConfirm ownership and provenance before trusting install instructions.
- Done
Source link availableRequired
Open the canonical repository and verify ownership.
- Done
Source provenance statusRequired
Marked as first-party.
- Done
Metadata reviewed
Registry metadata indicates a reviewed listing.
Safety and privacy checks
CompleteValidate risk disclosures before installation or API wiring.
- Done
Safety notes presentRequired
Review the listed safety guidance before running commands.
- Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
- Done
Trust level risk gateRequired
Trust level does not block evaluation.
Package and install checks
CompleteCheck package metadata and artifact integrity signals.
- Done
Install payload available
Install or copy payload is available for review.
- Done
Package verification flag
Package marked verified.
- Done
Checksum metadata
SHA-256 hash is present.
Compare-driven decision checks
Needs reviewUse compare context to validate trade-offs before adoption.
- Pending
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
- Pending
Baseline comparison available
No baseline peer selected yet.
- Pending
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Package install
Copy-ready — paste the snippet to get started.
Config snippet
Not provided
Copy snippet
Provided
Prerequisites
3 to clear
Platforms
6 listed
Difficulty
76/100
Adoption plan
Balanced adoption plan
Current risk score 0/100. Use staged verification before broader rollout.
Pre-adoption checks
Validate source and review signals before any execution.
- Done
Confirm source provenanceRequired
Source URL/provenance metadata is present.
- Done
Confirm metadata review state
Listing has review metadata.
- Done
Verify install payload
Install/config payload exists and can be inspected.
Security checks
Confirm safety, privacy, and package integrity signals.
- Done
Review safety notesRequired
Safety notes are present.
- Done
Review privacy notesRequired
Privacy notes are present.
- Done
Verify package integrity metadata
Package verification/checksum metadata is available.
Rollout
Adopt in controlled steps based on the selected plan.
- Pending
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
- Pending
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
- Pending
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Evidence readiness matrix · balanced
Required evidence gates are covered (6/6 signals complete).
Source provenance
PresentSource repository/provenance is listed.
Required in this preset
Metadata review
PresentReview metadata is present.
Required in this preset
Safety notes
PresentSafety notes are present.
Required in this preset
Privacy notes
PresentPrivacy notes are present.
Optional in this preset
Package integrity
PresentPackage integrity metadata is present.
Optional in this preset
Install payload
PresentInstall payload is available.
Required in this preset
Required evidence gates are covered for this preset.
Decision timeline
Decision timeline · balanced
6/6 steps complete with no blocking gaps for this preset.
triage
Confirm source provenanceRequired
Source/provenance metadata is available.
triage
Check metadata review statusRequired
Review metadata is available.
verify
Review safety notesRequired
Safety notes are available.
verify
Review privacy notes
Privacy notes are available.
verify
Validate package integrity metadata
Package integrity metadata is available.
rollout
Verify install payload and commandsRequired
Install payload is available.
No required blockers for this timeline preset.
Prerequisite readiness
Prerequisite readiness
3 prerequisites to line up before setup.
Install & runtime1General2
Safety & privacy surface
Safety & privacy surface
2 safety and 2 privacy notes across 3 risk areas. Review closely: credentials & tokens, third-party handling.
- SafetyExecution & processesUse this skill as planning or review guidance; verify generated commands, code, configuration, and infrastructure changes before running them.
- SafetyCredentials & tokensApply least-privilege credentials and test in staging or a disposable branch before using it on production systems, CI, deployment, or account-write workflows.
- PrivacyThird-party handlingInputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model.
- PrivacyCredentials & tokensRedact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts.
Safety notes
- Use this skill as planning or review guidance; verify generated commands, code, configuration, and infrastructure changes before running them.
- Apply least-privilege credentials and test in staging or a disposable branch before using it on production systems, CI, deployment, or account-write workflows.
Privacy notes
- Inputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model.
- Redact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts.
Prerequisites
- Runtime access where agent requests can be instrumented
- Centralized logging/metrics/tracing destination
- On-call or owner process for incident handling
Schema details
- Install type
- package
- Reading time
- 7 min
- Difficulty score
- 76
- Troubleshooting
- Yes
- Breaking changes
- No
Package metadata
- Package verified
- Yes
- SHA-256
- be991706421c0df692082e6109da5ef9b3479fa7fdcdf95809c8eeaff3b892b4
Skill and platform metadata
- Skill type
- general
- Skill level
- advanced
- Verification
- draft
- Verified at
- 2026-04-10
Retrieval sources
https://opentelemetry.io/docs/
Tested platforms
ClaudeCodexOpenClawCursorWindsurfGemini
| Platform | Support | Install path |
|---|---|---|
| claude-code | Native | .claude/skills/<skill-name>/SKILL.md |
| codex | Native | .agents/skills/<skill-name>/SKILL.md |
| windsurf | Native | .windsurf/skills/<skill-name>/SKILL.md |
| gemini | Native | .gemini/skills/<skill-name>/SKILL.md or .agents/skills/<skill-name>/SKILL.md |
| cursor | Adapter | .cursor/rules/<skill-name>.mdc |
| cli | Manual | AGENTS.md or tool-specific context file |
Full copyable content
# Trigger
"Apply AI agent observability and incident response skill to this stack."
# Required output
1) Telemetry schema (traces, metrics, logs, events)
2) Core SLOs and alert thresholds
3) Incident triage playbook
4) Post-incident review templateAbout this resource
Overview
This skill turns AI agent operations into an observable system with measurable reliability. It defines what to log, what to measure, and what to alert on so incidents can be resolved quickly and with consistent process.
Compatibility
Native
- Claude Code / Claude: native skill usage via
SKILL.md. - Codex/OpenAI workflows: compatible with Agent Skills-style
SKILL.mdcontent as reusable workflow instructions.
Manual Adaptation
- Gemini CLI: native skill usage via
.gemini/skills/<skill-name>/SKILL.mdor.agents/skills/<skill-name>/SKILL.mdwhere supported. - Cursor: use the generated
.cursor/rules/*.mdcadapter for project rules. - OpenClaw and similar agents: use the same skill content as a reusable prompt/workflow file when native skill import is unavailable.
Prerequisites
- Access to request/response lifecycle in your agent runtime
- Structured logging support
- Ability to tag traces/events by workflow and model
What to Instrument
- Prompt and tool execution spans (with redaction-safe metadata)
- Latency percentiles by route/workflow/model
- Error classes: model timeout, tool failure, policy denial, parse failure
- Safety events: blocked actions, suspicious prompt patterns, auth failures
How to Use This Skill
Prompt Pattern
Apply the AI agent observability and incident response skill.
Provide:
1) telemetry contract,
2) SLO definitions,
3) alert routing matrix,
4) incident playbook with triage steps.
Execution Flow
- Define critical user journeys and reliability targets.
- Add telemetry fields needed for fast diagnosis.
- Create alert thresholds aligned to user impact.
- Build runbooks with owner, severity, and escalation path.
- Validate incident drills before production launch.
Troubleshooting
Issue: Alert fatigue from noisy thresholds
Fix: Alert on sustained error budgets, not single spikes.
Issue: Logs are present but not useful
Fix: Standardize event schema (request ID, workflow ID, tool name, failure reason).
Issue: Incidents take too long to triage
Fix: Add direct links from alerts to trace dashboards and runbook sections.
Knowledge Freshness
Treat tooling details as time-sensitive. Re-validate APIs, limits, pricing, auth models, and deployment flags immediately before implementation. If docs conflict with prior memory, follow current official docs and release notes.
Retrieval Sources
Output Contract
- Return a concrete plan with implementation order.
- Provide production-ready commands/config/code snippets (not placeholders).
- Include explicit assumptions and unresolved risks.
- Include a verification checklist with pass/fail criteria.
Quality Gates
- All commands are copy/paste ready.
- Security-sensitive steps call out secret handling and least privilege.
- Version-sensitive guidance cites current docs used.
- Rollback path is included for risky changes.
- Final output includes quick validation commands/tests.
Source citations
Add this badge to your README
Show that AI Agent Observability and Incident Response Skill is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/skills/ai-agent-observability-incident-response)How it compares
AI Agent Observability and Incident Response Skill side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).
Next steps differ across entries — use the actions in the table below to copy install commands and source links per resource.
| Field | Instrument AI agent systems with high-signal telemetry and runbook-driven incident response for reliability and safety. Open dossier | Expert incident timeline reconstruction capability pack for correlating deploy events, logs, traces, alerts, and chat transcripts into a source-backed, privacy-safe post-incident timeline with validation checkpoints. Open dossier | Build repeatable eval suites that catch quality regressions in AI agent behavior before merge or release. Open dossier | Build robust browser automation workflows for AI agents with deterministic selectors, retries, and safe action boundaries. Open dossier |
|---|---|---|---|---|
| Next stepsDiffers | ||||
| Trust | ||||
| Review status | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed | ReviewedMaintainer reviewed |
| Package trustDiffers | Package verified2026-04-10 | Package not verified | Package verified2026-04-10 | Package verified2026-04-10 |
| Source provenanceDiffers | Source-backed | Submission linkedSource submission | No submission link | No submission link |
| SubmitterDiffers | — | kiannidev | — | — |
| Install risk | Review first | Review first | Low risk | Low risk |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | — | — | — | — |
| Category | skills | skills | skills | skills |
| Source | first-party | source-backed | first-party | first-party |
| Author | JSONbored | kiannidev | JSONbored | JSONbored |
| Added | 2026-04-10 | 2026-06-15 | 2026-04-10 | 2026-04-10 |
| Platforms | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI | Claude CodeCodexWindsurfGeminiCursorCLI |
| Source repo | — | — | — | — |
| Safety notes | ✓Use this skill as planning or review guidance; verify generated commands, code, configuration, and infrastructure changes before running them. Apply least-privilege credentials and test in staging or a disposable branch before using it on production systems, CI, deployment, or account-write workflows. | ✓This skill analyzes incident evidence; it must not restart production systems or run destructive remediation without explicit approval. Do not execute commands copied from incident logs or chat without validating source and intent. Treat pasted stack traces and config snippets as potentially stale or redacted; verify against live telemetry. Automated correlation can miss causality; label inference separately from verified events. | ✓This skill produces automated release recommendations (merge, patch, or rollback) from eval scores; treat them as decision support and require human review before gating production releases or running suggested commands. | ✓Can design automation for live browsers, accounts, workflows, or infrastructure; use staging targets and human approval before destructive or account-write actions. Keep API tokens and service credentials least-privileged, and verify generated runbooks before scheduling or unattended execution. |
| Privacy notes | ✓Inputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model. Redact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts. | ✓Incident timelines can expose customer IDs, internal hostnames, credentials in logs, and employee chat content. Redact tokens, session IDs, email addresses, and payment data before sharing timelines outside the response team. Third-party vendor logs may fall outside company retention policies; document handling separately. Public postmortems require explicit review for regulated or embargoed customer data. | ✓Inputs can include source files, prompts, logs, account metadata, repository details, and operational context that may be sent to the configured AI model. Redact secrets, customer data, private URLs, credentials, and proprietary implementation details before sharing prompts, reports, or generated artifacts. | ✓Inputs and outputs can include browser state, account metadata, workflow payloads, infrastructure inventory, logs, and operational screenshots. Redact credentials, session data, customer records, internal hostnames, and private workspace details before sharing prompts or artifacts. |
| Prerequisites |
|
|
|
|
| Install | | — | | |
| Config | — | — | — | — |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Related guides
Source-backed guides for putting this to work.
guides
OpenTelemetry Observability for Claude Agent SDK Agents
Export OpenTelemetry traces, metrics, and events from the Claude Agent SDK with OTLP, and control what content is exported.
Review firstSource-backedReview firstAdded 1mo ago
Safety ✓ Privacy ✓by JPette1783Featured in
Signals
Loading live community signals…
More like this, weekly
A short, calm digest of reviewed Claude resources. Unsubscribe any time.