fix: update vendored skills to latest versions

agent/skills/create-plugin-scaffold/SKILL.md

@@ -0,0 +1,68 @@
+---
+description: "Create a new Cursor plugin scaffold with a valid manifest, component directories, and marketplace wiring. Use when starting a new plugin or adding a plugin to a multi-plugin repository."
+---
+# Create plugin scaffold
+
+## Trigger
+
+You need to create a new Cursor plugin from scratch and make it ready for local use or marketplace submission.
+
+## Required Inputs
+
+- Plugin name (lowercase kebab-case)
+- Plugin purpose and target users
+- Component set to include (`rules`, `skills`, `agents`, `commands`, `hooks`, `mcpServers`)
+- Repository style (`single-plugin` or `multi-plugin marketplace`)
+
+## Output Location
+
+By default, create the plugin inside the user's local plugin directory:
+
+```
+~/.cursor/plugins/local/<plugin-name>/
+```
+
+This path makes the plugin immediately available to Cursor without any install step. If the user explicitly asks to create the plugin elsewhere (e.g. inside an existing repo or a specific directory), respect that choice instead.
+
+## Workflow
+
+1. Validate plugin name format: lowercase kebab-case, starts and ends with an alphanumeric character.
+2. Determine the target directory:
+   - Default: `~/.cursor/plugins/local/<plugin-name>/`
+   - Override: use the path the user specifies, if any.
+   - Create the directory (and parents) if it does not exist.
+3. Create base files inside the target directory:
+   - `.cursor-plugin/plugin.json`
+   - `README.md`
+   - `LICENSE`
+   - optional `CHANGELOG.md`
+4. Populate `plugin.json`:
+   - Required: `name`
+   - Recommended: `version`, `description`, `author`, `license`, `keywords`
+   - Add explicit component paths only when non-default discovery is needed.
+5. Create component files with valid frontmatter:
+   - Rules: `.mdc` with `description`, `alwaysApply`, optional `globs`
+   - Skills: `skills/<skill-name>/SKILL.md` with `name`, `description`
+   - Agents: `agents/*.md` with `name`, `description`
+   - Commands: `commands/*.(md|txt)` with `name`, `description`
+6. If repository uses `.cursor-plugin/marketplace.json`, add plugin entry:
+   - `name`
+   - `source`
+   - optional metadata (`description`, `keywords`, `category`, `tags`)
+7. Ensure all manifest paths are relative, valid, and do not use absolute paths or parent traversal.
+
+## Guardrails
+
+- Keep the plugin focused on one use case.
+- Prefer concise, actionable skill and rule text over long prose.
+- Do not reference files that do not exist.
+- Use folder discovery defaults unless custom paths are required.
+- Always save to `~/.cursor/plugins/local/<plugin-name>/` unless the user provides a different path.
+
+## Output
+
+- Created file tree for the plugin (with full path to the output directory)
+- Final `plugin.json`
+- Marketplace entry (if applicable)
+- Short validation report of required fields and component metadata
+- Confirmation that the plugin is saved under `~/.cursor/plugins/local/` and ready for use

plugins/ai-sdk/.agents/skills/ai-sdk/SKILL.md

@@ -3,78 +3,76 @@ name: ai-sdk
 description: 'Answer questions about the AI SDK and help build AI-powered features. Use when developers: (1) Ask about AI SDK functions like generateText, streamText, ToolLoopAgent, embed, or tools, (2) Want to build AI agents, chatbots, RAG systems, or text generation features, (3) Have questions about AI providers (OpenAI, Anthropic, Google, etc.), streaming, tool calling, structured output, or embeddings, (4) Use React hooks like useChat or useCompletion. Triggers on: "AI SDK", "Vercel AI SDK", "generateText", "streamText", "add AI to my app", "build an agent", "tool calling", "structured output", "useChat".'
 ---
 
-## Prerequisites
+## What the AI SDK Is
 
-This information is for AI SDK 7. Compare to version in `node_modules/ai/package.json`. If the versions don't match, warn the user.
+The AI SDK by Vercel (the `ai` package on npm) is a TypeScript toolkit for building AI applications. It provides a unified API across model providers for text generation, structured output, tool calling, agents, embeddings, and framework UI integrations.
 
-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`).
+- Repository: https://github.com/vercel/ai
+- Documentation: https://ai-sdk.dev/docs
 
-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 Your Own Memory
 
-## Critical: Do Not Trust Internal Knowledge
+Whatever you remember about the AI SDK is likely outdated. The SDK changes frequently across versions - APIs are renamed, removed, and added. Your training data almost certainly contains obsolete APIs, deprecated patterns, and model IDs that no longer exist. UI hooks like `useChat` are among the most frequently changed APIs, so be especially careful with client code.
 
-Everything you know about the AI SDK is outdated or wrong. Your training data contains obsolete APIs, deprecated patterns, and incorrect usage.
+**Never write AI SDK code from memory.** Always verify every API, option, and pattern against the documentation and source code for the version that is actually installed in the project.
 
-**When working with the AI SDK:**
+## Use the Bundled, Version-Matched Docs
 
-1. Ensure `ai` package is installed (see Prerequisites)
-2. Search `node_modules/ai/docs/` and `node_modules/ai/src/` for current APIs
-3. If not found locally, search ai-sdk.dev documentation (instructions below)
-4. Never rely on memory - always verify against source code or docs
-5. **`useChat` has changed significantly** - check [Common Errors](references/common-errors.md) before writing client code
-6. 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](references/ai-gateway.md) for usage details.
-7. **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`).
-8. Run typecheck after changes to ensure code is correct
-9. **Be minimal** - Only specify options that differ from defaults. When unsure of defaults, check docs or source rather than guessing or over-specifying.
+The `ai` package ships its full documentation and source code inside `node_modules`. These always match the installed version, so trust them over anything you remember.
 
