neatlogs-ts-vercel-ai
Use when adding neatlogs observability to a TypeScript/Node.js project that uses the Vercel AI SDK (depends on the `ai` package, calls `generateText`/`streamText`).
SKILL.mdskills/neatlogs-ts-vercel-ai/SKILL.md
GitHubNeatlogs TypeScript Setup — Vercel AI SDK (ai)
This project uses the Vercel AI SDK (ai package: generateText, streamText, generateObject, streamObject, embed, embedMany, rerank). Neatlogs instruments it with wrapAISDK(ai) from neatlogs/ai — NOT via an instrumentations list. The wrapper opts the AI SDK's native OpenTelemetry support in per call.
init({ instrumentations: ['ai_sdk'] })throws — as does every other provider/framework key. The public option and registry were removed because global auto-instrumentors cannot be isolated from a co-tenant tracer. The JavaScript compatibility guard rejects the obsolete property; usewrapAISDK().
Core mechanism (DIFFERENT from other skills)
await init({ ... })first (sets up Neatlogs' private tracer — never registered globally). Never passinstrumentations: ['ai_sdk']—init()throws for it; the wrapper does the work.const { generateText, streamText, ... } = wrapAISDK(ai)— wrap theaimodule.- Use the WRAPPED functions exactly like the originals. Each wrapped call auto-creates a WORKFLOW/CHAIN parent span + native
ai.doGenerate/doStreamLLM children + tool-call TOOL children.
Steps
- Install →
references/1-install.md - Add init() + wrapAISDK →
references/2-init-and-wrap.md - Set environment variables →
references/3-set-env.md - Verify: use wrapped fns, don't double-wrap →
references/4-verify.md - Lifecycle (flush/shutdown) →
references/5-lifecycle.md
Running inside Next.js? (most apps are)
If the project is a Next.js app (it has next.config.* / app/ route handlers / server actions), follow references/nextjs.md. The key Next-specific requirement:
init()goes ininstrumentation.tsvia theregister()hook, importing neatlogs with a dynamicawait import("neatlogs")— NOT a top-level import. A static import 500s the build withCan't resolve 'crypto'.
Rules (apply to ALL steps)
await init(...)runs first (registers the TracerProvider). ThenwrapAISDK(ai).- NEVER pass
instrumentations: ['ai_sdk'](or any provider key) —init()throws. The wrapper is the instrumentation. A provider SDK called DIRECTLY outside the AI SDK needs its own helper (wrapOpenAI,wrapAnthropic, …). - Replace direct
aicalls with the WRAPPED equivalents: destructuregenerateText/streamText/etc. fromwrapAISDK(ai)and call those. Don't leave bareimport { generateText } from 'ai'call sites — they won't be traced. - Do NOT also wrap wrapped calls in
span()/trace()— the wrapper already opens the parent span. Add aWORKFLOWonly when the application entry point owns a real multi-step request/job; keep each wrapped AI-SDK call as its canonical child. - Neatlogs supports AI SDK v6 and v7 (
ai >=6 <8). Keep usingwrapAISDK(ai)in both versions; it selects v6'sexperimental_telemetryor v7'stelemetryautomatically. - AI SDK v7 requires Node.js 22+. Its
@ai-sdk/oteladapter is an optional dependency ofneatlogsand installs automatically unless optional dependencies are disabled. - Never hardcode API keys — use
process.env. - For EU projects, set
endpoint: 'https://eu.ingest.neatlogs.com'ininit(); for other managed projects, omitendpoint,baseUrl, andNEATLOGS_ENDPOINT.
Safety gate
Before any edit, confirm this service is TypeScript/Node.js. Identify its package manager from the manifest and lockfile, then read the declared and installed SDK version. Do not install or change dependencies during this inspection. Run exactly one project-local command for the detected package manager:
npm: npm exec --offline --no -- neatlogs doctor --local --json
pnpm: pnpm exec neatlogs doctor --local --json
Yarn: yarn run neatlogs doctor --local --json
Bun: bun --no-install run neatlogs doctor --local --json
These commands let the package manager select the platform-specific local
executable, including the Windows shim. Do not substitute npx, pnpm dlx,
yarn dlx, bunx, a Wizard command, or another downloaded Doctor. Local
mode must be read-only and network-free. It requires no credential and must not
change source or configuration. Require format_version: "neatlogs.doctor/v2", runtime.language: "typescript", and
runtime.schema_version: "2". Compare runtime.sdk_version with the
installed project package to prove that the runner did not select another copy.
Do not compare it with one hardcoded patch version.
If the command is missing or its result has the wrong format, language, schema, or installed-package identity, fail closed. Check the canonical package registry for the latest published stable release. If the project uses an older release, show the exact upgrade command for the detected package manager and obtain explicit user approval before running it. Accept newer compatible releases and never downgrade one. If the installed release is already current but lacks Doctor v2, stop and give safe manual/support remediation. Rerun local Doctor after any approved upgrade. Do not edit while this gate is unresolved.
A local pass proves only that the installed SDK produced and validated its
controlled in-process envelope. It does not prove that the application is
instrumented, that anything was exported, or that a hosted trace is visible.
Preserve every reason_code and remediation_code exactly. Treat a warning,
failure, or unknown future code as manual/support remediation unless the code is
explicitly safe/fixable here. The only source fixes allowed by this gate are:
INSTRUMENTOR_INACTIVE: apply only this skill's documented initialization or wrapper/hook step.ROOT_MISSING: add only the already-requested, documented WORKFLOW boundary at a confirmed entry point.ROOT_NOT_ENDED: add only this skill's documented lifecycle hook.
Do not edit for credential, authentication, transport, backend, ambiguous ownership, or unknown codes. Never reproduce backend PII, routing, mapping, or finalization implementation. Before any build, test, or user-workflow command, show the exact command and obtain explicit user approval. Make reruns idempotent: reread the target first and never duplicate initialization, wrappers, roots, or shutdown hooks. Keep a pre-edit diff. If an approved check fails, use the rollback plan to revert only the edits from this run when they can be isolated safely. Otherwise, stop and give manual recovery instructions that preserve unrelated user work.
After instrumentation, obtain approval for the project checks and one representative real workflow. Obtain separate approval for the authenticated probe. Use only a credential already supplied through the process environment. Never print it, place it in command arguments or files, copy it into output, or put it in agent context.
Run the matching project-local command:
npm: npm exec --offline --no -- neatlogs doctor --probe --json
pnpm: pnpm exec neatlogs doctor --probe --json
Yarn: yarn run neatlogs doctor --probe --json
Bun: bun --no-install run neatlogs doctor --probe --json
Probe mode sends one controlled four-span trace through POST /v1/traces with
x-neatlogs-doctor: v1, then reads that exact trace through
GET /api/traces/v3/{trace_id} with the same project credential. Accept a
probe pass only when capture and readback trace IDs match, the trace is
finalized, exactly four spans contain one meaningful WORKFLOW root with
AGENT→LLM and root→TOOL relationships, there are no duplicates, required
semantics and I/O are present, and token values remain numeric. Never infer
success from installation, local logs, exporter flush, HTTP 2xx, or any
uncorrelated trace. Probe success proves the controlled path only. Verify the
real user workflow separately through the completion gate below.
Completion gate
After local Doctor passes and the requested instrumentation is in place:
- Show the exact project build, test, and real-workflow commands and obtain explicit user approval before running them.
- Run only the approved checks. Restart a long-running process so it loads the new initialization and wrappers; keep reruns idempotent.
- Exercise one representative real user workflow. End every opened span and use the documented flush/shutdown lifecycle for that process type.
- Through the target project's normal product trace view or supported public read path, verify that exact run is finalized, has one meaningful root and the expected semantic hierarchy, and contains no duplicate operation spans.
Keep project credentials in the process environment or client secret storage; never put them in commands, output, files, or agent context. Do not use a legacy marker-discovery protocol. Installation, local logs, exporter flush, HTTP 2xx, a local Doctor pass, and a separate probe pass are not proof that the application's real workflow is correct. If the exact user trace cannot be inspected, report the missing access or observation as a blocker and provide rollback/manual recovery instructions without claiming completion.
Reference
- Next.js setup (serverExternalPackages + instrumentation.ts) →
references/nextjs.md - Sessions & end-users (per-turn
identify()) →references/sessions-and-end-users.md - Custom span()/trace() (for real app-owned request/job orchestration) →
references/decorators-and-traces.md - Troubleshooting →
references/troubleshooting.md