Skip to content
TrustedSkillsbeta
Back to all skills

Zeabur Deployment Logs

Checked
zeabur·vlatest·devops

Analyze Zeabur deployment logs to identify errors, performance bottlenecks, and potential rollback triggers.

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 zeabur/agent-skills --skill zeabur-deployment-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

zeabur

Taken from the source listing. We haven't verified who controls this account.

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 zeabur/zeabur-claude-plugin at 5c8c19a65b.

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

Scanned
2 files, 120 lines
Copies in repo
2 — all of them scanned
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

This skill allows AI agents to access and interpret deployment logs from Zeabur. It retrieves detailed information about deployments, including status, errors, and resource usage. This enables the agent to understand past deployments, troubleshoot issues, and monitor application health within the Zeabur platform.

When to use it

  • Troubleshooting Deployment Failures: Investigate why a recent deployment failed by examining error messages and logs.
  • Monitoring Application Performance: Track resource usage (CPU, memory) across different deployments to identify performance bottlenecks.
  • Auditing Deployment History: Review the sequence of deployments and their associated changes for compliance or debugging purposes.
  • Automated Rollbacks: Trigger automated rollback procedures based on deployment failure analysis within the logs.

Key capabilities

  • Retrieve deployment status (success, failed, pending)
  • Access detailed error messages from deployments
  • View resource usage metrics for deployments
  • Query logs by deployment ID or timestamp range

Example prompts

  • "Show me the logs for deployment 'my-app-v1.2'."
  • "What was the status of the last failed deployment?"
  • "List all deployments from yesterday and their resource usage."
  • “Find any errors in the logs for deployment ‘production’ between 9am and 10am.”

Tips & gotchas

  • Requires authentication with a Zeabur account. Ensure your AI agent has the necessary API keys or credentials configured to access your Zeabur environment.