Skip to content
TrustedSkillsbeta
Back to all skills

Runtime Debug

Official
vercel·vlatest·testing·MIT

Automatically identifies and reports runtime errors in Vercel deployments, simplifying debugging and improving application stability.

Repository

Install on your platform

This skill no longer installs under the name runtime-debug. SKILL.md is marked internal, so the skills CLI hides it.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-22. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

vercel

Matched to the vendor's own GitHub organisation.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned vercel/next.js at e7feae7d53.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
e7feae7d53
Manifest
.agents/skills/runtime-debug/SKILL.md
Scanned
1 file, 55 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The runtime-debug skill enables AI agents to inspect and troubleshoot Next.js applications directly within the browser environment. It provides access to real-time execution data, allowing agents to analyze runtime behavior without needing a local development setup.

When to use it

  • Diagnosing complex client-side errors that occur only in production or staging environments.
  • Investigating performance bottlenecks by examining actual render times and network requests.
  • Verifying how dynamic routes and middleware behave under specific user interactions.
  • Debugging issues related to server actions or data fetching strategies in Next.js apps.

Key capabilities

  • Access to the Next.js runtime context for deep inspection.
  • Real-time monitoring of application state during execution.
  • Integration with Vercel's ecosystem for seamless debugging workflows.
  • Support for analyzing both client and server-side rendering behaviors.

Example prompts

  • "Use runtime-debug to trace why the homepage fails to load on mobile devices in our Next.js app."
  • "Inspect the runtime logs to identify latency spikes during the checkout process."
  • "Debug a hydration mismatch error by examining the component execution flow using runtime-debug."

Tips & gotchas

Ensure your AI agent has appropriate permissions to access production or staging environments where the debugging session will run. This skill is specific to Next.js applications, so it cannot be used for generic web frameworks like React SPA without a Next.js adapter.