[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EDERPYB39J167J2YP4EV95":3,"skill-same:01M7EDERPYB39J167J2YP4EV95":67},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":34,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7EDERPYB39J167J2YP4EV95","render-cron-jobs",null,"在 Render 上用 cron job 服务配置并排查定时任务。当用户需要按计划运行任务、编写 cron 表达式、设置周期性任务、从 Heroku Scheduler 迁移、在 cron job 与后台 worker 之间做选择，或修复未触发的 cron 时使用。触发词:cron job、scheduled task、periodic job、cron expression、schedule、run every、timer、Heroku Scheduler migration。","kael-odin\u002Fcodex-plugins-zh","kael-odin","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F166499071?v=4","01M7EBHJT87XN88WT3PEQ8ZGZK","Kael Odin","01M7EBHJVC91GD7PGJN3ZB14SG",37,"MIT","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\r\nname: render-cron-jobs\ndescription: \"在 Render 上用 cron job 服务配置并排查定时任务。当用户需要按计划运行任务、编写 cron 表达式、设置周期性任务、从 Heroku Scheduler 迁移、在 cron job 与后台 worker 之间做选择，或修复未触发的 cron 时使用。触发词:cron job、scheduled task、periodic job、cron expression、schedule、run every、timer、Heroku Scheduler migration。\"\nlicense: MIT\ncompatibility: Render cron job services\nmetadata:\n  author: Render\n  version: \"1.0.0\"\n  category: compute\r\n---\r\n\r\n# Render Cron Jobs\r\n\r\nThis skill covers **Cron Job** services on Render: how schedules run, what the platform guarantees, and how they differ from workers and workflows. Pair it with Blueprint and deploy skills when authoring `render.yaml` or Dashboard settings.\r\n\r\n## When to Use\r\n\r\n- **Scheduled** work that **starts on a cron**, runs a command, and **exits** when finished\r\n- Choosing between **cron**, **background worker**, or **workflow** for periodic or long-running jobs\r\n- **Blueprint** fields for `type: cron`, `schedule`, and commands\r\n- **Constraints**: no disk, single concurrent run, 12-hour max duration, private-network **outbound** only\r\n- **UTC** scheduling pitfalls (expressions are **not** local time)\r\n\r\nExpression cheat sheets, framework `startCommand` examples, and Heroku Scheduler migration mapping live under `references\u002F`.\r\n\r\n## Configuration\r\n\r\n- **Schedule**: a **cron expression evaluated in UTC**, not the team’s local timezone. All times in the Dashboard and Blueprints are UTC.\r\n- **Command**: any valid **Linux shell command** or **bash script** path. The process must **exit** when work is done—**billing is based on run duration** (prorated by the second).\r\n- **Source**:\r\n  - **Git repository** — Render **builds on push** (same deploy model as other repo-backed services); the built artifact runs on each scheduled invocation.\r\n  - **Prebuilt Docker image** — the image is **pulled before each run** and is **not retained between runs** (no warm cache of the image layer set across invocations in the same way as a long-lived service).\r\n\r\n## Constraints\r\n\r\n- **No persistent disk** — cron job services **cannot** provision or attach Render persistent disks; plan for object storage or databases instead.\r\n- **Single-run guarantee** — at most **one active run** per cron service at a time. A new scheduled tick does not start a second overlapping instance.\r\n- **Maximum run length**: **12 hours** per invocation.\r\n- **Pricing**: **$1\u002Fmonth minimum** per cron job service; usage is **prorated by the second** beyond plan\u002Fminimum rules that apply to your account.\r\n- **Private network**: cron jobs **can send** traffic **to** other services on the private network; they **cannot receive** inbound private-network connections (no internal hostname for accepting traffic from other services).\r\n\r\n## Execution Behavior\r\n\r\n- **Manual “Trigger Run”** while a run is **active**: Render **cancels** the active run, then **starts** a new one.\r\n- **New Git build \u002F deploy** does **not** affect a run already **in progress**—the in-flight process keeps using the revision it started with until it exits.\r\n- **Docker-based crons**: the image is **pulled fresh for each run**; do not assume layer or image reuse across invocations like a continuously running container.\r\n- **UTC everywhere**: cron expressions and “midnight” in docs mean **UTC**. A common mistake is copying a local-time schedule into the expression without converting to UTC.\r\n\r\n## Cron vs Worker vs Workflow\r\n\r\n| Need | Use | Why |\r\n|------|-----|-----|\r\n| Periodic task **under 12h** | **Cron Job** | Scheduled, simple, exits when done |\r\n| **Continuous** job processing | **Background Worker** | Always running, polls a queue |\r\n| Periodic but **over 12h** | **Background Worker** | No 12h cron run ceiling |\r\n| **Scheduled parallel** compute | **Cron Job + Workflow** | Cron triggers workflow runs on a schedule; workflows fan out or orchestrate parallel steps |\r\n\r\n## Blueprint Configuration\r\n\r\nCron services use **`type: cron`** with a **`schedule`** and the usual build\u002Fstart and env wiring:\r\n\r\n```yaml\r\nservices:\r\n  - type: cron\r\n    name: nightly-cleanup\r\n    schedule: \"0 * * * *\" # hourly at minute 0 — must be quoted in YAML\r\n    buildCommand: pip install -r requirements.txt\r\n    startCommand: python cleanup.py\r\n    envVars:\r\n      - key: DATABASE_URL\r\n        fromDatabase:\r\n          name: my-db\r\n          property: connectionString\r\n```\r\n\r\n- **`schedule`**: standard five-field cron (`minute hour day-of-month month day-of-week`), **UTC**.\r\n- **`buildCommand`** \u002F **`startCommand`**: same roles as other non-Docker services; Docker images use image + start command as configured for image-backed crons.\r\n- **`envVars`**: same patterns as web services and workers (secrets, linked databases, etc.).\r\n\r\n**YAML note**: the `schedule` value **must be quoted** so characters like `*` are not parsed as YAML aliases or flow syntax.\r\n\r\n## Common Patterns\r\n\r\n- **Database cleanup** — archive or delete stale rows on a schedule\r\n- **Report generation** — build CSV\u002FPDF and upload to object storage or email\r\n- **External API sync** — pull or push batches on an interval\r\n- **Cache warming** — hit endpoints or rebuild caches before peak traffic\r\n- **Scheduled emails** — digest or reminder sends driven by cron + mail\u002FAPI\r\n\r\n## References\r\n\r\n| Topic | File |\r\n|--------|------|\r\n| Expression examples, framework commands, errors, env vars | `references\u002Fcron-patterns.md` |\r\n| Heroku Scheduler → Render mapping, blueprint example | `references\u002Fmigration-from-scheduler.md` |\r\n\r\n## Related Skills\r\n\r\n- **render-deploy** — First-time deploy, service creation, Dashboard flow\r\n- **render-blueprints** — Full `render.yaml` schema, previews, common mistakes\r\n- **render-background-workers** — Long-lived processes, queues, no 12h cap\r\n- **render-workflows** — Orchestrated and parallel jobs, often triggered on a schedule from cron\r\n","# Render Cron Jobs\r\n\r\nThis skill covers **Cron Job** services on Render: how schedules run, what the platform guarantees, and how they differ from workers and workflows. Pair it with Blueprint and deploy skills when authoring `render.yaml` or Dashboard settings.\r\n\r\n## When to Use\r\n\r\n- **Scheduled** work that **starts on a cron**, runs a command, and **exits** when finished\r\n- Choosing between **cron**, **background worker**, or **workflow** for periodic or long-running jobs\r\n- **Blueprint** fields for `type: cron`, `schedule`, and commands\r\n- **Constraints**: no disk, single concurrent run, 12-hour max duration, private-network **outbound** only\r\n- **UTC** scheduling pitfalls (expressions are **not** local time)\r\n\r\nExpression cheat sheets, framework `startCommand` examples, and Heroku Scheduler migration mapping live under `references\u002F`.\r\n\r\n## Configuration\r\n\r\n- **Schedule**: a **cron expression evaluated in UTC**, not the team’s local timezone. All times in the Dashboard and Blueprints are UTC.\r\n- **Command**: any valid **Linux shell command** or **bash script** path. The process must **exit** when work is done—**billing is based on run duration** (prorated by the second).\r\n- **Source**:\r\n  - **Git repository** — Render **builds on push** (same deploy model as other repo-backed services); the built artifact runs on each scheduled invocation.\r\n  - **Prebuilt Docker image** — the image is **pulled before each run** and is **not retained between runs** (no warm cache of the image layer set across invocations in the same way as a long-lived service).\r\n\r\n## Constraints\r\n\r\n- **No persistent disk** — cron job services **cannot** provision or attach Render persistent disks; plan for object storage or databases instead.\r\n- **Single-run guarantee** — at most **one active run** per cron service at a time. A new scheduled tick does not start a second overlapping instance.\r\n- **Maximum run length**: **12 hours** per invocation.\r\n- **Pricing**: **$1\u002Fmonth minimum** per cron job service; usage is **prorated by the second** beyond plan\u002Fminimum rules that apply to your account.\r\n- **Private network**: cron jobs **can send** traffic **to** other services on the private network; they **cannot receive** inbound private-network connections (no internal hostname for accepting traffic from other services).\r\n\r\n## Execution Behavior\r\n\r\n- **Manual “Trigger Run”** while a run is **active**: Render **cancels** the active run, then **starts** a new one.\r\n- **New Git build \u002F deploy** does **not** affect a run already **in progress**—the in-flight process keeps using the revision it started with until it exits.\r\n- **Docker-based crons**: the image is **pulled fresh for each run**; do not assume layer or image reuse across invocations like a continuously running container.\r\n- **UTC everywhere**: cron expressions and “midnight” in docs mean **UTC**. A common mistake is copying a local-time schedule into the expression without converting to UTC.\r\n\r\n## Cron vs Worker vs Workflow\r\n\r\n| Need | Use | Why |\r\n|------|-----|-----|\r\n| Periodic task **under 12h** | **Cron Job** | Scheduled, simple, exits when done |\r\n| **Continuous** job processing | **Background Worker** | Always running, polls a queue |\r\n| Periodic but **over 12h** | **Background Worker** | No 12h cron run ceiling |\r\n| **Scheduled parallel** compute | **Cron Job + Workflow** | Cron triggers workflow runs on a schedule; workflows fan out or orchestrate parallel steps |\r\n\r\n## Blueprint Configuration\r\n\r\nCron services use **`type: cron`** with a **`schedule`** and the usual build\u002Fstart and env wiring:\r\n\r\n```yaml\r\nservices:\r\n  - type: cron\r\n    name: nightly-cleanup\r\n    schedule: \"0 * * * *\" # hourly at minute 0 — must be quoted in YAML\r\n    buildCommand: pip install -r requirements.txt\r\n    startCommand: python cleanup.py\r\n    envVars:\r\n      - key: DATABASE_URL\r\n        fromDatabase:\r\n          name: my-db\r\n          property: connectionString\r\n```\r\n\r\n- **`schedule`**: standard five-field cron (`minute hour day-of-month month day-of-week`), **UTC**.\r\n- **`buildCommand`** \u002F **`startCommand`**: same roles as other non-Docker services; Docker images use image + start command as configured for image-backed crons.\r\n- **`envVars`**: same patterns as web services and workers (secrets, linked databases, etc.).\r\n\r\n**YAML note**: the `schedule` value **must be quoted** so characters like `*` are not parsed as YAML aliases or flow syntax.\r\n\r\n## Common Patterns\r\n\r\n- **Database cleanup** — archive or delete stale rows on a schedule\r\n- **Report generation** — build CSV\u002FPDF and upload to object storage or email\r\n- **External API sync** — pull or push batches on an interval\r\n- **Cache warming** — hit endpoints or rebuild caches before peak traffic\r\n- **Scheduled emails** — digest or reminder sends driven by cron + mail\u002FAPI\r\n\r\n## References\r\n\r\n| Topic | File |\r\n|--------|------|\r\n| Expression examples, framework commands, errors, env vars | `references\u002Fcron-patterns.md` |\r\n| Heroku Scheduler → Render mapping, blueprint example | `references\u002Fmigration-from-scheduler.md` |\r\n\r\n## Related Skills\r\n\r\n- **render-deploy** — First-time deploy, service creation, Dashboard flow\r\n- **render-blueprints** — Full `render.yaml` schema, previews, common mistakes\r\n- **render-background-workers** — Long-lived processes, queues, no 12h cap\r\n- **render-workflows** — Orchestrated and parallel jobs, often triggered on a schedule from cron\r\n",{"name":5,"license":15,"metadata":24,"description":7,"compatibility":28},{"author":25,"version":26,"category":27},"Render","1.0.0","compute","Render cron job services","main","e3091d1b371a9dcd9455d333175f948b286fdfcf","plugins\u002Frender\u002Fskills\u002Frender-cron-jobs",1,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh","https:\u002F\u002Fkael-odin.github.io\u002Fcodex-plugins-zh\u002F","https:\u002F\u002Fgithub.com\u002Fkael-odin","https:\u002F\u002Fkael-odin.github.io\u002Fodin-valhalla\u002F","Full-stack development • Open-source • System engineering\r\nTurning ideas into repositories.","2026-11-08 17:05:36",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add kael-odin\u002Fcodex-plugins-zh --skill render-cron-jobs",{"tool":45,"command":46},"bunx","bunx skills add kael-odin\u002Fcodex-plugins-zh --skill render-cron-jobs",{"tool":48,"command":49},"pnpm","pnpm dlx skills add kael-odin\u002Fcodex-plugins-zh --skill render-cron-jobs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs\u002FSKILL.md",true,[53,59,63],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"agents\u002Fopenai.yaml","REFERENCE","参考文档",214,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs\u002Fagents\u002Fopenai.yaml",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fcron-patterns.md",2787,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs\u002Freferences\u002Fcron-patterns.md",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fmigration-from-scheduler.md",2834,"https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs\u002Freferences\u002Fmigration-from-scheduler.md",[68,77,84,92,99,106],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EDVCKB89EF755PQMKV1BZA","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\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EDPX7WHN6HQZ0QKWB0BGVZ","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\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":72,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7EDHHD98T8ZH09F40Q973G3","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\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M7EDH3SGVMS1AFS6Q40B5J48","render-workflows","搭建、开发、测试和部署 Render Workflows。涵盖首次脚手架搭建（通过 CLI 或手动方式）、SDK 安装（Python 或 TypeScript）、任务模式（重试、子任务、扇出）、本地开发、控制台部署和故障排查。适用于用户首次搭建 Render Workflows、构建工作流服务、添加或修改工作流任务、本地测试工作流或部署到 Render 的场景。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":19},"01M7EDH0CYEKQ4VVARHZAQ43S8","render-web-services","配置 Render web service——端口绑定、TLS、健康检查、自定义域名、自动部署、PR 预览、持久化磁盘及部署生命周期。当用户需要搭建 web service、修复健康检查失败、添加自定义域名、配置零停机部署，或排查端口绑定问题时使用。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":19},"01M7EDGVDYFBG1CKSNMQ2DD336","render-static-sites","在 Render 全球 CDN 上部署并配置静态站点——构建命令、发布路径、SPA 路由、重定向、自定义 header 及 PR 预览。当用户需要部署静态站点、搭建 React\u002FVue\u002FHugo\u002FGatsby 前端、配置 SPA 回退路由、添加重定向规则、自定义响应 header，或在静态站点与 web service 之间为前端做选择时使用。触发词:static site、CDN、SPA、single-page app、React deploy、Vue deploy、Hugo、Gatsby、Docusaurus、Jekyll、staticPublishPath。","https:\u002F\u002Fgithub.com\u002Fkael-odin\u002Fcodex-plugins-zh\u002Fblob\u002Fmain\u002Fplugins\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]