Repository navigation
[skills] Add vercel-tracing skill - #336
Open
kakadiadarpan wants to merge 11 commits into
Open
kakadiadarpan wants to merge 11 commits into
kakadiadarpan wants to merge 11 commits into
Conversation
lucleray
approved these changes
Oct 14, 2026
lucleray
left a comment
lucleray
left a comment
Member
There was a problem hiding this comment.
looks good, thanks! a few non-blocking notes inline 👍
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem / Intent
Agents have no guidance for setting up OpenTelemetry on Vercel. They guess where
registerOTelgoes, miss incoming trace context, and misreadvercel tracesoutput. Spans then land in the wrong trace, or nobody checks them.Approach
A new
vercel-tracingskill focused on instrumentation setup.SKILL.mdhas a setup workflow with the Next.js registration snippet, an investigation workflow, and notes on how the CLI behaves in agent (non-interactive) mode. Short references cover framework setup (Next.js, SvelteKit, any other framework), custom spans, context propagation, sampling, capture, search, inspection, performance, and troubleshooting. Search guidance matches the JSON Lines output of Vercel CLI 64.The performance-optimizer agent includes the investigation workflow.
vercel-cliandvercel-functionschain to the skill onvercel tracesand@vercel/otel.Agents followed the skill on fresh Next.js 16.4 and SvelteKit 3 apps deployed to Vercel previews. Setup worked on the first deploy, and custom spans nested under the request in the same trace.