[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill-vercel-labs-deep-investigation":3,"mdc-ulho0x-key":42,"related-repo-vercel-labs-deep-investigation":375,"related-org-vercel-labs-deep-investigation":427},{"slug":4,"name":4,"fn":5,"description":6,"org":7,"tags":11,"stars":28,"repoUrl":29,"updatedAt":30,"license":31,"forks":32,"topics":33,"repo":37,"sourceUrl":40,"mdContent":41},"deep-investigation","investigate operational problems and recommend solutions","Investigate an operational problem to determine what happened, assess its impact, and recommend next steps using a hypothesis-backed approach.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},"vercel-labs","Vercel Labs","https:\u002F\u002Fpexgzepcugksgbtrxkhf.supabase.co\u002Fstorage\u002Fv1\u002Fobject\u002Fpublic\u002Forg-logos\u002Fvercel-labs.png",[12,16,19,22,25],{"name":13,"slug":14,"type":15},"SRE","sre","tag",{"name":17,"slug":18,"type":15},"Operations","operations",{"name":20,"slug":21,"type":15},"Analysis","analysis",{"name":23,"slug":24,"type":15},"Diagnostics","diagnostics",{"name":26,"slug":27,"type":15},"Incident Response","incident-response",6,"https:\u002F\u002Fgithub.com\u002Fvercel-labs\u002Feve-sre-agent-template","2026-08-27T13:32:49.407914",null,1,[34,35,36],"agent","ai","vercel",{"repoUrl":29,"stars":28,"forks":32,"topics":38,"description":39},[34,35,36],"Meet sre, an eve incident response agent.","https:\u002F\u002Fgithub.com\u002Fvercel-labs\u002Feve-sre-agent-template\u002Ftree\u002FHEAD\u002Fagent\u002Fskills\u002Fdeep-investigation","---\nname: deep-investigation\ndescription: Investigate an operational problem to determine what happened, assess its impact, and recommend next steps using a hypothesis-backed approach.\n---\n\n# Evidence-Backed Investigation\n\nInvestigate an operational problem using relevant evidence to explain what happened, assess the impact, and identify useful next steps.\n\n## Procedure\n\n### 1. Understand the request\n\nScan the conversation for:\n\n- The reported symptom or unexpected behavior\n- The affected service, environment, region, or workflow\n- The relevant timestamps or time range\n- Links to external context\n- What the user needs to decide or do\n\nUse available context first. Fetch additional context when it can change the conclusion or next action.\n\nPerform a quick scan using available tools to determine if the problem is related to a recent, ongoing incident.\n\n### 2. Generate hypotheses\n\nAfter identifying what went wrong, generate 2-4 plausible root-cause hypotheses. Each must include:\n\n- A short label\n- Why the hypothesis is plausible based on the available context\n- The signals that can validate or invalidate it\n\nPrioritize the most plausible hypotheses and the signals most likely to distinguish between them.\n\n### 3. Validate hypotheses and determine what happened\n\nInvestigate each hypothesis using the hypothesis-validation skill. For each hypothesis, determine whether it is validated, invalidated, or inconclusive and explain the conclusion with specific evidence.\n\nEstablish:\n\n- What changed or failed\n- When it started\n- Whether it is ongoing, recovering, or resolved\n- Which explanation is best supported by the evidence\n\nDo not require a validated root cause. Clearly distinguish observed facts, supported explanations, and unknowns.\n\nRecord findings as you validate. Follow the Evidence rules in the agent instructions. Call `evidence_record`, `evidence_remove`, and `evidence_list` as those rules say.\n\n### 4. Assess the impact\n\nDetermine:\n\n- Which services, endpoints, regions, workflows, or users are affected\n- How severe and widespread the effect is\n- Whether the impact is increasing, stable, decreasing, or no longer present\n- Which important impact could not be confirmed\n\nDo not infer customer impact from an error or alert alone.\n\n### 5. Choose next steps\n\nRecommend 1-4 concrete actions based on the evidence. Prioritize actions that:\n\n- Reduce current impact\n- Confirm an important unknown\n- Restore normal operation\n- Prevent an unsafe or premature change\n\nState what each action is expected to accomplish. Do not recommend broad follow-up work unless it helps with the current decision.\n\n## Result\n\nIf the invoking prompt prescribes an exact output shape, follow it and fold the findings below into those sections rather than adding more headings. Otherwise, answer with:\n\n### What happened\n\nA short explanation of the observed behavior, timeline, current state, and best-supported cause. State important unknowns. Include related or recurring incidents only when this turn's evidence shows them. Do not state that no related incident exists because you do not have complete incident history to search.\n\n### Impact\n\nThe confirmed scope and severity. Clearly identify impact that could not be confirmed.\n\n### Next steps\n\nA ranked list of 1-4 concrete actions for the responder.\n\n## Boundaries\n\n- Do not assume the request represents a declared incident.\n- Do not require a root cause before giving useful next steps.\n- If the task is to validate one specific hypothesis, do not generate new hypotheses. Use the hypothesis-validation skill.\n",{"data":43,"body":44},{"name":4,"description":6},{"type":45,"children":46},"root",[47,56,62,69,76,81,111,116,121,127,132,150,155,161,166,171,194,199,229,235,240,263,268,274,279,302,307,313,318,324,329,335,340,346,351,357],{"type":48,"tag":49,"props":50,"children":52},"element","h1",{"id":51},"evidence-backed-investigation",[53],{"type":54,"value":55},"text","Evidence-Backed Investigation",{"type":48,"tag":57,"props":58,"children":59},"p",{},[60],{"type":54,"value":61},"Investigate an operational problem using relevant evidence to explain what happened, assess the impact, and identify useful next steps.",{"type":48,"tag":63,"props":64,"children":66},"h2",{"id":65},"procedure",[67],{"type":54,"value":68},"Procedure",{"type":48,"tag":70,"props":71,"children":73},"h3",{"id":72},"_1-understand-the-request",[74],{"type":54,"value":75},"1. Understand the request",{"type":48,"tag":57,"props":77,"children":78},{},[79],{"type":54,"value":80},"Scan the conversation for:",{"type":48,"tag":82,"props":83,"children":84},"ul",{},[85,91,96,101,106],{"type":48,"tag":86,"props":87,"children":88},"li",{},[89],{"type":54,"value":90},"The reported symptom or unexpected behavior",{"type":48,"tag":86,"props":92,"children":93},{},[94],{"type":54,"value":95},"The affected service, environment, region, or workflow",{"type":48,"tag":86,"props":97,"children":98},{},[99],{"type":54,"value":100},"The relevant timestamps or time range",{"type":48,"tag":86,"props":102,"children":103},{},[104],{"type":54,"value":105},"Links to external context",{"type":48,"tag":86,"props":107,"children":108},{},[109],{"type":54,"value":110},"What the user needs to decide or do",{"type":48,"tag":57,"props":112,"children":113},{},[114],{"type":54,"value":115},"Use available context first. Fetch additional context when it can change the conclusion or next action.",{"type":48,"tag":57,"props":117,"children":118},{},[119],{"type":54,"value":120},"Perform a quick scan using available tools to determine if the problem is related to a recent, ongoing incident.",{"type":48,"tag":70,"props":122,"children":124},{"id":123},"_2-generate-hypotheses",[125],{"type":54,"value":126},"2. Generate hypotheses",{"type":48,"tag":57,"props":128,"children":129},{},[130],{"type":54,"value":131},"After identifying what went wrong, generate 2-4 plausible root-cause hypotheses. Each must include:",{"type":48,"tag":82,"props":133,"children":134},{},[135,140,145],{"type":48,"tag":86,"props":136,"children":137},{},[138],{"type":54,"value":139},"A short label",{"type":48,"tag":86,"props":141,"children":142},{},[143],{"type":54,"value":144},"Why the hypothesis is plausible based on the available context",{"type":48,"tag":86,"props":146,"children":147},{},[148],{"type":54,"value":149},"The signals that can validate or invalidate it",{"type":48,"tag":57,"props":151,"children":152},{},[153],{"type":54,"value":154},"Prioritize the most plausible hypotheses and the signals most likely to distinguish between them.",{"type":48,"tag":70,"props":156,"children":158},{"id":157},"_3-validate-hypotheses-and-determine-what-happened",[159],{"type":54,"value":160},"3. Validate hypotheses and determine what happened",{"type":48,"tag":57,"props":162,"children":163},{},[164],{"type":54,"value":165},"Investigate each hypothesis using the hypothesis-validation skill. For each hypothesis, determine whether it is validated, invalidated, or inconclusive and explain the conclusion with specific evidence.",{"type":48,"tag":57,"props":167,"children":168},{},[169],{"type":54,"value":170},"Establish:",{"type":48,"tag":82,"props":172,"children":173},{},[174,179,184,189],{"type":48,"tag":86,"props":175,"children":176},{},[177],{"type":54,"value":178},"What changed or failed",{"type":48,"tag":86,"props":180,"children":181},{},[182],{"type":54,"value":183},"When it started",{"type":48,"tag":86,"props":185,"children":186},{},[187],{"type":54,"value":188},"Whether it is ongoing, recovering, or resolved",{"type":48,"tag":86,"props":190,"children":191},{},[192],{"type":54,"value":193},"Which explanation is best supported by the evidence",{"type":48,"tag":57,"props":195,"children":196},{},[197],{"type":54,"value":198},"Do not require a validated root cause. Clearly distinguish observed facts, supported explanations, and unknowns.",{"type":48,"tag":57,"props":200,"children":201},{},[202,204,211,213,219,221,227],{"type":54,"value":203},"Record findings as you validate. Follow the Evidence rules in the agent instructions. Call ",{"type":48,"tag":205,"props":206,"children":208},"code",{"className":207},[],[209],{"type":54,"value":210},"evidence_record",{"type":54,"value":212},", ",{"type":48,"tag":205,"props":214,"children":216},{"className":215},[],[217],{"type":54,"value":218},"evidence_remove",{"type":54,"value":220},", and ",{"type":48,"tag":205,"props":222,"children":224},{"className":223},[],[225],{"type":54,"value":226},"evidence_list",{"type":54,"value":228}," as those rules say.",{"type":48,"tag":70,"props":230,"children":232},{"id":231},"_4-assess-the-impact",[233],{"type":54,"value":234},"4. Assess the impact",{"type":48,"tag":57,"props":236,"children":237},{},[238],{"type":54,"value":239},"Determine:",{"type":48,"tag":82,"props":241,"children":242},{},[243,248,253,258],{"type":48,"tag":86,"props":244,"children":245},{},[246],{"type":54,"value":247},"Which services, endpoints, regions, workflows, or users are affected",{"type":48,"tag":86,"props":249,"children":250},{},[251],{"type":54,"value":252},"How severe and widespread the effect is",{"type":48,"tag":86,"props":254,"children":255},{},[256],{"type":54,"value":257},"Whether the impact is increasing, stable, decreasing, or no longer present",{"type":48,"tag":86,"props":259,"children":260},{},[261],{"type":54,"value":262},"Which important impact could not be confirmed",{"type":48,"tag":57,"props":264,"children":265},{},[266],{"type":54,"value":267},"Do not infer customer impact from an error or alert alone.",{"type":48,"tag":70,"props":269,"children":271},{"id":270},"_5-choose-next-steps",[272],{"type":54,"value":273},"5. Choose next steps",{"type":48,"tag":57,"props":275,"children":276},{},[277],{"type":54,"value":278},"Recommend 1-4 concrete actions based on the evidence. Prioritize actions that:",{"type":48,"tag":82,"props":280,"children":281},{},[282,287,292,297],{"type":48,"tag":86,"props":283,"children":284},{},[285],{"type":54,"value":286},"Reduce current impact",{"type":48,"tag":86,"props":288,"children":289},{},[290],{"type":54,"value":291},"Confirm an important unknown",{"type":48,"tag":86,"props":293,"children":294},{},[295],{"type":54,"value":296},"Restore normal operation",{"type":48,"tag":86,"props":298,"children":299},{},[300],{"type":54,"value":301},"Prevent an unsafe or premature change",{"type":48,"tag":57,"props":303,"children":304},{},[305],{"type":54,"value":306},"State what each action is expected to accomplish. Do not recommend broad follow-up work unless it helps with the current decision.",{"type":48,"tag":63,"props":308,"children":310},{"id":309},"result",[311],{"type":54,"value":312},"Result",{"type":48,"tag":57,"props":314,"children":315},{},[316],{"type":54,"value":317},"If the invoking prompt prescribes an exact output shape, follow it and fold the findings below into those sections rather than adding more headings. Otherwise, answer with:",{"type":48,"tag":70,"props":319,"children":321},{"id":320},"what-happened",[322],{"type":54,"value":323},"What happened",{"type":48,"tag":57,"props":325,"children":326},{},[327],{"type":54,"value":328},"A short explanation of the observed behavior, timeline, current state, and best-supported cause. State important unknowns. Include related or recurring incidents only when this turn's evidence shows them. Do not state that no related incident exists because you do not have complete incident history to search.",{"type":48,"tag":70,"props":330,"children":332},{"id":331},"impact",[333],{"type":54,"value":334},"Impact",{"type":48,"tag":57,"props":336,"children":337},{},[338],{"type":54,"value":339},"The confirmed scope and severity. Clearly identify impact that could not be confirmed.",{"type":48,"tag":70,"props":341,"children":343},{"id":342},"next-steps",[344],{"type":54,"value":345},"Next steps",{"type":48,"tag":57,"props":347,"children":348},{},[349],{"type":54,"value":350},"A ranked list of 1-4 concrete actions for the responder.",{"type":48,"tag":63,"props":352,"children":354},{"id":353},"boundaries",[355],{"type":54,"value":356},"Boundaries",{"type":48,"tag":82,"props":358,"children":359},{},[360,365,370],{"type":48,"tag":86,"props":361,"children":362},{},[363],{"type":54,"value":364},"Do not assume the request represents a declared incident.",{"type":48,"tag":86,"props":366,"children":367},{},[368],{"type":54,"value":369},"Do not require a root cause before giving useful next steps.",{"type":48,"tag":86,"props":371,"children":372},{},[373],{"type":54,"value":374},"If the task is to validate one specific hypothesis, do not generate new hypotheses. Use the hypothesis-validation skill.",{"items":376,"total":426},[377,385,399,416],{"slug":4,"name":4,"fn":5,"description":6,"org":378,"tags":379,"stars":28,"repoUrl":29,"updatedAt":30},{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[380,381,382,383,384],{"name":20,"slug":21,"type":15},{"name":23,"slug":24,"type":15},{"name":26,"slug":27,"type":15},{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},{"slug":386,"name":386,"fn":387,"description":388,"org":389,"tags":390,"stars":28,"repoUrl":29,"updatedAt":398},"hypothesis-validation","validate operational hypotheses through investigation","Given a hypothesis, take the necessary investigation steps to validate, invalidate, or reach an inconclusive result for the hypothesis.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[391,392,393,396,397],{"name":20,"slug":21,"type":15},{"name":23,"slug":24,"type":15},{"name":394,"slug":395,"type":15},"Engineering","engineering",{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},"2026-08-27T13:33:16.558074",{"slug":400,"name":400,"fn":401,"description":402,"org":403,"tags":404,"stars":28,"repoUrl":29,"updatedAt":415},"on-call-handoff","summarize on-call shift handoffs","Summarize a personal or team on-call shift from supplied context, Slack, Datadog, GitHub, and Vercel. Activate when asked for an on-call handoff, shift summary, rotation handoff, what to tell the next on-call, or leaving on-call.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[405,408,411,412],{"name":406,"slug":407,"type":15},"Communications","communications",{"name":409,"slug":410,"type":15},"Management","management",{"name":17,"slug":18,"type":15},{"name":413,"slug":414,"type":15},"Runbooks","runbooks","2026-08-27T13:33:04.26561",{"slug":417,"name":417,"fn":418,"description":419,"org":420,"tags":421,"stars":28,"repoUrl":29,"updatedAt":425},"suggest-follow-ups","suggest incident follow-up actions","Suggest high-leverage incident follow-up actions from established root cause and incident context. Activate when asked for follow-ups, action items, preventive measures, or \"what should we do so this doesn't happen again\" after an incident.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[422,423,424],{"name":26,"slug":27,"type":15},{"name":17,"slug":18,"type":15},{"name":13,"slug":14,"type":15},"2026-08-27T13:33:16.147912",4,{"items":428,"total":599},[429,447,459,471,486,503,515,533,546,557,568,580],{"slug":430,"name":430,"fn":431,"description":432,"org":433,"tags":434,"stars":444,"repoUrl":445,"updatedAt":446},"agent-browser","automate browser interactions for AI agents","Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to \"open a website\", \"fill out a form\", \"click a button\", \"take a screenshot\", \"scrape data from a page\", \"test this web app\", \"login to a site\", \"automate browser actions\", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[435,438,441],{"name":436,"slug":437,"type":15},"Agents","agents",{"name":439,"slug":440,"type":15},"Automation","automation",{"name":442,"slug":443,"type":15},"Browser Automation","browser-automation",38346,"https:\u002F\u002Fgithub.com\u002Fvercel-labs\u002Fagent-browser","2026-08-24T03:36:10.45111",{"slug":448,"name":448,"fn":449,"description":450,"org":451,"tags":452,"stars":444,"repoUrl":445,"updatedAt":458},"agentcore","run browser automation on AWS Bedrock","Run agent-browser on AWS Bedrock AgentCore cloud browsers. Use when the user wants to use AgentCore, run browser automation on AWS, use a cloud browser with AWS credentials, or needs a managed browser session backed by AWS infrastructure. Triggers include \"use agentcore\", \"run on AWS\", \"cloud browser with AWS\", \"bedrock browser\", \"agentcore session\", or any task requiring AWS-hosted browser automation.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[453,454,457],{"name":439,"slug":440,"type":15},{"name":455,"slug":456,"type":15},"AWS","aws",{"name":442,"slug":443,"type":15},"2026-07-17T06:08:33.665276",{"slug":460,"name":460,"fn":461,"description":462,"org":463,"tags":464,"stars":444,"repoUrl":445,"updatedAt":470},"core","navigate and interact with web pages","Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[465,466,467],{"name":436,"slug":437,"type":15},{"name":442,"slug":443,"type":15},{"name":468,"slug":469,"type":15},"Navigation","navigation","2026-08-27T13:05:09.446966",{"slug":472,"name":472,"fn":473,"description":474,"org":475,"tags":476,"stars":444,"repoUrl":445,"updatedAt":485},"derive-client","reverse engineer internal APIs from browser traffic","Reverse-engineer a website's internal API by recording browser traffic into a HAR file, then generate a standalone client or CLI that calls the endpoints directly, with no browser needed after the first recording. Use when asked to \"derive a client\", \"build a CLI for \u003Csite>\", \"reverse engineer this site's API\", \"record network requests\", \"turn this site into an API\", or when the same site will be automated repeatedly and direct HTTP calls would beat driving the browser every time.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[477,480,481,482],{"name":478,"slug":479,"type":15},"API Development","api-development",{"name":439,"slug":440,"type":15},{"name":442,"slug":443,"type":15},{"name":483,"slug":484,"type":15},"Web Scraping","web-scraping","2026-07-20T06:24:11.928835",{"slug":487,"name":487,"fn":488,"description":489,"org":490,"tags":491,"stars":444,"repoUrl":445,"updatedAt":502},"dogfood","perform exploratory testing on web applications","Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to \"dogfood\", \"QA\", \"exploratory test\", \"find issues\", \"bug hunt\", \"test this app\u002Fsite\u002Fplatform\", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[492,493,496,499],{"name":442,"slug":443,"type":15},{"name":494,"slug":495,"type":15},"Debugging","debugging",{"name":497,"slug":498,"type":15},"QA","qa",{"name":500,"slug":501,"type":15},"Testing","testing","2026-07-17T06:07:41.421482",{"slug":504,"name":504,"fn":505,"description":506,"org":507,"tags":508,"stars":444,"repoUrl":445,"updatedAt":514},"electron","automate Electron desktop applications","Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include \"automate Slack app\", \"control VS Code\", \"interact with Discord app\", \"test this Electron app\", \"connect to desktop app\", or any task requiring automation of a native Electron application.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[509,510,511],{"name":436,"slug":437,"type":15},{"name":442,"slug":443,"type":15},{"name":512,"slug":513,"type":15},"Desktop","desktop","2026-07-17T06:08:28.007783",{"slug":516,"name":516,"fn":517,"description":518,"org":519,"tags":520,"stars":444,"repoUrl":445,"updatedAt":532},"protected-vercel-deployments","access protected Vercel deployments","Access and test Vercel deployments protected by Vercel Authentication, SSO, or Deployment Protection with agent-browser. Use when a preview or production URL redirects to a Vercel login page, returns a protection 401 or 403, or needs short-lived Trusted Sources OIDC authentication instead of a static bypass secret or public exception.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[521,524,527,530],{"name":522,"slug":523,"type":15},"Auth","auth",{"name":525,"slug":526,"type":15},"Deployment","deployment",{"name":528,"slug":529,"type":15},"Security","security",{"name":531,"slug":36,"type":15},"Vercel","2026-08-24T03:57:05.330407",{"slug":534,"name":534,"fn":535,"description":536,"org":537,"tags":538,"stars":444,"repoUrl":445,"updatedAt":545},"slack","interact with Slack workspaces","Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include \"check my Slack\", \"what channels have unreads\", \"send a message to\", \"search Slack for\", \"extract from Slack\", \"find who said\", or any task requiring programmatic Slack interaction.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[539,540,543],{"name":442,"slug":443,"type":15},{"name":541,"slug":542,"type":15},"Messaging","messaging",{"name":544,"slug":534,"type":15},"Slack","2026-07-17T06:08:27.679015",{"slug":547,"name":547,"fn":548,"description":549,"org":550,"tags":551,"stars":444,"repoUrl":445,"updatedAt":556},"vercel-sandbox","run browser automation in Vercel Sandbox","Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include \"Vercel Sandbox browser\", \"microVM Chrome\", \"agent-browser in sandbox\", \"browser automation on Vercel\", or any task requiring Chrome in a Vercel Sandbox.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[552,553,554,555],{"name":439,"slug":440,"type":15},{"name":442,"slug":443,"type":15},{"name":500,"slug":501,"type":15},{"name":531,"slug":36,"type":15},"2026-07-17T06:08:28.349899",{"slug":558,"name":558,"fn":559,"description":560,"org":561,"tags":562,"stars":565,"repoUrl":566,"updatedAt":567},"deploy-to-vercel","deploy applications to Vercel","Deploy applications and websites to Vercel. Use when the user requests deployment actions like \"deploy my app\", \"deploy and give me the link\", \"push this live\", or \"create a preview deployment\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[563,564],{"name":525,"slug":526,"type":15},{"name":531,"slug":36,"type":15},28993,"https:\u002F\u002Fgithub.com\u002Fvercel-labs\u002Fagent-skills","2026-07-17T06:08:41.18374",{"slug":569,"name":569,"fn":570,"description":571,"org":572,"tags":573,"stars":565,"repoUrl":566,"updatedAt":579},"vercel-cli-with-tokens","manage Vercel projects via CLI","Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. \"deploy to vercel\", \"set up vercel\", \"add environment variables to vercel\".",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[574,577,578],{"name":575,"slug":576,"type":15},"CLI","cli",{"name":525,"slug":526,"type":15},{"name":531,"slug":36,"type":15},"2026-07-17T06:08:41.84179",{"slug":581,"name":581,"fn":582,"description":583,"org":584,"tags":585,"stars":565,"repoUrl":566,"updatedAt":598},"vercel-composition-patterns","implement scalable React composition patterns","React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.",{"slug":8,"name":9,"logoUrl":10,"githubOrg":8},[586,589,592,595],{"name":587,"slug":588,"type":15},"Best Practices","best-practices",{"name":590,"slug":591,"type":15},"Frontend","frontend",{"name":593,"slug":594,"type":15},"React","react",{"name":596,"slug":597,"type":15},"UI Components","ui-components","2026-07-17T06:05:40.576913",104]