Skip to content
TrustedSkillsbeta
Back to all skills

Render Deploy

Official
openai·vlatest·devops

Automatically generates and deploys visual assets like images and videos based on text prompts and specifications.

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 openai/skills --skill render-deploy -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

openai

Matched to the vendor's own GitHub organisation.

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 failed 2 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • No undeclared network calls: failed

    Contacts 2 hosts that are neither well-known infrastructure nor declared in the skill's frontmatter: internal-api.render-internal.com, mcp.render.com.

    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

    mcp.render.comundeclaredinternal-api.render-internal.comundeclared

    What it found

    • skills/.curated/render-deploy/SKILL.md:153contacts mcp.render.com
      claude mcp add --transport http render https://mcp.render.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
    • skills/.curated/render-deploy/agents/openai.yaml:14contacts mcp.render.com
      url: "https://mcp.render.com/mcp"
    • skills/.curated/render-deploy/references/service-types.md:383contacts internal-api.render-internal.com
      const API_URL = 'http://internal-api.render-internal.com:10000';

  • No pipe-to-shell installers: failed

    Runs code fetched at install time in 1 place.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

    What it found

    • skills/.curated/render-deploy/SKILL.md:111tells the user to run: remote script piped into a shell(in the instructions, not code)
      - Linux/macOS: `curl -fsSL https://raw.githubusercontent.com/render-oss/cli/main/bin/install.sh | sh`

  • 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 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.

  • Pinned to a commit: passed

    Scanned openai/skills at 49f948faa9.

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

Commit
49f948faa9
Manifest
skills/.curated/render-deploy/SKILL.md
Scanned
19 files, 3,190 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

The render-deploy skill enables AI agents to interact with Render's cloud platform, allowing them to deploy applications directly from code repositories or existing deployments. It streamlines the workflow for getting web services live by managing environment variables and handling deployment triggers automatically.

When to use it

  • You need to launch a new application instance directly from a GitHub repository without manual CLI intervention.
  • Your agent requires the ability to update an existing Render service with new code changes instantly.
  • You want to configure specific environment variables for your application during the automated deployment process.
  • The workflow involves testing a build locally before pushing it to the production environment on Render.

Key capabilities

  • Deploys applications from supported source control providers like GitHub directly to Render infrastructure.
  • Manages and sets custom environment variables required for application configuration at runtime.
  • Triggers deployments automatically upon code pushes or manual requests within the agent's context.
  • Handles the lifecycle management of services, including starting and stopping instances as needed.

Example prompts

  • "Deploy my latest changes from the GitHub repository to our production Render service."
  • "Create a new web service on Render using this Dockerfile and set the database URL environment variable."
  • "Check the status of the current deployment and redeploy if the build fails due to missing dependencies."

Tips & gotchas

Ensure your source code repository contains a valid render.yaml configuration file or a compatible Dockerfile, as these are prerequisites for successful deployment. Verify that all necessary environment variables, such as database credentials, are securely provided before initiating the deployment command.