agentcore-observability-setup
From the author
Validates and bootstraps Amazon Bedrock AgentCore observability so customers can trace agent reasoning, detect silent failures, and measure performance before an outage. Use this skill when a user asks to check, validate, audit, verify, fix, or set up AgentCore observability, tracing, metrics, or logging - for example "is AgentCore observability configured correctly", "why can't I see traces for my agent", "my Bedrock agent has no spans in CloudWatch", "validate agent monitoring", "AgentCore observability readiness", or "set up OTEL for my agent". Covers AgentCore Runtime agents, Memory and Gateway resources, built-in tools, and agents hosted outside the runtime (Lambda, ECS, EKS, on-prem, multi-cloud). Verifies what is reachable via read-only CloudWatch, X-Ray, and AgentCore control-plane APIs, and prescribes exact remediation for gaps it cannot directly read such as code-level OTEL instrumentation.
Install
npx skills add aws/tools-for-devops-agent --skill agentcore-observability-setup -a claude-code
Installs to .claude/skills/agentcore-observability-setup/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- agentcore-ops-reviewaws/tools-for-devops-agentComprehensive operational review procedures for Amazon Bedrock AgentCore resources aligned with the AWS Well-Architected Framework. Covers four check areas — Runtime Resilience, Gateway Health, Memory & Knowledge Effectiveness, and Resource Utilization & Operational Hygiene — plus runtime observability signals from CloudWatch. Use this skill when a user asks to review, audit, or assess Amazon Bedrock AgentCore workloads, perform an AgentCore operational readiness review, investigate agent runtime failures, audit memory/knowledge pipeline health, or review gateway resilience and resource hygiene. Triggers on requests like "AgentCore review", "AgentCore best practices audit", "review my AgentCore runtimes", "AgentCore health check", "audit my agent memory pipelines", or "ORR for AgentCore".Engineering★ 116
- aws-agentic-aizxkane/aws-skillsAWS Bedrock AgentCore comprehensive expert for deploying and managing AI agents at scale. Use when working with any AgentCore service including Gateway, Runtime, Memory, Identity, Code Interpreter, Browser, Observability, Agent Registry, or Evaluations. Covers agent deployment, MCP tool integration, credential management, agent discovery, governance workflows, and automated quality assessment. Essential when user mentions AgentCore, agent runtime, agent registry, agent evaluation, MCP gateway, deploy agent, register MCP server, discover agents, evaluate agent quality, agent credentials, or wants to build, deploy, catalog, or monitor AI agents on AWS.DevOps★ 371
- agentcorevercel-labs/agent-browserRun agent-browser on AWS Bedrock AgentCore cloud browsers. Use when the user wants to use AgentCore, run browser automation on AWS, use a cloud browser with AWS credentials, or needs a managed browser session backed by AWS infrastructure. Triggers include "use agentcore", "run on AWS", "cloud browser with AWS", "bedrock browser", "agentcore session", or any task requiring AWS-hosted browser automation.OfficialDevOps★ 44.6K
- agent-observabilityBagelHole/DevOps-Security-Agent-SkillsInstrument AI agents with tracing, token metrics, latency, and cost visibility. Use for reliability and debugging.DevOps★ 1.2K
- llm-observabilitynahid-sparktales/agent-dispatcherSee what an agent actually did — one trace per run with nested model, tool and retrieval spans, token and latency accounted per step, and failures clustered by mechanism instead of read one at a time. Use when an agent misbehaves in ways you cannot reproduce, when cost or latency is unexplained, when "it sometimes fails" is the whole bug report, or before writing evals when you do not yet know which failures exist. Not for judging whether an output is correct (agent-evals), and not a replacement for the application's own monitoring.DevOps★ 59
- mcp-data-observability-integrationvaquarkhan/data-engineering-agent-skillsGuides agents to wire Model Context Protocol servers for live data platform observability including Spark execution plans, OOM diagnosis, Kafka consumer lag, and orchestration run state. Use when agents need cluster metrics, streaming lag, or job diagnostics instead of blind code changes.DevOps★ 59
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in