Cron scheduling lets you run background workers on a regular basis. These workers keep working even after you restart your session. You can set them up for tasks like security scanning or performance checks.
Choose a cron expression to control how often a worker runs. For example, every 15 minutes or every hour. The system remembers your schedule and runs the worker automatically.
This is best for monitoring and CI tasks that need to run nonstop. For active development, use a loop instead. Cron workers are built for persistence.
Global
mkdir -p ~/.claude/skills/cron-scheduleProject
mkdir -p .claude/skills/cron-scheduleSource Repository
Google Agents Cli Deploygoogle/agents-cli
Deploy Google ADK agents to Agent Runtime, Cloud Run, or GKE with CI/CD
Turborepovercel/turborepo
Speed up your monorepo builds with Turborepo's caching and parallel task runs
Expo Cicd Workflowsexpo/skills
Write and validate EAS workflow YAML files for Expo CI/CD automation
Golang Continuous Integrationsamber/cc-skills-golang
Automate testing linting security and releases for Go projects with GitHub Actions
Docker Expertsickn33/antigravity-awesome-skills
Optimize, secure, and deploy Docker containers like a pro with proven techniques
Multi Stage Dockerfilegithub/awesome-copilot
Create efficient, secure Docker images using multi-stage builds and best practices
Diagnose Ci Failureswarpdotdev/common-skills
Diagnose CI failures fast and get a clear fix plan without touching code
Github Actions Templateswshobson/agents
Create production-ready GitHub Actions workflows for automated testing and deployment