Skip to content
TrustedSkillsbeta
Back to all skills

Logs

Official
vercel·vlatest·cloud·MIT

This skill captures and displays Vercel deployment logs in real-time, providing instant insights into your application's performance and troubleshooting.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add vercel/vercel-deploy-claude-code-plugin --skill logs -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

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/vercel-deploy-claude-code-plugin at ae067751b4.

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

Commit
ae067751b4
Manifest
skills/logs/SKILL.md
Scanned
1 file, 24 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

What it does

The logs skill provides access to deployment logs from Vercel deployments. It allows you to view detailed information about your deployments, including build steps, errors, and resource usage. This enables debugging and monitoring of your applications hosted on Vercel.

When to use it

  • Troubleshooting Deployment Errors: Investigate failed builds or unexpected behavior after a deployment.
  • Monitoring Application Performance: Track resource consumption and identify potential bottlenecks during deployments.
  • Auditing Deployment History: Review past deployments, their associated logs, and changes made.
  • Debugging Production Issues: Analyze logs to diagnose problems occurring in your live Vercel environment.

Key capabilities

  • Accesses Vercel deployment logs.
  • Provides detailed build information.
  • Displays error messages and resource usage data.
  • Allows review of past deployments.

Example prompts

  • "Show me the logs for my last deployment to production."
  • "What were the errors during the build process for commit [commit hash]?"
  • "Can you summarize the resource usage for my staging deployment?"

Tips & gotchas

Requires access to a Vercel account and project. The level of detail available in the logs depends on your Vercel plan and configuration.