/ar:ar-resume — Resume Experiment
Resume a paused experiment.
How to use it
Claude Code
- Run the line below. It pulls the whole folder into
~/.claude/skills/ar-resume. - Describe your job in plain words. Claude Code follows the skill from there.
Claude Code — installs the whole folder, not just SKILL.md
npx degit alirezarezvani/claude-skills/engineering/autoresearch-agent/skills/ar-resume#main ~/.claude/skills/ar-resumeFor one project only, change the path to .claude/skills/ar-resume.
Claude (web or desktop app)
- On this page open ⋯ → Download .md.
- Save it as SKILL.md in a folder, zip the folder, then Customize → Skills → + → Create skill → Upload a skill.
- Pick the file and Save. Claude shows the name and description and runs a security scan.
- Check the skill is switched on.
- Start a new chat and describe your job in plain words. The AI follows the skill from there.
ChatGPT or another app
- ChatGPT: make a Project and paste it into Instructions.
- Neither? Paste it at the top of a new chat — it works for that chat.
Not working?
- Check which app you pasted it into — the steps above name the right one.
- Some skills need the paid tier of Claude or ChatGPT.
Paste into Claude, ChatGPT or Cursor.
Source of /ar:ar-resume — Resume Experiment
Show the full text78 lines
| name | description | command |
|---|---|---|
| ar-resume | Resume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:ar-resume or asks to pick up a previously started autoresearch experiment. | /ar:ar-resume |
/ar:ar-resume — Resume Experiment
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.
| 1 | |
| 2 | name "ar-resume" |
| 3 | description "Resume a paused experiment. Checkout the experiment branch, read results history, continue iterating. Use when the user runs /ar:ar-resume or asks to pick up a previously started autoresearch experiment." |
| 4 | command /ar:ar-resume |
| 5 | |
| 6 | |
| 7 | # /ar:ar-resume — Resume Experiment |
| 8 | |
| 9 | Resume a paused or context-limited experiment. Reads all history and continues where you left off. |
| 10 | |
| 11 | ## Usage |
| 12 | |
| 13 | |
| 14 | /ar:ar-resume # List experiments, let user pick |
| 15 | /ar:ar-resume engineering/api-speed # Resume specific experiment |
| 16 | |
| 17 | |
| 18 | ## What It Does |
| 19 | |
| 20 | ### Step 1: List experiments if needed |
| 21 | |
| 22 | If no experiment specified: |
| 23 | |
| 24 | |
| 25 | python {skill_path}/scripts/setup_experiment.py --list |
| 26 | |
| 27 | |
| 28 | Show status for each (active/paused/done based on results.tsv age). Let user pick. |
| 29 | |
| 30 | ### Step 2: Load full context |
| 31 | |
| 32 | |
| 33 | # Checkout the experiment branch |
| 34 | git checkout autoresearch/{domain}/{name} |
| 35 | |
| 36 | # Read config |
| 37 | cat .autoresearch/{domain}/{name}/config.cfg |
| 38 | |
| 39 | # Read strategy |
| 40 | cat .autoresearch/{domain}/{name}/program.md |
| 41 | |
| 42 | # Read full results history |
| 43 | cat .autoresearch/{domain}/{name}/results.tsv |
| 44 | |
| 45 | # Read recent git log for the branch |
| 46 | git log --oneline -20 |
| 47 | |
| 48 | |
| 49 | ### Step 3: Report current state |
| 50 | |
| 51 | Summarize for the user: |
| 52 | |
| 53 | |
| 54 | Resuming: engineering/api-speed |
| 55 | Target: src/api/search.py |
| 56 | Metric: p50_ms (lower is better) |
| 57 | Experiments: 23 total — 8 kept, 12 discarded, 3 crashed |
| 58 | Best: 185ms (-42% from baseline of 320ms) |
| 59 | Last experiment: "added response caching" → KEEP (185ms) |
| 60 | |
| 61 | Recent patterns: |
| 62 | - Caching changes: 3 kept, 1 discarded (consistently helpful) |
| 63 | - Algorithm changes: 2 discarded, 1 crashed (high risk, low reward so far) |
| 64 | - I/O optimization: 2 kept (promising direction) |
| 65 | |
| 66 | |
| 67 | ### Step 4: Ask next action |
| 68 | |
| 69 | |
| 70 | How would you like to continue? |
| 71 | 1. Single iteration (/ar:run) — I'll make one change and evaluate |
| 72 | 2. Start a loop (/ar:loop) — Autonomous with scheduled interval |
| 73 | 3. Just show me the results — I'll review and decide |
| 74 | |
| 75 | |
| 76 | If the user picks loop, hand off to `/ar:loop` with the experiment pre-selected. |
| 77 | If single, hand off to `/ar:run`. |
| 78 |
Discussion
Academic CV builderFormat CVs for academic positions with publications, grants, and teachingAct as a resume reviewerA prompt for reviewing resumes in the context of a specific job opening.Customizable job scannerFind 80%+ matching [job sector] roles posted within the specified window (default: last 14 days)Linkedin profile enhancingCan you help me craft a catchy headline for my LinkedIn profile that would help me get noticed by recruiters looking to fill a ${job_title:data engineer} in ${industry:data engineering}?
Browse more free Claude skills or everything in People & hiring.