Skip to content
TrustedSkillsbeta
Back to all skills

Render Deploy

Listed
davila7·vlatest·frontend·MIT

Automatically renders and deploys updated frontend components based on code changes from davila7's design system.

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 davila7/claude-code-templates --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

davila7

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

    • cli-tool/components/skills/development/render-deploy/SKILL.md:154contacts mcp.render.com
      claude mcp add --transport http render https://mcp.render.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"
    • cli-tool/components/skills/development/render-deploy/agents/openai.yaml:14contacts mcp.render.com
      url: "https://mcp.render.com/mcp"
    • cli-tool/components/skills/development/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

    • cli-tool/components/skills/development/render-deploy/SKILL.md:112tells 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 davila7/claude-code-templates at 79182c51fb.

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

Scanned
19 files, 3,191 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

render-deploy

What it does

This skill enables AI agents to deploy frontend applications directly to Render, a cloud hosting platform. It streamlines the process of taking code and making it live without manual configuration steps.

When to use it

  • You have built a static site or web application and need immediate public access.
  • Your development workflow requires automated deployment after every code change.
  • You want to host projects on Render specifically for its reliability and pricing tiers.
  • You are integrating frontend delivery into an AI-driven coding pipeline.

Key capabilities

  • Direct integration with the Render cloud hosting service.
  • Automated deployment of frontend builds to production environments.
  • Simplified configuration for common web application structures.

Example prompts

  • "Deploy my React app to Render using the render-deploy skill."
  • "Configure and push my Next.js project live on Render."
  • "Automate the deployment of my static site to a Render URL."

Tips & gotchas

Ensure your code is committed to a repository accessible by the AI agent, as most hosting integrations require source control. Verify that you have a valid Render account configured before attempting deployment to avoid authentication errors.