Phase 4 — Run Without You (the recurring loop)
SkillCloud & infraThis skill takes your AI through the final step of turning a finished agent build into something that runs on its own. Once it is added, your AI can set the agent up as a recurring job on a schedule, a job that starts when an event happens, or one you confirm and run when needed, then wrap up the versioned roadmap.
Instructions available. Your AI can read the instructions. Execution depends on the setup they require.
Account requirements not reviewed. Check the skill instructions before use; ahel provides instructions and does not run this skill.
After adding it, tell your AI which finished agent build should run on its own and when — for example, say "run it every morning" or "put it on a schedule". Your AI will then guide the setup step by step.
Then ask your AI: use the Phase 4 skill
What your AI can do with it
- Put a finished agent build on a repeating schedule, such as every morning
- Set the agent to run automatically when a specific event happens
- Set up on-demand runs that you confirm before they start
- Finalize a versioned roadmap so the running setup has a clear record
- Walk through the final phase of turning a graded agent build into a hands-off deployment
What this skill tells your AI
The instructions your AI receives, as published by alirezarezvani/claude-skills in .gemini/skills/run-without-you/SKILL.md and read by ahel’s review.
A scheduled deployment fires a fresh session on a cron cadence — the agent runs without you. Each firing can carry its own outcome, nesting the bounded grade→iterate loop inside every recurring run.
See ../../references/loops-and-workflows.md.
Choose the trigger
| Answer | Shape | Tool |
|---|---|---|
| "every morning / weekly / nightly" | recurring cron deployment | deployment_builder.py + cron_validator.py |
| "when X happens" | event-driven curl (documented, not scheduled) | deployment_builder.py (message only) |
| "only when I ask" | on-demand (no deployment) | none — just re-send a user.message |
Workflow (recurring)
- Validate the schedule.
Invalid cron/timezone → exit 1. Read the DST note: wall-clock semantics mean spring-forward times are skipped and fall-back times fire twice — avoid 02:00–03:00 in DST zones if exactly-once matters.python3 scripts/cron_validator.py --cron "0 9 * * *" --timezone Europe/Berlin - Build the deployment payload.
python3 scripts/deployment_builder.py \ --sheet ./my-agent/build-sheet.json --agent-id agent_123 --env-id env_456 \ --nest-outcome --out ./my-agent/payloads/deployment.json--nest-outcomeincludes the rubric so each firing self-grades. The tool prints the BYOK curl to create it and to test it once with the manualrunendpoint before trusting the schedule. - Test before you trust. Fire one manual
run, read the verdict, only then leave the cron in place. Pin the agent version in the deployment once it passes. - Finalize the roadmap.
python3 scripts/next_directions_writer.py \ --sheet ./my-agent/build-sheet.json --loop-shape cron-loop --last-verdict satisfied --out-dir ./my-agent - Advance + hand to wrap-up.
goal_state.py set --phase wrap-up, then invoke thewrap-upskill.
Hard rules
- Test with a manual
runfirst. Never commit a schedule you haven't fired once. - Safety rails on by default.
always_askMCP,limitednetworking where you can,read_onlyuntrusted memory,max_iterationsper firing, workspace spend limit. There is no spend cap inside CMA. - DST is wall-clock. Surface the note; pick safe times.
- ≤1,000 deployments/org.
Forcing-question library (recommend + cite)
- "Cadence, event, or on-request?" Recommend: on-request v0 → cadence once graded. Cite: loops-and-workflows.md.
- "Should each firing self-grade?" Recommend: yes — nest the outcome. Cite: loops-and-workflows.md (nesting rule).
- "Which timezone, and is the time DST-safe?" Recommend: avoid 02:00–03:00 in DST zones. Cite: cma-primitives.md (wall-clock DST).
- "Did you fire one manual run first?" Recommend: always. Cite: this SKILL.
Tools
scripts/deployment_builder.py— POST /v1/deployments payload (+ test-run curl).scripts/cron_validator.py— 5-field cron + IANA tz + DST note.scripts/next_directions_writer.py— write/refresh NEXT-DIRECTIONS.md.
Signals
- GitHub stars
- 27k
- Forks
- 4k
- Last commit
- Aug 2026
Advanced
- Item type
- skill
- Key
run-without-you- Source
- github.com/alirezarezvani/claude-skills
github.com/alirezarezvani/claude-skills
Related picks
Skill · countbot-ai
The pick for Croncron-packs
Skill · profbernardoj
The pick for Cronwebhooks
Skill · nahid-sparktales
The pick for Webhooksadobe-webhooks-events
Skill · jeremylongshore
The pick for Webhooksfind-skills
Skill · vercel-labs
More in Cloud & infravercel-react-best-practices
Skill · vercel-labs
More in Cloud & infra