Ai Sdk
ai-sdk — an installable skill for AI agents, published by getsentry/webvitals.com.
Install
Quick install
npx skills add https://github.com/getsentry/webvitals.com/tree/HEAD/.agents/skills/ai-sdknpx skills add getsentry/webvitals.com --skill ai-sdk --agent claude-codenpx skills add getsentry/webvitals.com --skill ai-sdk --agent cursornpx skills add getsentry/webvitals.com --skill ai-sdk --agent codexnpx skills add getsentry/webvitals.com --skill ai-sdk --agent opencodenpx skills add getsentry/webvitals.com --skill ai-sdk --agent github-copilotnpx skills add getsentry/webvitals.com --skill ai-sdk --agent windsurfMore install options
Shorthand — useful for multi-skill repos:
npx skills add getsentry/webvitals.com --skill ai-sdkManual — clone the repo and drop the folder into your agent's skills directory:
git clone https://github.com/getsentry/webvitals.com.gitcp -r webvitals.com/.agents/skills/ai-sdk ~/.claude/skills/ai-sdk
ai-sdk — an installable skill for AI agents, published by getsentry/webvitals.com.
ai-sdkby sentry
ai-sdk — an installable skill for AI agents, published by getsentry/webvitals.com.npx skills add https://github.com/getsentry/webvitals.com --skill ai-sdkDownload ZIPGitHub
Prerequisites
Before searching docs, check if node_modules/ai/docs/ exists. If not, install only the ai package using the project's package manager (e.g., pnpm add ai).
Do not install other packages at this stage. Provider packages (e.g., @ai-sdk/openai) and client packages (e.g., @ai-sdk/react) should be installed later when needed based on user requirements.
Critical: Do Not Trust Internal Knowledge
Everything you know about the AI SDK is outdated or wrong. Your training data contains obsolete APIs, deprecated patterns, and incorrect usage.
When working with the AI SDK:
- Ensure
aipackage is installed (see Prerequisites)
- Search
node_modules/ai/docs/andnode_modules/ai/src/for current APIs
- If not found locally, search ai-sdk.dev documentation (instructions below)
- Never rely on memory - always verify against source code or docs
useChathas changed significantly - check Common Errors before writing client code
- When deciding which model and provider to use (e.g. OpenAI, Anthropic, Gemini), use the Vercel AI Gateway provider unless the user specifies otherwise. See AI Gateway Reference for usage details.
- Always fetch current model IDs - Never use model IDs from memory. Before writing code that uses a model, run
curl -s https://ai-gateway.vercel.sh/v1/models | jq -r '[.data[] | select(.id | startswith("provider/")) | .id] | reverse | .[]'(replacingproviderwith the relevant provider likeanthropic,openai, orgoogle) to get the full list with newest models first. Use the model with the highest version number (e.g.,claude-sonnet-4-5overclaude-sonnet-4overclaude-3-5-sonnet).
- Run typecheck after changes to ensure code is correct
- Be minimal - Only specify options that differ from defaults. When unsure of defaults, check docs or source rather than guessing or over-specifying.
If you cannot find documentation to support your answer, state that explicitly.
Finding Documentation
[email protected]+
Search bundled docs and source in node_modules/ai/:
- Docs:
grep "query" node_modules/ai/docs/
- Source:
grep "query" node_modules/ai/src/
Provider packages include docs at node_modules/@ai-sdk/<provider>/docs/.
Earlier versions
- Search:
https://ai-sdk.dev/api/search-docs?q=your_query
- Fetch
.mdURLs from results (e.g.,https://ai-sdk.dev/docs/agents/building-agents.md)
When Typecheck Fails
Before searching source code, grep Common Errors for the failing property or function name. Many type errors are caused by deprecated APIs documented there.
If not found in common-errors.md:
- Search
node_modules/ai/src/andnode_modules/ai/docs/
- Search ai-sdk.dev (for earlier versions or if not found locally)
Building and Consuming Agents
Creating Agents
Always use the ToolLoopAgent pattern. Search node_modules/ai/docs/ for current agent creation APIs.
File conventions: See type-safe-agents.md for where to save agents and tools.
Type Safety: When consuming agents with useChat, always use InferAgentUIMessage<typeof agent> for type-safe tool results. See reference.
Consuming Agents (Framework-Specific)
Before implementing agent consumption:
- Check
package.jsonto detect the project's framework/stack
- Search documentation for the framework's quickstart guide
- Follow the framework-specific patterns for streaming, API routes, and client integration
References
- Common Errors - Renamed parameters reference (parameters → inputSchema, etc.)
- AI Gateway - Gateway setup and usage
- Type-Safe Agents with useChat - End-to-end type safety with InferAgentUIMessage
More skills from sentry
sentry-cocoa-sdkby sentryFull Sentry SDK setup for Apple platforms (iOS, macOS, tvOS, watchOS, visionOS). Use when asked to "add Sentry to iOS", "add Sentry to Swift", "install…sentry-create-alertby sentryCreate Sentry alerts using the workflow engine API. Use when asked to create alerts, set up notifications, configure issue priority alerts, or build workflow…sentry-dotnet-sdkby sentryFull Sentry SDK setup for .NET. Use when asked to "add Sentry to .NET", "install Sentry for C#", or configure error monitoring, tracing, profiling, logging, or…sentry-fix-issuesby sentryFind and fix issues from Sentry using MCP. Use when asked to fix Sentry errors, debug production issues, investigate exceptions, or resolve bugs reported in…sentry-go-sdkby sentryFull Sentry SDK setup for Go. Use when asked to "add Sentry to Go", "install sentry-go", "setup Sentry in Go", or configure error monitoring, tracing, logging,…sentry-ios-swift-setupby sentrySetup Sentry in iOS/Swift apps. Use when asked to add Sentry to iOS, install sentry-cocoa SDK, or configure error monitoring for iOS applications using Swift…sentry-nextjs-sdkby sentryFull Sentry SDK setup for Next.js. Use when asked to "add Sentry to Next.js", "install @sentry/nextjs", or configure error monitoring, tracing, session replay,…sentry-otel-exporter-setupby sentryConfigure the OpenTelemetry Collector with Sentry Exporter for multi-project routing and automatic project creation. Use when setting up OTel with Sentry,…---
Source: https://github.com/getsentry/webvitals.com/tree/HEAD/.agents/skills/ai-sdk
Author: sentry
Discovered via: mcpservers.org
SKILL.md source
---
name: ai-sdk
description: ai-sdk — an installable skill for AI agents, published by getsentry/webvitals.com.
---
# ai-sdk
ai-sdk — an installable skill for AI agents, published by getsentry/webvitals.com.
# ai-sdkby sentry
ai-sdk — an installable skill for AI agents, published by getsentry/webvitals.com.
`npx skills add https://github.com/getsentry/webvitals.com --skill ai-sdk`Download ZIPGitHub
## Prerequisites
Before searching docs, check if `node_modules/ai/docs/` exists. If not, install only the `ai` package using the project's package manager (e.g., `pnpm add ai`).
Do not install other packages at this stage. Provider packages (e.g., `@ai-sdk/openai`) and client packages (e.g., `@ai-sdk/react`) should be installed later when needed based on user requirements.
## Critical: Do Not Trust Internal Knowledge
Everything you know about the AI SDK is outdated or wrong. Your training data contains obsolete APIs, deprecated patterns, and incorrect usage.
When working with the AI SDK:
* Ensure `ai` package is installed (see Prerequisites)
* Search `node_modules/ai/docs/` and `node_modules/ai/src/` for current APIs
* If not found locally, search ai-sdk.dev documentation (instructions below)
* Never rely on memory - always verify against source code or docs
* `useChat` has changed significantly - check Common Errors before writing client code
* When deciding which model and provider to use (e.g. OpenAI, Anthropic, Gemini), use the Vercel AI Gateway provider unless the user specifies otherwise. See AI Gateway Reference for usage details.
* Always fetch current model IDs - Never use model IDs from memory. Before writing code that uses a model, run `curl -s https://ai-gateway.vercel.sh/v1/models | jq -r '[.data[] | select(.id | startswith("provider/")) | .id] | reverse | .[]'` (replacing `provider` with the relevant provider like `anthropic`, `openai`, or `google`) to get the full list with newest models first. Use the model with the highest version number (e.g., `claude-sonnet-4-5` over `claude-sonnet-4` over `claude-3-5-sonnet`).
* Run typecheck after changes to ensure code is correct
* Be minimal - Only specify options that differ from defaults. When unsure of defaults, check docs or source rather than guessing or over-specifying.
If you cannot find documentation to support your answer, state that explicitly.
## Finding Documentation
### [email protected]+
Search bundled docs and source in `node_modules/ai/`:
* Docs: `grep "query" node_modules/ai/docs/`
* Source: `grep "query" node_modules/ai/src/`
Provider packages include docs at `node_modules/@ai-sdk/<provider>/docs/`.
### Earlier versions
* Search: `https://ai-sdk.dev/api/search-docs?q=your_query`
* Fetch `.md` URLs from results (e.g., `https://ai-sdk.dev/docs/agents/building-agents.md`)
## When Typecheck Fails
Before searching source code, grep Common Errors for the failing property or function name. Many type errors are caused by deprecated APIs documented there.
If not found in common-errors.md:
* Search `node_modules/ai/src/` and `node_modules/ai/docs/`
* Search ai-sdk.dev (for earlier versions or if not found locally)
## Building and Consuming Agents
### Creating Agents
Always use the `ToolLoopAgent` pattern. Search `node_modules/ai/docs/` for current agent creation APIs.
File conventions: See type-safe-agents.md for where to save agents and tools.
Type Safety: When consuming agents with `useChat`, always use `InferAgentUIMessage<typeof agent>` for type-safe tool results. See reference.
### Consuming Agents (Framework-Specific)
Before implementing agent consumption:
* Check `package.json` to detect the project's framework/stack
* Search documentation for the framework's quickstart guide
* Follow the framework-specific patterns for streaming, API routes, and client integration
## References
* Common Errors - Renamed parameters reference (parameters → inputSchema, etc.)
* AI Gateway - Gateway setup and usage
* Type-Safe Agents with useChat - End-to-end type safety with InferAgentUIMessage
## More skills from sentry
sentry-cocoa-sdkby sentryFull Sentry SDK setup for Apple platforms (iOS, macOS, tvOS, watchOS, visionOS). Use when asked to "add Sentry to iOS", "add Sentry to Swift", "install…sentry-create-alertby sentryCreate Sentry alerts using the workflow engine API. Use when asked to create alerts, set up notifications, configure issue priority alerts, or build workflow…sentry-dotnet-sdkby sentryFull Sentry SDK setup for .NET. Use when asked to "add Sentry to .NET", "install Sentry for C#", or configure error monitoring, tracing, profiling, logging, or…sentry-fix-issuesby sentryFind and fix issues from Sentry using MCP. Use when asked to fix Sentry errors, debug production issues, investigate exceptions, or resolve bugs reported in…sentry-go-sdkby sentryFull Sentry SDK setup for Go. Use when asked to "add Sentry to Go", "install sentry-go", "setup Sentry in Go", or configure error monitoring, tracing, logging,…sentry-ios-swift-setupby sentrySetup Sentry in iOS/Swift apps. Use when asked to add Sentry to iOS, install sentry-cocoa SDK, or configure error monitoring for iOS applications using Swift…sentry-nextjs-sdkby sentryFull Sentry SDK setup for Next.js. Use when asked to "add Sentry to Next.js", "install @sentry/nextjs", or configure error monitoring, tracing, session replay,…sentry-otel-exporter-setupby sentryConfigure the OpenTelemetry Collector with Sentry Exporter for multi-project routing and automatic project creation. Use when setting up OTel with Sentry,…
---
**Source**: https://github.com/getsentry/webvitals.com/tree/HEAD/.agents/skills/ai-sdk
**Author**: sentry
**Discovered via**: mcpservers.org
Related skills 6
find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
appinsights-instrumentation
Guidance for instrumenting webapps with Azure Application Insights. Provides telemetry patterns, SDK setup, and configuration references. WHEN: how to instrument app, App Insights SDK, telemetry patterns, what is App Insights, Application Insights guidance, instrumentation examples, APM best practices.
azure-messaging
Troubleshoot and resolve issues with Azure Messaging SDKs for Event Hubs and Service Bus. Covers connection failures, authentication errors, message processing issues, and SDK configuration problems. WHEN: event hub SDK error, service bus SDK issue, messaging connection failure, AMQP error, event processor host issue, message lock lost, message lock expired, lock renewal, lock renewal batch, send timeout, receiver disconnected, SDK troubleshooting, azure messaging SDK, event hub consumer, ser...
azure-hosted-copilot-sdk
Build, deploy, and modify GitHub Copilot SDK apps on Azure. MANDATORY when codebase contains @github/copilot-sdk or CopilotClient in package.json. PREFER OVER azure-prepare when copilot-sdk markers detected. WHEN: copilot SDK, @github/copilot-sdk, copilot-powered app, build copilot app, prepare copilot app, add feature to copilot app, modify copilot app, BYOM, bring your own model, CopilotClient, createSession, sendAndWait, azd init copilot. DO NOT USE FOR: deploying already-prepared copilot-...
lark-event
Lark/Feishu real-time event listening / subscribing / consuming: stream events as NDJSON via `lark-cli event consume <EventKey>` (covers IM message receive, reactions, chat member changes, etc.). Use for Lark bots, real-time message processing, long-running subscribers, streaming webhook/push handlers. Supports `--max-events` / `--timeout` bounded runs and a stderr ready-marker contract — designed for AI agents running as subprocesses.
xget
Use when tasks involve Xget URL rewriting, registry/package/container/API acceleration, integrating Xget into Git, download tools, package managers, container builds, AI SDKs, CI/CD, deployment, self-hosting, or adapting commands and config from the live README `Use Cases` section into files, environments, shells, or base URLs.