/ar:ar-resume — Resume Experiment
SkillAI & modelsThis skill lets your AI pick up a paused autoresearch experiment and continue it from where it stopped. Once added, your AI can return to the experiment's branch, read its results history, and keep iterating on the code-optimization work.
Available today. Use it from your connected AI after setup.
No other account needed.
After adding it, run /ar:ar-resume or simply ask your AI to pick up a previously started autoresearch experiment.
Then ask your AI: use the /ar:ar-resume — Resume Experiment skill
What your AI can do with it
- Resume a paused code-optimization experiment
- Switch back to the experiment's branch
- Read the experiment's results history
- Continue iterating from where the experiment left off
- Pick up a previously started autoresearch experiment when you ask
What this skill tells your AI
The instructions your AI receives, as published by alirezarezvani/claude-skills in .gemini/skills/ar-resume/SKILL.md and read by ahel’s review.
Resume a paused or context-limited experiment. Reads all history and continues where you left off.
Usage
/ar:ar-resume # List experiments, let user pick
/ar:ar-resume engineering/api-speed # Resume specific experiment
What It Does
Step 1: List experiments if needed
If no experiment specified:
python {skill_path}/scripts/setup_experiment.py --list
Show status for each (active/paused/done based on results.tsv age). Let user pick.
Step 2: Load full context
# Checkout the experiment branch
git checkout autoresearch/{domain}/{name}
# Read config
cat .autoresearch/{domain}/{name}/config.cfg
# Read strategy
cat .autoresearch/{domain}/{name}/program.md
# Read full results history
cat .autoresearch/{domain}/{name}/results.tsv
# Read recent git log for the branch
git log --oneline -20
Step 3: Report current state
Summarize for the user:
Resuming: engineering/api-speed
Target: src/api/search.py
Metric: p50_ms (lower is better)
Experiments: 23 total — 8 kept, 12 discarded, 3 crashed
Best: 185ms (-42% from baseline of 320ms)
Last experiment: "added response caching" → KEEP (185ms)
Recent patterns:
- Caching changes: 3 kept, 1 discarded (consistently helpful)
- Algorithm changes: 2 discarded, 1 crashed (high risk, low reward so far)
- I/O optimization: 2 kept (promising direction)
Step 4: Ask next action
How would you like to continue?
1. Single iteration (/ar:run) — I'll make one change and evaluate
2. Start a loop (/ar:loop) — Autonomous with scheduled interval
3. Just show me the results — I'll review and decide
If the user picks loop, hand off to /ar:loop with the experiment pre-selected.
If single, hand off to /ar:run.
Signals
- GitHub stars
- 26k
- Forks
- 4k
- Last commit
- Aug 2026
Advanced
- Catalog kind
- skill
- Gateway key
ar-resume- Source
- github.com/alirezarezvani/claude-skills