Skip to content
TrustedSkillsbeta
Back to all skills

Render Debug

Checked
render-oss·vlatest·testing·MIT

Visualize render engine state and debug rendering issues directly within the scene using detailed overlays and data displays.

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

Commit
3f2aa30eaa
Manifest
skills/render-debug/SKILL.md
Scanned
7 files, 2,824 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-debug skill provides debugging capabilities for Render applications. It allows users to inspect application logs, view metrics, and troubleshoot issues directly within the agent's workflow. This facilitates faster identification and resolution of problems in deployed applications.

When to use it

  • Troubleshooting Application Errors: When an application is experiencing unexpected behavior or errors.
  • Monitoring Performance: To analyze key performance indicators (KPIs) and identify bottlenecks.
  • Debugging Deployment Issues: During deployment processes, to diagnose failures and ensure successful deployments.
  • Investigating Log Data: For detailed analysis of application events and error messages.

Key capabilities

  • Log inspection
  • Metric viewing
  • Application troubleshooting

Example prompts

  • "Show me the latest logs for my 'web' service."
  • "What is the average response time for my API endpoint?"
  • "Why did my deployment fail yesterday?"

Tips & gotchas

The skill requires access to a Render account and appropriate permissions to view application resources. Ensure your agent has been configured with these credentials for proper functionality.