Skills / Product and discovery / run-without-you

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).

alirezarezvaniIndexed from GitHubFor Founders

By alirezarezvani on GitHub, licence MIT. Redistributed unchanged with its licence and attribution, from the source at commit 19392f7, the version we scanned. The description is ours.

SecurityReview before userisk 16 of 100 · SkillSpector (static rules)
Rating—0 verified reviews
Uses this month00 installs
Job done—reported after each use

About this skill

Summary from the skill's own text
Use it whenA **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.
You provideSee the skill's instructions.
You receiveSee the skill's instructions.
It needsRuns 3 scripts: scripts/cron_validator.py, scripts/deployment_builder.py, scripts/next_directions_writer.py.
It won'tNot stated by the author.
Try asking“Use the run-without-you skill.”

What's inside

Every file in version 1.0.0, exactly as you will install it
Instructions 1Scripts 3References 37 files · 21.4 KB
Scripts can:Network access
SKILL.mdInstructions · 79 lines · 4.3 KB
medium · Skill declares no tool scope ('permissions' or 'allowed-tools') but code capabilities were detected: file_read, file_write, shell. · line 1
Without declared permissions the skill's intent is opaque and cannot be validated.

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](../../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.

  1. 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.

  1. 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.

  1. 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 ``

  1. 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.

  1. "Should each firing self-grade?" *Recommend:* yes — nest the outcome. *Cite:*

loops-and-workflows.md (nesting rule).

  1. "Which timezone, and is the time DST-safe?" *Recommend:* avoid 02:00–03:00 in

DST zones. *Cite:* cma-primitives.md (wall-clock DST).

  1. "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.

Reviews

Only from people who installed it

No reviews yet.