[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7E7RZ9P7GHVR25DKBKVGJ8C":3,"skill-same:01M7E7RZ9P7GHVR25DKBKVGJ8C":65},{"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":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M7E7RZ9P7GHVR25DKBKVGJ8C","render-cron-jobs",null,"Configures and troubleshoots scheduled tasks on Render using cron job services. Use when the user needs to run something on a schedule, write a cron expression, set up a periodic job, migrate from Heroku Scheduler, choose between cron jobs and background workers, or fix a cron that isn't firing. Trigger terms: cron job, scheduled task, periodic job, cron expression, schedule, run every, timer, Heroku Scheduler migration.","wxdwu\u002Fnew-api","wxdwu","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F80968397?v=4","01M7E6AEMB59N90BKXD77EC83D","Xudong Wu","01M7E6AEMY2BXCDVZ9MJJHFQ4C",0,"MIT","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: render-cron-jobs\ndescription: >-\n  Configures and troubleshoots scheduled tasks on Render using cron job\n  services. Use when the user needs to run something on a schedule, write a\n  cron expression, set up a periodic job, migrate from Heroku Scheduler,\n  choose between cron jobs and background workers, or fix a cron that isn't\n  firing.\n  Trigger terms: cron job, scheduled task, periodic job, cron expression,\n  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\n---\n\n# Render Cron Jobs\n\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.\n\n## When to Use\n\n- **Scheduled** work that **starts on a cron**, runs a command, and **exits** when finished\n- Choosing between **cron**, **background worker**, or **workflow** for periodic or long-running jobs\n- **Blueprint** fields for `type: cron`, `schedule`, and commands\n- **Constraints**: no disk, single concurrent run, 12-hour max duration, private-network **outbound** only\n- **UTC** scheduling pitfalls (expressions are **not** local time)\n\nExpression cheat sheets, framework `startCommand` examples, and Heroku Scheduler migration mapping live under `references\u002F`.\n\n## Configuration\n\n- **Schedule**: a **cron expression evaluated in UTC**, not the team’s local timezone. All times in the Dashboard and Blueprints are UTC.\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).\n- **Source**:\n  - **Git repository** — Render **builds on push** (same deploy model as other repo-backed services); the built artifact runs on each scheduled invocation.\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).\n\n## Constraints\n\n- **No persistent disk** — cron job services **cannot** provision or attach Render persistent disks; plan for object storage or databases instead.\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.\n- **Maximum run length**: **12 hours** per invocation.\n- **Pricing**: **$1\u002Fmonth minimum** per cron job service; usage is **prorated by the second** beyond plan\u002Fminimum rules that apply to your account.\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).\n\n## Execution Behavior\n\n- **Manual “Trigger Run”** while a run is **active**: Render **cancels** the active run, then **starts** a new one.\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.\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.\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.\n\n## Cron vs Worker vs Workflow\n\n| Need | Use | Why |\n|------|-----|-----|\n| Periodic task **under 12h** | **Cron Job** | Scheduled, simple, exits when done |\n| **Continuous** job processing | **Background Worker** | Always running, polls a queue |\n| Periodic but **over 12h** | **Background Worker** | No 12h cron run ceiling |\n| **Scheduled parallel** compute | **Cron Job + Workflow** | Cron triggers workflow runs on a schedule; workflows fan out or orchestrate parallel steps |\n\n## Blueprint Configuration\n\nCron services use **`type: cron`** with a **`schedule`** and the usual build\u002Fstart and env wiring:\n\n```yaml\nservices:\n  - type: cron\n    name: nightly-cleanup\n    schedule: \"0 * * * *\" # hourly at minute 0 — must be quoted in YAML\n    buildCommand: pip install -r requirements.txt\n    startCommand: python cleanup.py\n    envVars:\n      - key: DATABASE_URL\n        fromDatabase:\n          name: my-db\n          property: connectionString\n```\n\n- **`schedule`**: standard five-field cron (`minute hour day-of-month month day-of-week`), **UTC**.\n- **`buildCommand`** \u002F **`startCommand`**: same roles as other non-Docker services; Docker images use image + start command as configured for image-backed crons.\n- **`envVars`**: same patterns as web services and workers (secrets, linked databases, etc.).\n\n**YAML note**: the `schedule` value **must be quoted** so characters like `*` are not parsed as YAML aliases or flow syntax.\n\n## Common Patterns\n\n- **Database cleanup** — archive or delete stale rows on a schedule\n- **Report generation** — build CSV\u002FPDF and upload to object storage or email\n- **External API sync** — pull or push batches on an interval\n- **Cache warming** — hit endpoints or rebuild caches before peak traffic\n- **Scheduled emails** — digest or reminder sends driven by cron + mail\u002FAPI\n\n## References\n\n| Topic | File |\n|--------|------|\n| Expression examples, framework commands, errors, env vars | `references\u002Fcron-patterns.md` |\n| Heroku Scheduler → Render mapping, blueprint example | `references\u002Fmigration-from-scheduler.md` |\n\n## Related Skills\n\n- **render-deploy** — First-time deploy, service creation, Dashboard flow\n- **render-blueprints** — Full `render.yaml` schema, previews, common mistakes\n- **render-background-workers** — Long-lived processes, queues, no 12h cap\n- **render-workflows** — Orchestrated and parallel jobs, often triggered on a schedule from cron\n","# Render Cron Jobs\n\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.\n\n## When to Use\n\n- **Scheduled** work that **starts on a cron**, runs a command, and **exits** when finished\n- Choosing between **cron**, **background worker**, or **workflow** for periodic or long-running jobs\n- **Blueprint** fields for `type: cron`, `schedule`, and commands\n- **Constraints**: no disk, single concurrent run, 12-hour max duration, private-network **outbound** only\n- **UTC** scheduling pitfalls (expressions are **not** local time)\n\nExpression cheat sheets, framework `startCommand` examples, and Heroku Scheduler migration mapping live under `references\u002F`.\n\n## Configuration\n\n- **Schedule**: a **cron expression evaluated in UTC**, not the team’s local timezone. All times in the Dashboard and Blueprints are UTC.\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).\n- **Source**:\n  - **Git repository** — Render **builds on push** (same deploy model as other repo-backed services); the built artifact runs on each scheduled invocation.\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).\n\n## Constraints\n\n- **No persistent disk** — cron job services **cannot** provision or attach Render persistent disks; plan for object storage or databases instead.\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.\n- **Maximum run length**: **12 hours** per invocation.\n- **Pricing**: **$1\u002Fmonth minimum** per cron job service; usage is **prorated by the second** beyond plan\u002Fminimum rules that apply to your account.\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).\n\n## Execution Behavior\n\n- **Manual “Trigger Run”** while a run is **active**: Render **cancels** the active run, then **starts** a new one.\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.\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.\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.\n\n## Cron vs Worker vs Workflow\n\n| Need | Use | Why |\n|------|-----|-----|\n| Periodic task **under 12h** | **Cron Job** | Scheduled, simple, exits when done |\n| **Continuous** job processing | **Background Worker** | Always running, polls a queue |\n| Periodic but **over 12h** | **Background Worker** | No 12h cron run ceiling |\n| **Scheduled parallel** compute | **Cron Job + Workflow** | Cron triggers workflow runs on a schedule; workflows fan out or orchestrate parallel steps |\n\n## Blueprint Configuration\n\nCron services use **`type: cron`** with a **`schedule`** and the usual build\u002Fstart and env wiring:\n\n```yaml\nservices:\n  - type: cron\n    name: nightly-cleanup\n    schedule: \"0 * * * *\" # hourly at minute 0 — must be quoted in YAML\n    buildCommand: pip install -r requirements.txt\n    startCommand: python cleanup.py\n    envVars:\n      - key: DATABASE_URL\n        fromDatabase:\n          name: my-db\n          property: connectionString\n```\n\n- **`schedule`**: standard five-field cron (`minute hour day-of-month month day-of-week`), **UTC**.\n- **`buildCommand`** \u002F **`startCommand`**: same roles as other non-Docker services; Docker images use image + start command as configured for image-backed crons.\n- **`envVars`**: same patterns as web services and workers (secrets, linked databases, etc.).\n\n**YAML note**: the `schedule` value **must be quoted** so characters like `*` are not parsed as YAML aliases or flow syntax.\n\n## Common Patterns\n\n- **Database cleanup** — archive or delete stale rows on a schedule\n- **Report generation** — build CSV\u002FPDF and upload to object storage or email\n- **External API sync** — pull or push batches on an interval\n- **Cache warming** — hit endpoints or rebuild caches before peak traffic\n- **Scheduled emails** — digest or reminder sends driven by cron + mail\u002FAPI\n\n## References\n\n| Topic | File |\n|--------|------|\n| Expression examples, framework commands, errors, env vars | `references\u002Fcron-patterns.md` |\n| Heroku Scheduler → Render mapping, blueprint example | `references\u002Fmigration-from-scheduler.md` |\n\n## Related Skills\n\n- **render-deploy** — First-time deploy, service creation, Dashboard flow\n- **render-blueprints** — Full `render.yaml` schema, previews, common mistakes\n- **render-background-workers** — Long-lived processes, queues, no 12h cap\n- **render-workflows** — Orchestrated and parallel jobs, often triggered on a schedule from cron\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","dde9a06ab10bce3fe52058c783826590231f7df3","plugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api","https:\u002F\u002Fgithub.com\u002Fwxdwu","24120128@bjtu.edu.cn","I am Xudong Wu，a student in beijing jiaotong University, \"I am eager to learn on GitHub and contribute my part to this community.","2026-10-05 17:26:50",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add wxdwu\u002Fnew-api --skill render-cron-jobs",{"tool":43,"command":44},"bunx","bunx skills add wxdwu\u002Fnew-api --skill render-cron-jobs",{"tool":46,"command":47},"pnpm","pnpm dlx skills add wxdwu\u002Fnew-api --skill render-cron-jobs","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs\u002FSKILL.md",true,[51,57,61],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"agents\u002Fopenai.yaml","REFERENCE","参考文档",210,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs\u002Fagents\u002Fopenai.yaml",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"references\u002Fcron-patterns.md",2674,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs\u002Freferences\u002Fcron-patterns.md",{"path":62,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":63,"sourceHtmlUrl":64},"references\u002Fmigration-from-scheduler.md",2749,"https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Frender\u002Fskills\u002Frender-cron-jobs\u002Freferences\u002Fmigration-from-scheduler.md",[66,74,81,88,95,102],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M7E8SVA2N0JA09RW1XJYXCWX","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","AGPL-3.0","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzotero\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M7E8ST1FJAD5PWTW2FN1NSK0","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M7E8SRW074NNNCZRCZA5T3Z1","setup-zoom-websockets","Use when building Zoom WebSockets.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fwebsockets\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M7E8SPCFMD3YVPRX2MW8X3RA","setup-zoom-webhooks","Use when building Zoom webhooks.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fwebhooks\u002FSKILL.md",[],[],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":19},"01M7E8SMCH4RPCX8YSBNGWQCMP","zoom-virtual-agent-web","Zoom Virtual Agent SDK for web embeds. Use for campaign or entry ID chat launch, event-driven controls, user context updates, and CSP-safe deployment.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fvirtual-agent\u002Fweb\u002FSKILL.md",[],[],{"skillNo":103,"name":104,"nameZh":6,"description":105,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":70,"licenseFileUrl":6,"sourceHtmlUrl":106,"categories":107,"keywords":108,"publishedAt":19},"01M7E8SJCAY323E36Z8SAP8H4M","zoom-virtual-agent-ios","Zoom Virtual Agent iOS integration via WKWebView. Use for Swift\u002FObjective-C script injection, message handlers, support_handoff relay, and URL routing policies.","https:\u002F\u002Fgithub.com\u002Fwxdwu\u002Fnew-api\u002Fblob\u002Fmain\u002Fplugins\u002F.tmp\u002Fplugins\u002Fplugins\u002Fzoom\u002Fskills\u002Fvirtual-agent\u002Fios\u002FSKILL.md",[],[]]