What problem does it solve? Setting up observability for AI applications is error-prone: developers must detect which AI SDKs are installed, enable tracing, configure sampling so agent spans are not dropped, and handle PII concerns around prompt capture. This Skill guides the full setup of Sentry AI Agent Monitoring so LLM calls, agent executions, tool usage, and token costs become visible in Sentry. ## Core Features & Use Cases - SDK Detection and Auto-Configuration: Detects installed AI SDKs (OpenAI, Anthropic, Vercel AI, LangChain, Google GenAI, Pydantic AI) in JavaScript or Python projects and applies the correct Sentry integrations. - Sampling and Cost Guidance: Configures tracesSampler so gen_ai spans are kept at 100% while other traffic uses a lower rate, and explains correct cached/reasoning token accounting to avoid negative costs. - Conversations View Setup: Sets conversation IDs and user attribution so multi-turn chats are grouped into a readable timeline in Sentry. - Use Case: A team shipping a Next.js chatbot using the Vercel AI SDK asks to track model latency and token spend; the Skill detects the SDK, adds vercelAIIntegration with per-call telemetry, and verifies spans appear in the Sentry Traces dashboard. ## Quick Start Ask the assistant to set up Sentry AI monitoring for the LLM calls in this project and verify the spans appear in the Sentry dashboard.