-If you cannot find documentation to support your answer, state that explicitly.
+1. Ensure `ai` is installed. If `node_modules/ai/` does not exist, install **only** the `ai` package using the project's package manager (e.g. `pnpm add ai`). Install provider packages (e.g. `@ai-sdk/openai`) and framework packages (e.g. `@ai-sdk/react`) later, when the task requires them.
+2. Read and grep the bundled docs at `node_modules/ai/docs/` and the source at `node_modules/ai/src/`.
+3. Provider and framework packages bundle their own docs at `node_modules/@ai-sdk/<name>/docs/`.
+4. If something isn't in the bundled docs, search https://ai-sdk.dev/docs. You can append `.md` to any docs page URL to get its markdown, and search via `https://ai-sdk.dev/api/search-docs?q=your_query`.
+5. If you cannot find support for an answer in the docs or source, say so explicitly — do not guess.
 
-## Finding Documentation
+## AI Gateway: The Fastest Way to Start
 
-### ai@6.0.34+
+The Vercel AI Gateway is the fastest way to get started with the AI SDK. It provides access to models from OpenAI, Anthropic, Google, and other providers through a single API, without installing provider packages or managing multiple API keys.
 
-Search bundled docs and source in `node_modules/ai/`:
+To set it up:
 
-- **Docs**: `grep "query" node_modules/ai/docs/`
-- **Source**: `grep "query" node_modules/ai/src/`
+1. Authenticate with OIDC (for Vercel deployments) or get an AI Gateway API key.
+2. Provide it to your app via the `AI_GATEWAY_API_KEY` environment variable.
+3. Reference models with `provider/model` strings.
 
-Provider packages include docs at `node_modules/@ai-sdk/<provider>/docs/`.
+For exact setup, authentication, and usage, read the bundled guide and the AI Gateway docs.
 
-### Earlier versions
+### Choosing a Model
 
-1. Search: `https://ai-sdk.dev/api/search-docs?q=your_query`
-2. Fetch `.md` URLs from results (e.g., `https://ai-sdk.dev/docs/agents/building-agents.md`)
+Never use model IDs from memory — models are released and retired frequently. Fetch the current list before writing code that references a model. Do not truncate the list (e.g. with `head`) so you can find the newest models:
 
-## When Typecheck Fails
+```bash
+# All available models
+curl -s https://ai-gateway.vercel.sh/v1/models | jq -r '.data[].id'
 
-**Before searching source code**, grep [Common Errors](references/common-errors.md) for the failing property or function name. Many type errors are caused by deprecated APIs documented there.
+# Filter by provider (e.g. anthropic, openai, google)
+curl -s https://ai-gateway.vercel.sh/v1/models | jq -r '[.data[] | select(.id | startswith("anthropic/")) | .id] | reverse | .[]'
+```
 
-If not found in common-errors.md:
-
-1. Search `node_modules/ai/src/` and `node_modules/ai/docs/`
-2. Search ai-sdk.dev (for earlier versions or if not found locally)
+When multiple versions of a model exist, prefer the one with the highest version number.
 
 ## Building and Consuming Agents
 
-### Creating Agents
+Use the SDK's built-in agent abstraction (such as `ToolLoopAgent`) rather than hand-rolling tool-calling loops. For end-to-end type safety, infer the UI message type from your agent definition when consuming it on the client (e.g. with `useChat`). Consuming an agent is framework-specific: check `package.json` to detect the stack, then follow the matching quickstart.
+
+Look up the current agent, tool, and type-safety APIs in the bundled docs (`node_modules/ai/docs/`, especially the agents section) or at https://ai-sdk.dev/docs.
+
+## DevTools
 
-Always use the `ToolLoopAgent` pattern. Search `node_modules/ai/docs/` for current agent creation APIs.
+AI SDK DevTools captures your AI SDK calls - requests, responses, tool calls, token usage, and multi-step runs - so you can inspect exactly what your agents do. Use it while developing to debug generations. It is a separate package and is intended for local development only.
 
-**File conventions**: See [type-safe-agents.md](references/type-safe-agents.md) for where to save agents and tools.
+For setup instructions, read the bundled DevTools documentation.
 
-**Type Safety**: When consuming agents with `useChat`, always use `InferAgentUIMessage<typeof agent>` for type-safe tool results. See [reference](references/type-safe-agents.md).
+## Keep the SDK Current
 
-### Consuming Agents (Framework-Specific)
+Outdated installs are the most common source of errors. Compare the installed version against the latest:
 
-Before implementing agent consumption:
+- **Installed:** the `version` field in `node_modules/ai/package.json`.
+- **Latest:** run `npm view ai version`.
 
-1. Check `package.json` to detect the project's framework/stack
-2. Search documentation for the framework's quickstart guide
-3. Follow the framework-specific patterns for streaming, API routes, and client integration
+If the installed version is a major version (or more) behind the latest, tell the user they are on an old release, and recommend upgrading before continuing. Migration guides are at https://ai-sdk.dev/docs/migration-guides.
 
-## References
+## After Making Changes
 
-- [Common Errors](references/common-errors.md) - Renamed parameters reference (parameters → inputSchema, etc.)
-- [AI Gateway](references/ai-gateway.md) - Gateway setup and usage
-- [Type-Safe Agents with useChat](references/type-safe-agents.md) - End-to-end type safety with InferAgentUIMessage
-- [DevTools](references/devtools.md) - Set up local debugging and observability (development only)
+Run the project's type checker. Be minimal — only set options that differ from the defaults, checking docs or source for the defaults rather than over-specifying. Most type errors come from remembered, now-changed APIs; re-check the current docs and source when they occur.