Skip to content
TrustedSkillsbeta
Back to all skills

Eve Deploy Debugging

Checked
incept5·vlatest·testing·MIT

Helps with deployment, debugging as part of testing, debugging, and quality assurance workflows.

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 incept5/eve-skillpacks --skill eve-deploy-debugging -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

incept5

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

    Only contacts known or declared hosts: myorg-lmstudio.eve-tunnels.svc.cluster.local.

    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.

    Hosts contacted

    myorg-lmstudio.eve-tunnels.svc.cluster.locallocal

  • 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 incept5/eve-skillpacks at d8b938d71f.

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

Commit
d8b938d71f
Manifest
eve-se/eve-deploy-debugging/SKILL.md
Scanned
1 file, 289 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

This skill, Eve Deploy Debugging, assists with deploying applications and diagnosing issues within a testing or quality assurance workflow. It provides tools for managing deployments through an environment (staging), monitoring job progress, and troubleshooting failures using diagnostic commands and log analysis. The tool emphasizes controlled infrastructure changes via Terraform and uses the Eve CLI for application deployment management.

When to use it

  • Deploying applications to a staging environment.
  • Troubleshooting failed deployments or jobs.
  • Monitoring the health of an environment during deployment.
  • Diagnosing why a job won't start, is stuck, or has failed.
  • Investigating system-level issues impacting deployments and jobs.

Key capabilities

  • Environment Management: Create and use profiles for different environments (e.g., staging).
  • Deployment via CLI: Deploy applications using eve env deploy with options to bypass pipelines (--direct) and pass inputs.
  • Job Monitoring: Track job progress in real-time with eve job follow, poll status updates with eve job watch, and retrieve diagnostic information with eve job diagnose.
  • Log Analysis: Access raw worker logs (eve job runner-logs), system logs (eve system logs), and thread messages (eve thread messages).
  • Diagnostic Commands: Provides commands to check dependencies, environment readiness, orchestrator status, and secret lists.

Example prompts

  • "Deploy the application from the main branch to the staging environment."
  • "Show me the diagnostic information for job ID 12345."
  • "What is the current health of the staging environment?"
  • "Follow the progress of job ID 67890 in real-time."

Tips & gotchas

  • Infrastructure Changes: Direct Kubernetes resource modifications (like kubectl apply) are prohibited; use the Eve CLI (eve env, eve env deploy) for deployments.
  • Pipeline Bypass: Use --direct with caution, as it bypasses automated pipeline steps.
  • Polling: After a pipeline deployment, poll the pipeline endpoint (/pipelines/{name}/runs/{id}) until all steps complete and active_pipeline_run is null to confirm successful completion.