How do I install the Run Without You skill?

Run npx skillmds@latest add alirezarezvani/run-without-you in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Run Without You safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. Capability flags: executes scripts, makes network calls. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Run Without You?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Run Without You free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Run Without You?

Alireza Rezvani (@alirezarezvani) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Run Without You by alirezarezvani — Agent Skill

Name: Run Without You
Rating: 4.2 (5 reviews)
Author: Alireza Rezvani

Run Without You

Phase 4 of building a Claude Managed Agent — make it run without you. Turn a graded agent into a recurring scheduled deployment (POSIX-cron), an event-driven curl trigger, or confirmed on-demand use, then finalize the versioned roadmap. Use when the user says "run it every morning", "put it on a schedule", "nightly", "weekly", "automate this", "make it recurring", or when the orchestrator routes phase=run-without-you. deployment_builder.py builds the POST /v1/deployments payload (initial_events must include user.message; optionally nests a user.define_outcome so each firing self-grades); cron_validator.py validates the 5-field cron + IANA timezone and prints the wall-clock DST note; next_directions_writer.py writes NEXT-DIRECTIONS.md. No tool makes API calls — the deployment is created via BYOK curl. Distinct from grade-iterate (the in-session loop) and wrap-up (closeout).

Alireza Rezvani Updated Sep 8, 2026 20.4k repo stars

File contents

Phase 4 — Run Without You (the recurring loop)

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.
```
python3 scripts/cron_validator.py --cron "0 9 * * *" --timezone Europe/Berlin
```
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.
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-outcome includes the rubric so each firing self-grades. The tool prints the BYOK curl to create it and to test it once with the manual run endpoint 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 the wrap-up skill.

Hard rules

Test with a manual run first. Never commit a schedule you haven't fired once.
Safety rails on by default. always_ask MCP, limited networking where you can, read_only untrusted memory, max_iterations per 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.

---name: run-without-youdescription: Phase 4 of building a Claude Managed Agent — make it run without you. Turn a graded agent into a recurring scheduled deployment (POSIX-cron), an event-driven curl trigger, or confirmed on-demand use, then finalize the versioned roadmap. Use when the user says "run it every morning", "put it on a schedule", "nightly", "weekly", "automate this", "make it recurring", or when the orchestrator routes phase=run-without-you. deployment_builder.py builds the POST /v1/deployments payload (initial_events must include user.message; optionally nests a user.define_outcome so each firing self-grades); cron_validator.py validates the 5-field cron + IANA timezone and prints the wall-clock DST note; next_directions_writer.py writes NEXT-DIRECTIONS.md. No tool makes API calls — the deployment is created via BYOK curl. Distinct from grade-iterate (the in-session loop) and wrap-up (closeout).license: MIT---# Phase 4 — Run Without You (the recurring loop)A **scheduled deployment** fires a fresh session on a cron cadence — the agentruns without you. Each firing can carry its own outcome, nesting the boundedgrade→iterate loop inside every recurring run.See [`../../references/loops-and-workflows.md`](../../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)1. **Validate the schedule.** ```bash python3 scripts/cron_validator.py --cron "0 9 * * *" --timezone Europe/Berlin ``` 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.2. **Build the deployment payload.** ```bash 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-outcome` includes the rubric so **each firing self-grades**. The tool prints the BYOK curl to create it and to **test it once** with the manual `run` endpoint before trusting the schedule.3. **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.4. **Finalize the roadmap.** ```bash python3 scripts/next_directions_writer.py \ --sheet ./my-agent/build-sheet.json --loop-shape cron-loop --last-verdict satisfied --out-dir ./my-agent ```5. **Advance + hand to wrap-up.** `goal_state.py set --phase wrap-up`, then invoke the `wrap-up` skill.## Hard rules- **Test with a manual `run` first.** Never commit a schedule you haven't fired once.- **Safety rails on by default.** `always_ask` MCP, `limited` networking where you can, `read_only` untrusted memory, `max_iterations` per 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)1. "Cadence, event, or on-request?" *Recommend:* on-request v0 → cadence once graded. *Cite:* loops-and-workflows.md.2. "Should each firing self-grade?" *Recommend:* yes — nest the outcome. *Cite:* loops-and-workflows.md (nesting rule).3. "Which timezone, and is the time DST-safe?" *Recommend:* avoid 02:00–03:00 in DST zones. *Cite:* cma-primitives.md (wall-clock DST).4. "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.

Frequently asked questions