Skip to content

alirezarezvani/claude-skills / agent-launcher/skills/run-without-you

run-without-you

Verified

Use when a graded managed agent should run on a schedule, on an event trigger or on demand ('run it every morning'). Validates cron with cron_validator.py and builds the deployment with deployment_builder.py.

FileKindSize
README.mdmarkdown1.1 KB
SKILL.mdskill md3.6 KB
scripts/cron_validator.pyscript5.2 KB
scripts/deployment_builder.pyscript5.9 KB
scripts/next_directions_writer.pyscript3.9 KB
---
name: run-without-you
description: "Use when a graded managed agent should run on a schedule, on an event trigger or on demand ('run it every morning'). Validates cron with cron_validator.py and builds the deployment with deployment_builder.py."
license: MIT
metadata:
  version: 2.11.2
  author: Alireza Rezvani
  tags: [cma, deployment, cron, schedule, recurring, run-without-you, next-directions, dst]
  compatible_tools: [claude-code, codex-cli, cursor, antigravity, opencode, gemini-cli]
---

# 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.
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.
writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deploymentStars: 323kUpdated Claude CodeCodexVerifiedInstall
xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.Stars: 198kUpdated Claude CodeCodexVerifiedInstall
shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy.Stars: 119kUpdated Claude CodeCodexVerifiedInstall
childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release.Stars: 118kUpdated Claude CodeCodexVerifiedInstall