agentleFS
Sign inStart free
hebertzhuhebertzhu/agent-foundry/skills/render-deploy/SKILL.md

render-deploy

Skill0 starsChanged 8 months agoMITView on GitHub

Use when the user wants to deploy, publish, or set up an application on Render; prefer the Git-backed Blueprint flow with `render.yaml`, validate when the Render CLI is available, and return a dashboard deeplink plus next steps.

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use render-background-workers, render-blueprints and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • aaronbrethorstSkill

    render-background-workers

    Sets up and configures background workers on Render for queue-based job processing. Use when the user needs to process async jobs, consume from a queue, run Celery/Sidekiq/BullMQ/Asynq/Oban workers, handle graceful shutdown with SIGTERM, wire a worker to Key Value, or choose between workers and cron jobs for background work. Trigger terms: background worker, async jobs, queue consumer, Celery, Sidekiq, BullMQ, Asynq, Oban, job processing, SIGTERM, graceful shutdown.

    Also in 3 projects that use this

  • aaronbrethorstSkill

    render-blueprints

    Authors and validates render.yaml Blueprints for Render infrastructure. Use when the user needs to write or edit a render.yaml, wire services together with fromDatabase/fromService/fromGroup, set up projects and environments for multi-service apps, configure preview environments, validate against the schema, or fix immutable field errors. Trigger terms: render.yaml, Blueprint, IaC, fromDatabase, fromService, envVarGroups, previews, projects, environments.

    Also in 3 projects that use this

  • +10 more from aaronbrethorst

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 11 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use for Render deployment planning, render.yaml authoring, and Git-backed Blueprint handoff with a reproducible deploy path.

    line 9
  2. Very specific:

    Create or update a minimal render.yaml that keeps secrets unresolved and documents the actual build, start, and runtime requirements.

    line 14
  3. Very specific:

    If the Render CLI is available, run render blueprints validate.

    line 15
  4. Distinctive:

    Do not continue with a Blueprint flow if the repository is not pushed to a supported Git host.

    line 24
  5. Distinctive:

    Do not assume image-backed direct deploys, MCP automation, or pre-created infrastructure unless the current environment already exposes …

    line 25

“Common” is measured: kept by at least 6 in 10 of the 11 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Render Deploy

Intent

  • Use for Render deployment planning, render.yaml authoring, and Git-backed Blueprint handoff with a reproducible deploy path.

Default operating pattern

  1. Confirm the repository already has a pushed Git remote before designing the deploy flow; if not, stop and ask the user to push the repo first.
  2. Analyze the app shape and decide whether the Blueprint should include a web service, static site, worker, cron job, or supporting datastore.
  3. Create or update a minimal render.yaml that keeps secrets unresolved and documents the actual build, start, and runtime requirements.
  4. If the Render CLI is available, run render blueprints validate; otherwise, call out the missing validation step clearly instead of pretending it was checked.
  5. Convert the Git remote to an HTTPS URL if needed, then build the Blueprint deeplink as https://dashboard.render.com/blueprint/new?repo=<HTTPS_REPO_URL>.
  6. Return the deeplink and the next manual steps: push render.yaml, fill secrets, apply the Blueprint, and monitor the first deploy in Render.

Pack fit

  • Included in: deploy-ops
  • Favor the reproducible Blueprint path over host-specific automation or private deployment glue.

Boundary

  • Do not continue with a Blueprint flow if the repository is not pushed to a supported Git host.
  • Do not assume image-backed direct deploys, MCP automation, or pre-created infrastructure unless the current environment already exposes them.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free