Download for MacApple silicon, macOS 14+
Skill

render-disks

@render-oss Updated 2026-10-13

Attaches and manages persistent disks on Render services—mount paths, sizing, snapshots, file transfers, and single-instance constraints. Use when the user needs persistent storage, file uploads, a custom database on disk, CMS media storage, or needs to understand why their service can't scale horizontally or use zero-downtime deploys. Trigger terms: persistent disk, disk, storage, mount path, sizeGB, SSD, file uploads, snapshots, disk restore, ephemeral filesystem.

Install

With your agent

Install OMGSkills skill "render-oss/render-plugin-claude-code:skills/render-disks" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.

Manual command

git clone https://github.com/render-oss/render-plugin-claude-code /tmp/render-plugin-claude-code && ln -s /tmp/render-plugin-claude-code/skills/render-disks ~/.claude/skills/render-disks

From README

Render Persistent Disks Persistent disks preserve files written beneath a service's configured mount path across deploys and restarts. Before designing, configuring, resizing, transferring data to, snapshotting, restoring, or troubleshooting a disk, read references/persistent-disks.md. When to Use Storing file uploads, CMS media, or user-generated content Running a self-managed database (MySQL, MongoDB, ClickHouse) on Render Deploying stateful infrastructure (Elasticsearch, Kafka, RabbitMQ, Mattermost) Understanding why scaling is blocked or zero-downtime deploys are disabled Restoring data from a disk snapshot For managed databases, prefer Render Postgres (render-postgres) or Key Value (render-keyvalue) over self-managed alternatives on disk. Core Decisions Render's default filesystem is ephemeral. Only files written beneath a disk's mount path persist across deploys and restarts. A disk-backed service is single-instance: it cannot use horizontal scaling or zero-downtime deploys.