ablation-planner
Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission.
Full end-to-end research pipeline: from a broad research direction through idea discovery, experiments, and review all the way to a polished paper PDF. Use when user says \"全流程\", \"full pipeline\", \"从找idea到投稿\", \"end-to-end research\", or wants the complete autonomous
Claude Code
$ npx -y skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill research-pipeline --agent claude-code
Codex
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill research-pipeline -a codex -y
Cursor
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill research-pipeline -a cursor -y
Gemini CLI
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill research-pipeline -a gemini-cli -y
GitHub Copilot
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill research-pipeline -a github-copilot -y
OpenCode
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill research-pipeline -a opencode -y
Windsurf
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill research-pipeline -a windsurf -y
name: research-pipeline description: "Full end-to-end research pipeline: from a broad research direction through idea discovery, experiments, and review all the way to a polished paper PDF. Use when user says \"全流程\", \"full pipeline\", \"从找idea到投稿\", \"end-to-end research\", or wants the complete autonomous research lifecycle." argument-hint: "[research-direction] [— resume <run_id>]" allowed-tools: Bash(*), Read, Write, Edit, Grep, Glob, WebSearch, WebFetch, Skill, mcp__codex__codex, mcp__codex__codex-reply
> **Before each reviewer slot**, follow [Selectable Reviewers](../shared-references/reviewer-backends.md): > resolve invocation → `.aris/reviewer.json` → Claude Code default (Codex MCP) > with `reviewer_route.py` through the canonical helper resolver, preserving this > slot's tier, fresh contexts, source/image inputs and deterministic gates. > Codex examples/pins below apply only to `backend=codex`; other routes use their > own first-call/reply contract. Save the route and actual returned identity; > unavailable selections are `REVIEW_UNAVAILABLE`. Classify acceptance from actual > families/completion/scope. Forward invocation reviewer/model/effort overrides > to reviewer-bearing children. Generation workers are unchanged.
> ⏱ **External cadence: non-judgmental heartbeat only.** An overnight `/loop` / > `CronCreate` heartbeat may wake, detect a **stalled** phase (no progress, dead > process, blocked on a freed resource) and **nudge** it forward — it may NEVER > decide the work is good (paper good enough, proof holds, claim supported). > Every such verdict stays on its own skill's internal cadence and terminates in > the cross-model jury. A heartbeat may say "keep going," never "good enough." > See > [`shared-references/external-cadence.md`](../shared-references/external-cadence.md) > (overnight-pipeline rule + stall detection & forced structural pivot). At heartbeat > startup, touch the run state first each tick and register this run with the watchdog > `loop` type (so a silent death surfaces as STALE); unregister on completion. The > watchdog only detects — it never acquits. Each tick also record the new-finding count > via the `iteration_log.py` helper (resolve through the canonical > `.aris/tools → tools → $ARIS_REPO/tools → $ARIS_REPO/tools via ~/.aris/repo` > chain, integration-contract §2; warn-and-skip if unresolved): > `python3 "$ITER_LOG" note <root> <run_id> <phase> <n>`. On the returned > `pivot=structural` (stale ≥ 2) the nudge must change a STRUCTURAL constraint and pick an > untried direction; on `pivot=human` (stale ≥ 4) flag for attention. Counting only — > never a quality verdict.
End-to-end autonomous research workflow for: **$ARGUMENTS**
Before creating an experimental run, route theorem-centered requests for Lean to [`/lean-formalize`](../lean-formalize/SKILL.md) and report its actual proof result. Run the experimental stages below when the task includes empirical research. In a mixed project, use Lean for a user-requested formal proof or a specific mathematical obligation whose formal verification would materially help; return its checked scope and remaining obligations to the research summary and applicable proof audit. Ordinary mathematics stays in the existing theory skills. Difficulty alone does not make Lean mandatory, and a formal sublemma does not establish an empirical claim.
· · · · · · · · 💬 Join Community · 🌱 ARIS is a methodology, not a platform. What matters is the research workflow — take it wherever you go.
Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission.
Quick single-paper lookup via AlphaXiv LLM-optimized summaries with tiered source fallback. Use when user says "explain this…
Analyze ML experiment results, compute statistics, generate comparison tables and insights. Use when user says "analyze results",…
Search, download, and summarize academic papers from arXiv. Use when user says "search arxiv", "download paper", "fetch arxiv",…
Autonomously improve a generated paper via GPT-6-Astra xhigh review → implement fixes → recompile, for 2 rounds. Use when user…
Autonomous research review loop using any OpenAI-compatible LLM API. Configure via llm-chat MCP server or environment variables.…
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…