[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75JXH708FQQYF9EXPP5AMA7":3,"skill-same:01M75JXH708FQQYF9EXPP5AMA7":59},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":28,"commitSha":29,"skillDirectory":30,"forksCount":31,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M75JXH708FQQYF9EXPP5AMA7","render-disks",null,"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.","zhongjingyun\u002Fcodex-plugins","zhongjingyun","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F29746390?v=4","01M75HD6KCBVW17ZTD8FGWNX3Z","01M75HD6MEP2SRDSHCVAHHVZXV",30,"MIT","https:\u002F\u002Fgithub.com\u002Fzhongjingyun\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-disks\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: render-disks\ndescription: >-\n  Attaches and manages persistent disks on Render services—mount paths, sizing,\n  snapshots, file transfers, and single-instance constraints. Use when the user\n  needs persistent storage, file uploads, a custom database on disk, CMS media\n  storage, or needs to understand why their service can't scale horizontally\n  or use zero-downtime deploys.\n  Trigger terms: persistent disk, disk, storage, mount path, sizeGB, SSD,\n  file uploads, snapshots, disk restore, ephemeral filesystem.\nlicense: MIT\ncompatibility: Render paid web services, private services, and background workers\nmetadata:\n  author: Render\n  version: \"1.0.0\"\n  category: storage\n---\n\n# Render Persistent Disks\n\nPersistent disks are high-performance SSDs you attach to a Render service to preserve filesystem changes across deploys and restarts. Without a disk, services have an **ephemeral filesystem**—all local file changes are lost on every deploy.\n\n## When to Use\n\n- Storing **file uploads**, CMS media, or user-generated content\n- Running a **self-managed database** (MySQL, MongoDB, ClickHouse) on Render\n- Deploying **stateful infrastructure** (Elasticsearch, Kafka, RabbitMQ, Mattermost)\n- Understanding **why scaling is blocked** or **zero-downtime deploys are disabled**\n- **Restoring data** from an automatic disk snapshot\n\nFor managed databases, prefer **Render Postgres** (render-postgres) or **Key Value** (render-keyvalue) over self-managed alternatives on disk.\n\n## Critical Constraints\n\nThese constraints affect architecture decisions. Understand them **before** attaching a disk:\n\n| Constraint | Impact |\n|------------|--------|\n| **Single instance only** | Cannot scale horizontally (`numInstances` must be 1, autoscaling not available) |\n| **No zero-downtime deploys** | Old instance stops before new instance starts (brief downtime on each deploy) |\n| **Runtime access only** | Disk is not available during `buildCommand` or `preDeployCommand` (those run on separate compute) |\n| **Not accessible from other services** | Only the attached service can read\u002Fwrite the disk |\n| **Not available on cron jobs** | Attach to a web service, private service, or background worker instead |\n| **Not available on one-off jobs** | One-off jobs run on separate compute without disk access |\n| **Can increase size, cannot decrease** | Start small and grow as needed |\n\n## Setup\n\n### Dashboard\n\n1. Go to your service's **Disks** page\n2. Set the **mount path** (absolute path where persistent data is stored)\n3. Choose a **size** in GB\n4. Click **Add disk** — triggers a new deploy\n\n### Blueprint\n\n```yaml\nservices:\n  - type: web\n    name: cms\n    runtime: node\n    plan: starter\n    region: oregon\n    buildCommand: npm ci && npm run build\n    startCommand: npm start\n    disk:\n      name: cms-data\n      mountPath: \u002Fvar\u002Fdata\n      sizeGB: 10\n```\n\n## Mount Path\n\nOnly files written **under the mount path** are preserved. Everything else remains ephemeral.\n\n| Runtime | Source code path | Example mount path |\n|---------|------------------|--------------------|\n| Node.js, Python, Ruby, Elixir, Rust | `\u002Fopt\u002Frender\u002Fproject\u002Fsrc` | `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads` |\n| Go | `\u002Fopt\u002Frender\u002Fproject\u002Fgo\u002Fsrc\u002Fgithub.com\u002F\u003Cuser>\u002F\u003Crepo>` | `...\u002Fdata` |\n| Docker | Dockerfile's `WORKDIR` (commonly `\u002Fapp`) | `\u002Fapp\u002Fstorage` |\n\n### Disallowed mount paths\n\nCannot mount at: `\u002F`, `\u002Fopt`, `\u002Fopt\u002Frender`, `\u002Fopt\u002Frender\u002Fproject`, `\u002Fopt\u002Frender\u002Fproject\u002Fsrc`, `\u002Fhome`, `\u002Fhome\u002Frender`, `\u002Fetc`, `\u002Fetc\u002Fsecrets`.\n\nSubdirectories of these paths are fine (e.g. `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads`).\n\n## Snapshots\n\n- Render creates an **automatic snapshot every 24 hours**\n- Snapshots are available for **at least 7 days**\n- Restore from the service's **Disks** page in the Dashboard\n- **Full restore only** — you cannot restore individual files\n- **Destructive** — all changes after the snapshot are lost\n\n**Do not restore snapshots for custom database recovery.** Use database-native backup tools (mysqldump, mongodump) instead—disk snapshots may capture a corrupted database state.\n\n## File Transfers\n\n### SCP (via SSH)\n\n```bash\n# Download from service\nscp -s YOUR_SERVICE@ssh.YOUR_REGION.render.com:\u002Fmount\u002Fpath\u002Ffile .\u002Flocal-file\n\n# Upload to service\nscp -s .\u002Flocal-file YOUR_SERVICE@ssh.YOUR_REGION.render.com:\u002Fmount\u002Fpath\u002Ffile\n```\n\nRequires SSH access enabled for the service.\n\n### Magic-Wormhole\n\nAvailable on all native runtimes (install manually on Docker):\n\n```bash\n# On the service shell\nwormhole send \u002Fmount\u002Fpath\u002Ffile\n\n# On your local machine\nwormhole receive\n```\n\n## Common Patterns\n\n| Pattern | Service type | Mount path | Notes |\n|---------|-------------|------------|-------|\n| WordPress \u002F Ghost \u002F CMS | Web Service | `\u002Fvar\u002Fdata` or `\u002Fapp\u002Fcontent` | Media uploads, SQLite |\n| Self-managed MySQL | Private Service | `\u002Fvar\u002Flib\u002Fmysql` | Use mysqldump for backups, not disk snapshots |\n| File upload API | Web Service | `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads` | Single instance constraint |\n| Elasticsearch | Private Service | `\u002Fusr\u002Fshare\u002Felasticsearch\u002Fdata` | Stateful search infrastructure |\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Expecting horizontal scaling with a disk | Not possible — disk services are single-instance only |\n| Mounting at a disallowed path | Use a subdirectory (e.g. `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads` not `\u002Fopt\u002Frender\u002Fproject\u002Fsrc`) |\n| Reading disk during build or pre-deploy | These run on separate compute — move logic to the start command |\n| Restoring disk snapshot for a database | Use database-native backups instead |\n| Starting with a large disk size | Start small — you can increase but never decrease |\n\n## References\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Fsizing-and-snapshots.md` | Sizing guidance, snapshot lifecycle, restore procedures, cost patterns |\n\n## Related Skills\n\n- **render-web-services** — Deploy lifecycle, health checks (disk disables zero-downtime)\n- **render-private-services** — Internal services with disks (Elasticsearch, MySQL)\n- **render-blueprints** — `disk` field reference in `render.yaml`\n- **render-postgres** — Managed database alternative (no disk management needed)\n","# Render Persistent Disks\n\nPersistent disks are high-performance SSDs you attach to a Render service to preserve filesystem changes across deploys and restarts. Without a disk, services have an **ephemeral filesystem**—all local file changes are lost on every deploy.\n\n## When to Use\n\n- Storing **file uploads**, CMS media, or user-generated content\n- Running a **self-managed database** (MySQL, MongoDB, ClickHouse) on Render\n- Deploying **stateful infrastructure** (Elasticsearch, Kafka, RabbitMQ, Mattermost)\n- Understanding **why scaling is blocked** or **zero-downtime deploys are disabled**\n- **Restoring data** from an automatic disk snapshot\n\nFor managed databases, prefer **Render Postgres** (render-postgres) or **Key Value** (render-keyvalue) over self-managed alternatives on disk.\n\n## Critical Constraints\n\nThese constraints affect architecture decisions. Understand them **before** attaching a disk:\n\n| Constraint | Impact |\n|------------|--------|\n| **Single instance only** | Cannot scale horizontally (`numInstances` must be 1, autoscaling not available) |\n| **No zero-downtime deploys** | Old instance stops before new instance starts (brief downtime on each deploy) |\n| **Runtime access only** | Disk is not available during `buildCommand` or `preDeployCommand` (those run on separate compute) |\n| **Not accessible from other services** | Only the attached service can read\u002Fwrite the disk |\n| **Not available on cron jobs** | Attach to a web service, private service, or background worker instead |\n| **Not available on one-off jobs** | One-off jobs run on separate compute without disk access |\n| **Can increase size, cannot decrease** | Start small and grow as needed |\n\n## Setup\n\n### Dashboard\n\n1. Go to your service's **Disks** page\n2. Set the **mount path** (absolute path where persistent data is stored)\n3. Choose a **size** in GB\n4. Click **Add disk** — triggers a new deploy\n\n### Blueprint\n\n```yaml\nservices:\n  - type: web\n    name: cms\n    runtime: node\n    plan: starter\n    region: oregon\n    buildCommand: npm ci && npm run build\n    startCommand: npm start\n    disk:\n      name: cms-data\n      mountPath: \u002Fvar\u002Fdata\n      sizeGB: 10\n```\n\n## Mount Path\n\nOnly files written **under the mount path** are preserved. Everything else remains ephemeral.\n\n| Runtime | Source code path | Example mount path |\n|---------|------------------|--------------------|\n| Node.js, Python, Ruby, Elixir, Rust | `\u002Fopt\u002Frender\u002Fproject\u002Fsrc` | `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads` |\n| Go | `\u002Fopt\u002Frender\u002Fproject\u002Fgo\u002Fsrc\u002Fgithub.com\u002F\u003Cuser>\u002F\u003Crepo>` | `...\u002Fdata` |\n| Docker | Dockerfile's `WORKDIR` (commonly `\u002Fapp`) | `\u002Fapp\u002Fstorage` |\n\n### Disallowed mount paths\n\nCannot mount at: `\u002F`, `\u002Fopt`, `\u002Fopt\u002Frender`, `\u002Fopt\u002Frender\u002Fproject`, `\u002Fopt\u002Frender\u002Fproject\u002Fsrc`, `\u002Fhome`, `\u002Fhome\u002Frender`, `\u002Fetc`, `\u002Fetc\u002Fsecrets`.\n\nSubdirectories of these paths are fine (e.g. `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads`).\n\n## Snapshots\n\n- Render creates an **automatic snapshot every 24 hours**\n- Snapshots are available for **at least 7 days**\n- Restore from the service's **Disks** page in the Dashboard\n- **Full restore only** — you cannot restore individual files\n- **Destructive** — all changes after the snapshot are lost\n\n**Do not restore snapshots for custom database recovery.** Use database-native backup tools (mysqldump, mongodump) instead—disk snapshots may capture a corrupted database state.\n\n## File Transfers\n\n### SCP (via SSH)\n\n```bash\n# Download from service\nscp -s YOUR_SERVICE@ssh.YOUR_REGION.render.com:\u002Fmount\u002Fpath\u002Ffile .\u002Flocal-file\n\n# Upload to service\nscp -s .\u002Flocal-file YOUR_SERVICE@ssh.YOUR_REGION.render.com:\u002Fmount\u002Fpath\u002Ffile\n```\n\nRequires SSH access enabled for the service.\n\n### Magic-Wormhole\n\nAvailable on all native runtimes (install manually on Docker):\n\n```bash\n# On the service shell\nwormhole send \u002Fmount\u002Fpath\u002Ffile\n\n# On your local machine\nwormhole receive\n```\n\n## Common Patterns\n\n| Pattern | Service type | Mount path | Notes |\n|---------|-------------|------------|-------|\n| WordPress \u002F Ghost \u002F CMS | Web Service | `\u002Fvar\u002Fdata` or `\u002Fapp\u002Fcontent` | Media uploads, SQLite |\n| Self-managed MySQL | Private Service | `\u002Fvar\u002Flib\u002Fmysql` | Use mysqldump for backups, not disk snapshots |\n| File upload API | Web Service | `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads` | Single instance constraint |\n| Elasticsearch | Private Service | `\u002Fusr\u002Fshare\u002Felasticsearch\u002Fdata` | Stateful search infrastructure |\n\n## Common Mistakes\n\n| Mistake | Fix |\n|---------|-----|\n| Expecting horizontal scaling with a disk | Not possible — disk services are single-instance only |\n| Mounting at a disallowed path | Use a subdirectory (e.g. `\u002Fopt\u002Frender\u002Fproject\u002Fsrc\u002Fuploads` not `\u002Fopt\u002Frender\u002Fproject\u002Fsrc`) |\n| Reading disk during build or pre-deploy | These run on separate compute — move logic to the start command |\n| Restoring disk snapshot for a database | Use database-native backups instead |\n| Starting with a large disk size | Start small — you can increase but never decrease |\n\n## References\n\n| Document | Contents |\n|----------|----------|\n| `references\u002Fsizing-and-snapshots.md` | Sizing guidance, snapshot lifecycle, restore procedures, cost patterns |\n\n## Related Skills\n\n- **render-web-services** — Deploy lifecycle, health checks (disk disables zero-downtime)\n- **render-private-services** — Internal services with disks (Elasticsearch, MySQL)\n- **render-blueprints** — `disk` field reference in `render.yaml`\n- **render-postgres** — Managed database alternative (no disk management needed)\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":27},{"author":24,"version":25,"category":26},"Render","1.0.0","storage","Render paid web services, private services, and background workers","main","67f0a2a774e0e57d841a7f3372c48e257f64c481","plugins\u002Frender\u002Fskills\u002Frender-disks",2,"https:\u002F\u002Fgithub.com\u002Fzhongjingyun\u002Fcodex-plugins","https:\u002F\u002Fgithub.com\u002Fzhongjingyun","2026-07-06 15:06:09",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add zhongjingyun\u002Fcodex-plugins --skill render-disks",{"tool":41,"command":42},"bunx","bunx skills add zhongjingyun\u002Fcodex-plugins --skill render-disks",{"tool":44,"command":45},"pnpm","pnpm dlx skills add zhongjingyun\u002Fcodex-plugins --skill render-disks","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzhongjingyun\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-disks\u002FSKILL.md",true,[49,55],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml","REFERENCE","参考文档",220,"https:\u002F\u002Fgithub.com\u002Fzhongjingyun\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-disks\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fsizing-and-snapshots.md",2167,"https:\u002F\u002Fgithub.com\u002Fzhongjingyun\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-disks\u002Freferences\u002Fsizing-and-snapshots.md",[60,69,76,84,91,98],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":64,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M75KA59Q22JVCRD3E955XW43","android-emulator-qa","Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzhongjingyun\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzhongjingyun\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":18},"01M75K6A00090T4DDE3QGJNE22","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002Fzhongjingyun\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":64,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M75K257HZ6ETNTAY5CEYB7JZ","sentry","Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.","https:\u002F\u002Fgithub.com\u002Fzhongjingyun\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzhongjingyun\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M75JZG6QHND8KRPRFV8BTFBG","render-workflows","Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.","https:\u002F\u002Fgithub.com\u002Fzhongjingyun\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M75JZCW206VJRSSASBHKEVZ3","render-web-services","Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.","https:\u002F\u002Fgithub.com\u002Fzhongjingyun\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M75JZ7W3CFG5M7TYK7F2V2F1","render-static-sites","Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React\u002FVue\u002FHugo\u002FGatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.","https:\u002F\u002Fgithub.com\u002Fzhongjingyun\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]