autoresearch-agent
Skill4 starsChanged 7 months agoMITView on GitHub
Delegate autoresearch tasks to a headless Claude Code sub-agent process. Use when the current agent needs to run any autoresearch command (autoresearch, ship, plan, security, debug, fix, scenario, predict, learn) as an autonomous background or foreground subprocess via `claude --dangerously-skip-permissions -p`. Ideal for long-running autonomous loops, overnight improvement runs, CI/CD pipeline integration, and fire-and-forget shipping workflows. Triggers on: "run autoresearch in background", "headless autoresearch", "delegate autoresearch", "spawn autoresearch", "autoresearch sub-agent", "autoresearch agent", or any request to run autoresearch non-interactively.
We split this skill into the rules it gives an agent
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 41
Run directly when the result is needed immediately:
- Very specific: line 50
If agent-exec is available, prefer it for any run that may exceed 5 minutes.
- Very specific: line 68
Add --notify-file results.ndjson to get a completion event written when done.
- Very specific: line 113
If claude is not found, the script exits with a clear error message.
- Distinctive: line 114
If the autoresearch skill is not installed, claude will report an unknown command.
- Distinctive: line 116
If agent-exec is unavailable, fall back to direct foreground execution and warn the user that long runs will block.
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
autoresearch-agent
Spawn autoresearch as a headless Claude Code subprocess. The wrapper script
scripts/autoresearch translates CLI subcommands into
claude --dangerously-skip-permissions -p "/autoresearch:<sub> <flags>".
Prerequisites
claudeCLI in PATH (or setCLAUDE_BIN)- The autoresearch skill installed in the target project or globally
(
~/.claude/skills/autoresearch/)
Quick reference
# Foreground (blocks until done)
scripts/autoresearch ship --auto
# Background via agent-exec (preferred for long runs)
agent-exec run --timeout 3600000 -- scripts/autoresearch fix --guard "npm test"Execution modes
1. Foreground — short tasks (<5 min)
Run directly when the result is needed immediately:
scripts/autoresearch ship --checklist-only
scripts/autoresearch plan "Reduce bundle size"2. Background via agent-exec — long tasks (>5 min)
If agent-exec is available, prefer it for any run that may exceed 5 minutes.
This keeps the calling agent responsive.
# Launch
agent-exec run \
--cwd "$(pwd)" \
--timeout 7200000 \
-- scripts/autoresearch security --fail-on critical
# Check progress
agent-exec status <JOB_ID>
agent-exec tail --tail-lines 50 <JOB_ID>
# Wait for completion
agent-exec wait <JOB_ID>Add --notify-file results.ndjson to get a completion event written when done.
3. Dry-run — verify command before launch
scripts/autoresearch -n ship --auto
# prints: + claude --dangerously-skip-permissions -p '/autoresearch:ship --auto'Workflow
- Determine subcommand and flags from the user request
- Check estimated duration — short (<5 min) → foreground; long → agent-exec
- Verify prerequisites —
which claude, skill installed - Launch — foreground exec or
agent-exec run - Monitor (background only) —
agent-exec tail/status - Report results back to the user
Subcommands
See references/subcommands.md for the full subcommand table with flags.
| Subcommand | Typical duration | Recommended mode |
ship --auto | 2-10 min | foreground |
ship --checklist-only | <1 min | foreground |
plan | 1-3 min | foreground |
security | 10-60 min | agent-exec |
debug | 10-60 min | agent-exec |
fix | 5-30 min | agent-exec |
scenario | 5-30 min | agent-exec |
predict | 3-10 min | foreground or agent-exec |
learn | 5-30 min | agent-exec |
| (base loop) | unbounded | agent-exec with --timeout |
Environment variables
| Variable | Purpose | Default |
CLAUDE_BIN | Path to claude binary | claude |
CLAUDE_EXTRA_ARGS | Extra flags for claude (e.g. --model sonnet) | (empty) |
AUTORESEARCH_DRY_RUN | Set 1 to print command without executing | 0 |
Error handling
- If
claudeis not found, the script exits with a clear error message. - If the autoresearch skill is not installed, claude will report an unknown command. Fix: install the skill per the autoresearch README.
- If agent-exec is unavailable, fall back to direct foreground execution and warn the user that long runs will block.
Examples
# Ship a PR headlessly
scripts/autoresearch ship --auto
# Run 25 iterations of test coverage improvement in background
agent-exec run --timeout 3600000 \
-- scripts/autoresearch "Goal: coverage to 90%" --iterations 25
# Security audit with CI gate
agent-exec run --timeout 7200000 \
-- scripts/autoresearch security --fail-on critical --iterations 15
# Debug then fix pipeline
agent-exec run --timeout 1800000 \
-- scripts/autoresearch debug --scope "src/**/*.ts" --iterations 10
# ... after completion:
agent-exec run --timeout 1800000 \
-- scripts/autoresearch fix --from-debug --iterations 20Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- Hassaan146/claude-skills★ 18same name
- csiddhant796-blip/claude-skills-collection★ 2same name
- Hussain-Elfalah/Agentic-Skills★ 2same name
- mahiunfiltered/claude-code-skills★ 1same name
- Arnav-0/claude-code-setup★ 0same name
- vbrevik/claude_code_skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository25 other files it gives its agents.
- AGENTS.mdAGENTS.md
- greats-soul-archive-contributor/AGENTS.mdAGENTS.md
- agentic-cli-designSkill
- ai-chat-frontendSkill
- brainstorm-frameworksSkill
- business-planningSkill
- clawdbot-configSkill
- dashboard-design-guidebookSkill
- fermi-estimationSkill
- firecrawlSkill
- gogcliSkill
- greats-soul-archive-contributorSkill
- jp-grantsSkill
- openclaw-agent-creatorSkill
- opencode-agent-creatorSkill
- opencode-command-creatorSkill
- openspec-brownfield-baselineSkill
- oss-publishSkill
- product-improvement-proposalSkill
- python-uv-projectSkill
- rust-cliSkill
- slack-rsSkill
- unit-test-hygieneSkill
- wt-setupSkill
- youtube-summarizerSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

