Skip to content
TrustedSkillsbeta
Back to all skills

Vps Checkup

Checked
jmerta·vlatest·other·MIT

This "VPS Checkup" skill scans your VPS for potential issues like outdated software and recommends optimizations to ensure peak performance & stability.

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 jmerta/codex-skills --skill vps-checkup -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

jmerta

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 jmerta/codex-skills at 929ed6ca7e.

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

Commit
929ed6ca7e
Manifest
vps-checkup/SKILL.md
Scanned
4 files, 165 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

vps-checkup

What it does

This skill enables AI agents to perform health checks and diagnostics on Virtual Private Servers (VPS). It allows the agent to verify system status, identify potential issues, and ensure server stability through automated monitoring routines.

When to use it

  • Automating routine maintenance tasks for production environments without manual intervention.
  • Diagnosing unexpected downtime or performance degradation on cloud infrastructure.
  • Validating that specific services are running correctly after a deployment or configuration change.
  • Proactively monitoring server health to prevent outages before they impact users.

Key capabilities

  • Executes comprehensive system diagnostics on VPS instances.
  • Identifies and reports on potential hardware or software failures.
  • Provides actionable insights into the current operational state of the server.

Example prompts

  • "Run a full health check on my production VPS and summarize any critical errors found."
  • "Check if the web server and database services are responding correctly on this instance."
  • "Perform a diagnostic scan to identify resource bottlenecks or security vulnerabilities."

Tips & gotchas

Ensure you have appropriate access permissions (such as SSH keys or API tokens) configured before requesting checks, as the agent needs direct connectivity to the target server. Be aware that running diagnostics on live production systems may consume additional CPU or memory resources; schedule these checks during low-traffic windows if possible.