Skip to content
TrustedSkillsbeta
Back to all skills

Render Monitor

Checked
render-oss·vlatest·video-media·MIT

Visually inspect and monitor rendered environments in real-time using this flexible, open-source AI observation tool.

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 render-oss/skills --skill render-monitor -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

render-oss

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 render-oss/skills at 3f2aa30eaa.

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

Scanned
2 files, 587 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 render-monitor skill provides monitoring capabilities for Render applications. It allows agents to check the status of deployed services, databases, and other resources within a Render environment. This includes retrieving metrics like CPU usage, memory consumption, and error rates to ensure application health and performance.

When to use it

  • Automated Health Checks: Schedule regular checks to proactively identify and address potential issues before they impact users.
  • Incident Response: Quickly assess the state of a Render environment during an incident to pinpoint the root cause.
  • Performance Optimization: Analyze resource utilization metrics to optimize application performance and reduce costs.
  • Deployment Validation: Verify successful deployments by confirming that all services are running as expected after updates.

Key capabilities

  • Service Status Retrieval
  • Database Monitoring
  • Resource Metric Collection (CPU, Memory)
  • Error Rate Tracking

Example prompts

  • "Check the status of my 'web-app' service on Render."
  • "What is the current CPU usage for my PostgreSQL database?"
  • "Report any errors occurring in my 'worker' service over the last hour."

Tips & gotchas

The skill requires appropriate credentials to access your Render account. Ensure that the AI agent has been configured with a valid Render API token or other authentication method.