Conventions for observing a multi-step AI SDK agent in a Next.js app — how to model every agent boundary as a closed TypeScript discriminated union, emit it from a single recorder that isolates volatile experimental callback names, stream it as custom data-trace-event parts over the same UI message stream, reduce it in a store, and derive the view through pure selectors with cost computed in one pricing module. Use whenever creating, updating, or porting the src/lib/trace module — trace event union, recorder, pricing, run store, selectors, or the agent run route. Triggers include: 'observe the agent', 'trace events', 'agent timeline', 'token usage', 'tool call timeline', 'stream agent steps', 'cost per run', 'add a trace event', 'instrument the agent'.
EnglishConventions for the multi-provider model layer in Next.js + AI SDK apps — how to structure the registry, customProvider aliases, available-providers detection, and model resolution so the rest of the app never touches raw model strings or provider packages. Use whenever creating, updating, or porting the src/lib/ai/ module — registry, customProvider aliases, available-providers detection, model resolution. Triggers include: 'set up models', 'add a provider', 'multi-provider', 'model registry', 'model picker', 'switch model'.
EnglishIncludes Agent Observability Pattern and AI Model Layer.
Supported by the Atlas install prompt. Skill-specific requirements vary.
Pack stats
What’s included
Agent Observability Pattern
Conventions for observing a multi-step AI SDK agent in a Next.js app — how to model every agent boundary as a closed TypeScript discriminated union, emit it from a single recorder that isolates volatile experimental callback names, stream it as custom data-trace-event parts over the same UI message stream, reduce it in a store, and derive the view through pure selectors with cost computed in one pricing module. Use whenever creating, updating, or porting the src/lib/trace module — trace event union, recorder, pricing, run store, selectors, or the agent run route. Triggers include: 'observe the agent', 'trace events', 'agent timeline', 'token usage', 'tool call timeline', 'stream agent steps', 'cost per run', 'add a trace event', 'instrument the agent'.
AI Model Layer
Conventions for the multi-provider model layer in Next.js + AI SDK apps — how to structure the registry, customProvider aliases, available-providers detection, and model resolution so the rest of the app never touches raw model strings or provider packages. Use whenever creating, updating, or porting the src/lib/ai/ module — registry, customProvider aliases, available-providers detection, model resolution. Triggers include: 'set up models', 'add a provider', 'multi-provider', 'model registry', 'model picker', 'switch model'.
Quick start
- Choose your skills. Select individual skills above, or choose the entire pack.
- Copy the install prompt. Use Copy install prompt above the list.
- Send it to your agent. Paste into your coding agent’s chat. Your agent reviews the source and guides the setup.
Try it with your agent
After installation, start with a request like:
Use the Agent Observability Pattern skill to help with my task.
Ask me for the context you need before getting started.Requirements & license
- A coding agent that can access your project files and install skills.
- Your agent checks each skill’s instructions, dependencies, and permissions during setup.
- Reported license for the skills shown: MIT. The author’s terms apply.