render-deploy
Skill19 starsChanged 57 days agoMITView on GitHub
Deploy applications to Render by analyzing codebases, generating render.yaml Blueprints, and providing Dashboard deeplinks. Use when the user wants to deploy, host, publish, or set up their application on Render's cloud platform.
- Pipes a download into a shell
- Reads credentials
- Installs packages
- Commits and pushes
12 other projects use a version of this, 5 of them edited.
Adopted by
Most recently taken up by
- kushvinth/skillsword for word, first seen Oct 29, 2026
- davidanthonyn/claude-skillsword for word, first seen Oct 20, 2026
- render-oss/skillsedited, first seen Oct 13, 2026
- render-oss/render-plugin-claude-codeedited, first seen Oct 9, 2026
- VoDaiLocz/kilo-kit-mcpword for word, first seen Aug 21, 2026
- FuSheng-MG/Pi-Agent-skillsword for word, first seen Jul 24, 2026
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.
aaronbrethorstSkillrender-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
aaronbrethorstSkillrender-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
Other versions12 projects use a version of this.
Word for word · 6
- openai/skills★ 27k100% same
- VoDaiLocz/kilo-kit-mcp★ 27100% same
- FuSheng-MG/Pi-Agent-skills★ 1100% same
- davidanthonyn/claude-skills★ 0100% same
- kushvinth/skills★ 0100% same
- belentani7/manus-ai-skill-pack★ 0100% same
Edited · 5
- JetBrains/skills★ 38699% same
- render-oss/skills★ 10169% same
- aaronbrethorst/claude-skills★ 489% same
- render-oss/render-plugin-claude-code★ 169% same
- tutti-os/skills★ 099% same
Wrote their own version · 1
- hebertzhu/agent-foundry★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository87 other files it gives its agents.
- .agents/skills/vercel-optimize/AGENTS.mdAGENTS.md
- block-kitSkill
- cloudflare-deploySkill
- connect-recommendSkill
- connect-required-verification-informationSkill
- create-slack-appSkill
- deploy-to-vercelSkill
- gws-calendar-agendaSkill
- gws-calendar-insertSkill
- gws-calendarSkill
- gws-chat-sendSkill
- gws-chatSkill
- gws-docsSkill
- gws-docs-writeSkill
- gws-driveSkill
- gws-drive-uploadSkill
- gws-gmail-forwardSkill
- gws-gmail-readSkill
- gws-gmail-reply-allSkill
- gws-gmail-replySkill
- gws-gmail-sendSkill
- gws-gmailSkill
- gws-gmail-triageSkill
- gws-gmail-watchSkill
- gws-peopleSkill
- gws-sharedSkill
- gws-sheets-appendSkill
- gws-sheets-readSkill
- gws-sheetsSkill
- gws-tasksSkill
- gws-workflow-email-to-taskSkill
- gws-workflow-file-announceSkill
- gws-workflow-meeting-prepSkill
- gws-workflowSkill
- gws-workflow-standup-reportSkill
- gws-workflow-weekly-digestSkill
- linearSkill
- netlify-deploySkill
- notion-knowledge-captureSkill
- notion-meeting-intelligenceSkill
- notion-research-documentationSkill
- notion-spec-to-implementationSkill
- rampSkill
- sentry-android-sdkSkill
- sentry-browser-sdkSkill
- sentry-cloudflare-sdkSkill
- sentry-cocoa-sdkSkill
- sentry-create-alertSkill
- sentry-debug-issueSkill
- sentry-dotnet-sdkSkill
- sentry-elixir-sdkSkill
- sentry-fix-issuesSkill
- sentry-flutter-sdkSkill
- sentry-get-startedSkill
- sentry-go-sdkSkill
- sentry-nestjs-sdkSkill
- sentry-nextjs-sdkSkill
- sentry-node-sdkSkill
- sentry-php-sdkSkill
- sentry-python-sdkSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
58 rules. 24 are common, 12 are distinctive, and 22 are very specific to this project.
24
Common
Most of the 6 edited versions we read keep these.
12
Distinctive
This author's own choices. Worth a look.
22
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 12
Direct Creation: - Create services instantly via MCP tools
- Common: line 16
If there is no Git remote, stop and ask the user to either:
- Common: line 17
Create/push a Git remote (can be minimal if only the Blueprint is needed), or
- Common: line 18
Use the Render Dashboard/API to deploy a prebuilt Docker image (MCP cannot create image-backed services).
- Very specific: line 22
When sandboxing blocks the deployment network calls, rerun with sandbox_permissions=require_escalated.
- Very specific: line 29
Create a render.yaml Blueprint file
- Common: line 32
Create databases, cron jobs, or other Render resources
- Distinctive: line 36
Use this short prompt sequence before deep analysis to reduce friction:
- Common: line 37
Ask whether they want to deploy from a Git repo or a prebuilt Docker image.
- Very specific: line 51
If the user chooses a Docker image, guide them to the Render Dashboard image deploy flow or ask them to add a Git remote (so you can use a …
- Common: line 64
Use this decision rule by default unless the user requests a specific method.
- Common: line 68
No separate worker/cron services
- Common: line 69
No attached databases or Key Value
- Common: line 71
If this path fits and MCP isn't configured yet, stop and guide MCP setup before proceeding.
- Common: line 80
If unsure, ask a quick clarifying question, but default to Blueprint for safety.
- Common: line 84
When starting a deployment, verify these requirements in order:
- Very specific: line 88
If using Git-based methods (Blueprint or Direct Creation), the repo must be pushed to GitHub/GitLab/Bitbucket.
- Common: line 94
If no remote exists, stop and ask the user to create/push a remote or switch to Docker image deploy.
- Distinctive: line 103
If MCP tools are available, you can skip CLI installation for most operations.
- Distinctive: line 109
If not installed, offer to install:
- Very specific: line 115
If list_services() fails because MCP isn't configured, ask whether they want to set up MCP (preferred) or continue with the CLI fallback.
- Very specific: line 126
Add this to ~/.cursor/mcp.json (replace <YOUR_API_KEY>):
- Very specific: line 151
Add the MCP server with Claude Code (replace <YOUR_API_KEY>):
- Distinctive: line 172
Add the MCP server with the Codex CLI:
- Distinctive: line 181
If the user is on another AI app, direct them to the Render MCP docs for that tool's setup steps and install method.
- Distinctive: line 185
After MCP is configured, have the user set the active Render workspace with a prompt like:
- Distinctive: line 193
If MCP isn't available, use the CLI instead and verify you can access your account:
- Very specific: line 199
If render whoami fails or returns empty data, the CLI is not authenticated.
- Distinctive: line 201
If neither is configured, ask user which method they prefer:
- Distinctive: line 207
Verify the active workspace:
- Very specific: line 222
If user needs to switch workspaces, they must do so via Dashboard or CLI (render workspace set).
- Very specific: line 238
Create a render.yaml Blueprint file following the Blueprint specification.
- Very specific: line 243
Always use plan: free unless user specifies otherwise
- Very specific: line 246
Use appropriate service type: web, worker, cron, static, or pserv
- Common: line 247
Use appropriate runtime: references/runtimes.md
- Very specific: line 285
After creating render.yaml, always give the user a short, explicit checklist and run validation immediately when the CLI is available:
- Very specific: line 286
Authenticate (CLI): run render whoami -o json (if not logged in, run render login or set RENDER_API_KEY)
- Very specific: line 287
Validate (recommended): run render blueprints validate
- Common: line 288
If the CLI isn't installed, offer to install it and provide the command.
- Common: line 290
Open Dashboard: Use the Blueprint deeplink and complete Git OAuth if prompted
- Very specific: line 315
Ensure the render.yaml file is committed and pushed to your Git remote:
- Very specific: line 323
If there is no Git remote yet, stop here and guide the user to create a GitHub/GitLab/Bitbucket repo, add it as origin, and push before …
- Common: line 327
Verify the file is in your remote repository before proceeding to the next step.
- Very specific: line 359
CRITICAL: Ensure the user has merged and pushed the render.yaml file to their repository before clicking the deeplink.
- Distinctive: line 375
After the user deploys via Dashboard, verify everything is working.
- Very specific: line 381
Look for status: "live" to confirm successful deployment.
- Common: line 396
If errors are found, proceed to the Post-deploy verification and basic triage section below.
- Very specific: line 408
When you don't need a render.yaml file in your repo
- Common: line 428
Use the concise steps below, and refer to references/direct-creation.md for full MCP command examples and follow-on configuration.
- Common: line 431
Use references/codebase-analysis.md to determine runtime, build/start commands, env vars, and datastores.
- Common: line 434
Create the service (web or static) and any required databases or key-value stores.
- Common: line 436
If MCP returns an error about missing Git credentials or repo access, stop and guide the user to connect their Git provider in the Render …
- Distinctive: line 439
Add required env vars via MCP after creation.
- Common: line 444
Check deploy status, logs, and metrics.
- Distinctive: line 454
Keep this short and repeatable.
- Very specific: line 459
Verify required env vars and port binding (0.0.0.0:$PORT)
- Common: line 463
If the service fails to start or health checks time out, use the basic triage guide: references/troubleshooting-basics.md
- Very specific: line 470
If deployment fails due to network issues (timeouts, DNS errors, connection resets), rerun the deploy with escalated permissions (use …
“Common” is measured: kept by at least 6 in 10 of the 6 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.
Files
Deploy to Render
Render supports Git-backed services and prebuilt Docker image services.
This skill covers Git-backed flows:
- Blueprint Method - Generate render.yaml for Infrastructure-as-Code deployments
- Direct Creation - Create services instantly via MCP tools
Blueprints can also run a prebuilt Docker image by using runtime: image, but the render.yaml still must live in a Git repo.
If there is no Git remote, stop and ask the user to either:
- Create/push a Git remote (can be minimal if only the Blueprint is needed), or
- Use the Render Dashboard/API to deploy a prebuilt Docker image (MCP cannot create image-backed services).
Prerequisites
- When sandboxing blocks the deployment network calls, rerun with
sandbox_permissions=require_escalated. - The deployment might take a few minutes. Use appropriate timeout values.
When to Use This Skill
Activate this skill when users want to:
- Deploy an application to Render
- Create a render.yaml Blueprint file
- Set up Render deployment for their project
- Host or publish their application on Render's cloud platform
- Create databases, cron jobs, or other Render resources
Happy Path (New Users)
Use this short prompt sequence before deep analysis to reduce friction:
- Ask whether they want to deploy from a Git repo or a prebuilt Docker image.
- Ask whether Render should provision everything the app needs (based on what seems likely from the user's description) or only the app while they bring their own infra. If dependencies are unclear, ask a short follow-up to confirm whether they need a database, workers, cron, or other services.
Then proceed with the appropriate method below.
Choose Your Source Path
Git Repo Path: Required for both Blueprint and Direct Creation. The repo must be pushed to GitHub, GitLab, or Bitbucket.
Prebuilt Docker Image Path: Supported by Render via image-backed services. This is not supported by MCP; use the Dashboard/API. Ask for:
- Image URL (registry + tag)
- Registry auth (if private)
- Service type (web/worker) and port
If the user chooses a Docker image, guide them to the Render Dashboard image deploy flow or ask them to add a Git remote (so you can use a Blueprint with runtime: image).
Choose Your Deployment Method (Git Repo)
Both methods require a Git repository pushed to GitHub, GitLab, or Bitbucket. (If using runtime: image, the repo can be minimal and only contain render.yaml.)
| Method | Best For | Pros |
| Blueprint | Multi-service apps, IaC workflows | Version controlled, reproducible, supports complex setups |
| Direct Creation | Single services, quick deployments | Instant creation, no render.yaml file needed |
Method Selection Heuristic
Use this decision rule by default unless the user requests a specific method. Analyze the codebase first; only ask if deployment intent is unclear (e.g., DB, workers, cron).
Use Direct Creation (MCP) when ALL are true:
- Single service (one web app or one static site)
- No separate worker/cron services
- No attached databases or Key Value
- Simple env vars only (no shared env groups) If this path fits and MCP isn't configured yet, stop and guide MCP setup before proceeding.
Use Blueprint when ANY are true:
- Multiple services (web + worker, API + frontend, etc.)
- Databases, Redis/Key Value, or other datastores are required
- Cron jobs, background workers, or private services
- You want reproducible IaC or a render.yaml committed to the repo
- Monorepo or multi-env setup that needs consistent configuration
If unsure, ask a quick clarifying question, but default to Blueprint for safety. For a single service, strongly prefer Direct Creation via MCP and guide MCP setup if needed.
Prerequisites Check
When starting a deployment, verify these requirements in order:
1. Confirm Source Path (Git vs Docker)
If using Git-based methods (Blueprint or Direct Creation), the repo must be pushed to GitHub/GitLab/Bitbucket. Blueprints that reference a prebuilt image still require a Git repo with render.yaml.
git remote -v- If no remote exists, stop and ask the user to create/push a remote or switch to Docker image deploy.
2. Check MCP Tools Availability (Preferred for Single-Service)
MCP tools provide the best experience. Check if available by attempting:
list_services()If MCP tools are available, you can skip CLI installation for most operations.
3. Check Render CLI Installation (for Blueprint validation)
render --versionIf not installed, offer to install:
- macOS:
brew install render - Linux/macOS:
curl -fsSL https://raw.githubusercontent.com/render-oss/cli/main/bin/install.sh | sh
4. MCP Setup (if MCP isn't configured)
If list_services() fails because MCP isn't configured, ask whether they want to set up MCP (preferred) or continue with the CLI fallback. If they choose MCP, ask which AI tool they're using, then provide the matching instructions below. Always use their API key.
Cursor
Walk the user through these steps:
- Get a Render API key:
https://dashboard.render.com/u/*/settings#api-keys- Add this to
~/.cursor/mcp.json(replace<YOUR_API_KEY>):
{
"mcpServers": {
"render": {
"url": "https://mcp.render.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}- Restart Cursor, then retry
list_services().
Claude Code
Walk the user through these steps:
- Get a Render API key:
https://dashboard.render.com/u/*/settings#api-keys- Add the MCP server with Claude Code (replace
<YOUR_API_KEY>):
claude mcp add --transport http render https://mcp.render.com/mcp --header "Authorization: Bearer <YOUR_API_KEY>"- Restart Claude Code, then retry
list_services().
Codex
Walk the user through these steps:
- Get a Render API key:
https://dashboard.render.com/u/*/settings#api-keys- Set it in their shell:
export RENDER_API_KEY="<YOUR_API_KEY>"- Add the MCP server with the Codex CLI:
codex mcp add render --url https://mcp.render.com/mcp --bearer-token-env-var RENDER_API_KEY- Restart Codex, then retry
list_services().
Other Tools
If the user is on another AI app, direct them to the Render MCP docs for that tool's setup steps and install method.
Workspace Selection
After MCP is configured, have the user set the active Render workspace with a prompt like:
Set my Render workspace to [WORKSPACE_NAME]5. Check Authentication (CLI fallback only)
If MCP isn't available, use the CLI instead and verify you can access your account:
# Check if user is logged in (use -o json for non-interactive mode)
render whoami -o jsonIf render whoami fails or returns empty data, the CLI is not authenticated. The CLI won't always prompt automatically, so explicitly prompt the user to authenticate:
If neither is configured, ask user which method they prefer:
- API Key (CLI):
export RENDER_API_KEY="rnd_xxxxx"(Get from https://dashboard.render.com/u/*/settings#api-keys) - Login:
render login(Opens browser for OAuth)
6. Check Workspace Context
Verify the active workspace:
get_selected_workspace()Or via CLI:
render workspace current -o jsonTo list available workspaces:
list_workspaces()If user needs to switch workspaces, they must do so via Dashboard or CLI (render workspace set).
Once prerequisites are met, proceed with deployment workflow.
Method 1: Blueprint Deployment (Recommended for Complex Apps)
Blueprint Workflow
Step 1: Analyze Codebase
Analyze the codebase to determine framework/runtime, build and start commands, required env vars, datastores, and port binding. Use the detailed checklists in references/codebase-analysis.md.
Step 2: Generate render.yaml
Create a render.yaml Blueprint file following the Blueprint specification.
Complete specification: references/blueprint-spec.md
Key Points:
- Always use
plan: freeunless user specifies otherwise - Include ALL environment variables the app needs
- Mark secrets with
sync: false(user fills these in Dashboard) - Use appropriate service type:
web,worker,cron,static, orpserv - Use appropriate runtime: references/runtimes.md
Basic Structure:
services:
- type: web
name: my-app
runtime: node
plan: free
buildCommand: npm ci
startCommand: npm start
envVars:
- key: DATABASE_URL
fromDatabase:
name: postgres
property: connectionString
- key: JWT_SECRET
sync: false # User fills in Dashboard
databases:
- name: postgres
databaseName: myapp_db
plan: freeService Types:
web: HTTP services, APIs, web applications (publicly accessible)worker: Background job processors (not publicly accessible)cron: Scheduled tasks that run on a cron schedulestatic: Static sites (HTML/CSS/JS served via CDN)pserv: Private services (internal only, within same account)
Service type details: references/service-types.md Runtime options: references/runtimes.md Template examples: assets/
Step 2.5: Immediate Next Steps (Always Provide)
After creating render.yaml, always give the user a short, explicit checklist and run validation immediately when the CLI is available:
- Authenticate (CLI): run
render whoami -o json(if not logged in, runrender loginor setRENDER_API_KEY) - Validate (recommended): run
render blueprints validate- If the CLI isn't installed, offer to install it and provide the command.
- Commit + push:
git add render.yaml && git commit -m "Add Render deployment configuration" && git push origin main - Open Dashboard: Use the Blueprint deeplink and complete Git OAuth if prompted
- Fill secrets: Set env vars marked
sync: false - Deploy: Click "Apply" and monitor the deploy
Step 3: Validate Configuration
Validate the render.yaml file to catch errors before deployment. If the CLI is installed, run the commands directly; only prompt the user if the CLI is missing:
render whoami -o json # Ensure CLI is authenticated (won't always prompt)
render blueprints validateFix any validation errors before proceeding. Common issues:
- Missing required fields (
name,type,runtime) - Invalid runtime values
- Incorrect YAML syntax
- Invalid environment variable references
Configuration guide: references/configuration-guide.md
Step 4: Commit and Push
IMPORTANT: You must merge the render.yaml file into your repository before deploying.
Ensure the render.yaml file is committed and pushed to your Git remote:
git add render.yaml
git commit -m "Add Render deployment configuration"
git push origin mainIf there is no Git remote yet, stop here and guide the user to create a GitHub/GitLab/Bitbucket repo, add it as origin, and push before continuing.
Why this matters: The Dashboard deeplink will read the render.yaml from your repository. If the file isn't merged and pushed, Render won't find the configuration and deployment will fail.
Verify the file is in your remote repository before proceeding to the next step.
Step 5: Generate Deeplink
Get the Git repository URL:
git remote get-url originThis will return a URL from your Git provider. If the URL is SSH format, convert it to HTTPS:
| SSH Format | HTTPS Format |
git@github.com:user/repo.git | https://github.com/user/repo |
git@gitlab.com:user/repo.git | https://gitlab.com/user/repo |
git@bitbucket.org:user/repo.git | https://bitbucket.org/user/repo |
Conversion pattern: Replace git@<host>: with https://<host>/ and remove .git suffix.
Format the Dashboard deeplink using the HTTPS repository URL:
https://dashboard.render.com/blueprint/new?repo=<REPOSITORY_URL>Example:
https://dashboard.render.com/blueprint/new?repo=https://github.com/username/repo-nameStep 6: Guide User
CRITICAL: Ensure the user has merged and pushed the render.yaml file to their repository before clicking the deeplink. If the file isn't in the repository, Render cannot read the Blueprint configuration and deployment will fail.
Provide the deeplink to the user with these instructions:
- Verify render.yaml is merged - Confirm the file exists in your repository on GitHub/GitLab/Bitbucket
- Click the deeplink to open Render Dashboard
- Complete Git provider OAuth if prompted
- Name the Blueprint (or use default from render.yaml)
- Fill in secret environment variables (marked with
sync: false) - Review services and databases configuration
- Click "Apply" to deploy
The deployment will begin automatically. Users can monitor progress in the Render Dashboard.
Step 7: Verify Deployment
After the user deploys via Dashboard, verify everything is working.
Check deployment status via MCP:
list_deploys(serviceId: "<service-id>", limit: 1)Look for status: "live" to confirm successful deployment.
Check for runtime errors (wait 2-3 minutes after deploy):
list_logs(resource: ["<service-id>"], level: ["error"], limit: 20)Check service health metrics:
get_metrics(
resourceId: "<service-id>",
metricTypes: ["http_request_count", "cpu_usage", "memory_usage"]
)If errors are found, proceed to the Post-deploy verification and basic triage section below.
Method 2: Direct Service Creation (Quick Single-Service Deployments)
For simple deployments without Infrastructure-as-Code, create services directly via MCP tools.
When to Use Direct Creation
- Single web service or static site
- Quick prototypes or demos
- When you don't need a render.yaml file in your repo
- Adding databases or cron jobs to existing projects
Prerequisites for Direct Creation
Repository must be pushed to a Git provider. Render clones your repository to build and deploy services.
git remote -v # Verify remote exists
git push origin main # Ensure code is pushedSupported providers: GitHub, GitLab, Bitbucket
If no remote exists, stop and ask the user to create/push a remote or switch to Docker image deploy.
Note: MCP does not support creating image-backed services. Use the Dashboard/API for prebuilt Docker image deploys.
Direct Creation Workflow
Use the concise steps below, and refer to references/direct-creation.md for full MCP command examples and follow-on configuration.
Step 1: Analyze Codebase
Use references/codebase-analysis.md to determine runtime, build/start commands, env vars, and datastores.
Step 2: Create Resources via MCP
Create the service (web or static) and any required databases or key-value stores. See references/direct-creation.md.
If MCP returns an error about missing Git credentials or repo access, stop and guide the user to connect their Git provider in the Render Dashboard, then retry.
Step 3: Configure Environment Variables
Add required env vars via MCP after creation. See references/direct-creation.md.
Remind the user that secrets can be set in the Dashboard if they prefer not to pass them via MCP.
Step 4: Verify Deployment
Check deploy status, logs, and metrics. See references/direct-creation.md.
For service discovery, configuration details, quick commands, and common issues, see references/deployment-details.md.
Post-deploy verification and basic triage (All Methods)
Keep this short and repeatable. If any check fails, fix it before redeploying.
- Confirm the latest deploy is
liveand serving traffic - Hit the health endpoint (or root) and verify a 200 response
- Scan recent error logs for a clear failure signature
- Verify required env vars and port binding (
0.0.0.0:$PORT)
Detailed checklist and commands: references/post-deploy-checks.md
If the service fails to start or health checks time out, use the basic triage guide: references/troubleshooting-basics.md
Troubleshooting
Escalated Network Access
If deployment fails due to network issues (timeouts, DNS errors, connection resets), rerun the deploy with escalated permissions (use sandbox_permissions=require_escalated). The deploy requires escalated network access when sandbox networking blocks outbound requests.
Example guidance to the user:
The deploy needs escalated network access to deploy to Render. I can rerun the command with escalated permissions—want me to proceed?Optional: If you need deeper diagnostics (metrics/DB checks/error catalog), suggest installing the
render-debug skill. It is not required for the core deploy flow.
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
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.

