agent-launcher-orchest…
Use when a user wants to build, launch, grade, or schedule a Claude Managed Agent (CMA) in their own Anthropic account — "build me an agent", "launch this as a…
Start an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule.
$ npx -y skills add alirezarezvani/claude-skills --skill loop --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/loopContext preview
The summary Claude sees to decide when to auto-load this skill.
Start an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule.
name: "loop" description: "Start an autonomous experiment loop with user-selected interval (10min, 1h, daily, weekly, monthly). Uses CronCreate for scheduling. Use when the user runs /ar:loop or asks to run an autoresearch experiment continuously on a schedule." command: /ar:loop
Start a recurring experiment loop that runs at a user-selected interval.
/ar:loop engineering/api-speed # Start loop (prompts for interval) /ar:loop engineering/api-speed 10m # Every 10 minutes /ar:loop engineering/api-speed 1h # Every hour /ar:loop engineering/api-speed daily # Daily at ~9am /ar:loop engineering/api-speed weekly # Weekly on Monday ~9am /ar:loop engineering/api-speed monthly # Monthly on 1st ~9am /ar:loop stop engineering/api-speed # Stop an active loop
If no experiment specified, list experiments and let user pick.
If interval not provided as argument, present options:
Select loop interval: 1. Every 10 minutes (rapid — stay and watch) 2. Every hour (background — check back later) 3. Daily at ~9am (overnight experiments) 4. Weekly on Monday (long-running experiments) 5. Monthly on 1st (slow experiments)
Map to cron expressions:
| Interval | Cron Expression | Shorthand | |----------|----------------|-----------| | 10 minutes | `*/10 * * * *` | `10m` | | 1 hour | `7 * * * *` | `1h` | | Daily | `57 8 * * *` | `daily` | | Weekly | `57 8 * * 1` | `weekly` | | Monthly | `57 8 1 * *` | `monthly` |
Use `CronCreate` with this prompt (fill in the experiment details):
You are running autoresearch experiment "{domain}/{name}".
1. Read .autoresearch/{domain}/{name}/config.cfg for: target, evaluate_cmd, metric, metric_direction
2. Read .autoresearch/{domain}/{name}/program.md for strategy and constraints
3. Read .autoresearch/{domain}/{name}/results.tsv for experiment history
4. Run: git checkout autoresearch/{domain}/{name}
Then do exactly ONE iteration:
- Review results.tsv: what worked, what failed, what hasn't been tried
- Edit the target file with ONE change (strategy escalation based on run count)
- Commit: git add {target} && git commit -m "experiment: {description}"
- Evaluate: python {skill_path}/scripts/run_experiment.py --experiment {domain}/{name} --single
- Read the output (KEEP/DISCARD/CRASH)
Rules:
- ONE change per experiment
- NEVER modify the evaluator
- If 5 consecutive crashes in results.tsv, delete this cron job (CronDelete) and alert
- After every 10 experiments, update Strategy section of program.md
Current best metric: {read from results.tsv or "no baseline yet"}
Total experiments so far: {count from results.tsv}Write to `.autoresearch/{domain}/{name}/loop.json`:
{
"cron_id": "{id from CronCreate}",
"interval": "{user selection}",
"started": "{ISO timestamp}",
"experiment": "{domain}/{name}"
}Loop started for {domain}/{name}
Interval: {interval description}
Cron ID: {id}
Auto-expires: 3 days (CronCreate limit)
To check progress: /ar:ar-status
To stop the loop: /ar:loop stop {domain}/{name}
Note: Recurring jobs auto-expire after 3 days.
Run /ar:loop again to restart after expiry.When user runs `/ar:loop stop {experiment}`:
1. Read `.autoresearch/{domain}/{name}/loop.json` to get the cron ID 2. Call `CronDelete` with that ID 3. Delete `loop.json` 4. Confirm: "Loop stopped for {experiment}. {n} experiments completed."
388 production-ready Claude Code skills, plugins, and agent skills for 13 AI coding tools. The most comprehensive open-source library of Claude Code skills and agent plugins — also works with OpenAI Codex, Gemini CLI, Cursor, and 9 more coding agents.
Repo: alirezarezvani/claude-skills
Use when a user wants to build, launch, grade, or schedule a Claude Managed Agent (CMA) in their own Anthropic account — "build me an agent", "launch this as a…
Phase 3 of building a Claude Managed Agent — the bounded grade→iterate loop. Define a CMA outcome (a required markdown rubric graded by an isolated grader),…
Phase 1 of building a Claude Managed Agent — interview the founder about the one job the agent should do, then produce a build sheet (CMA primitives table +…
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…
Phase 2 of building a Claude Managed Agent — turn a validated build sheet into exact API payloads and a resumable BYOK curl launch script, then launch…
Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2…