Turn a refined research proposal or method idea into a detailed, claim-driven experiment roadmap. Use after `research-refine`, or when the user asks for a detailed experiment plan, ablation matrix, evaluation protocol, run order, compute budget, or paper-ready validation that supports the core problem, novelty, simplicity, and any LLM / VLM / Diffusion / RL-based contribution.
Experiment Plan: Claim Driven, Paper Oriented Validation Refine and concretize: $ARGUMENTS Overview Use this skill after the method is stable enough that the next question becomes: what exact experiments should we run, in what order, to defend the paper? If the user wants the full chain in one request, prefer . The goal is not to generate a giant benchmark wishlist. The goal is to turn a proposal into a claim evidence run order roadmap that supports four things: 1. the method actually solves…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/experiment-plan · pinned to the source commit
# Run from your project root
git clone https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 692e9fa3fea40bbdf614584d461851f8fb968ac2
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/42-wanshuiyin-ARIS/skills/skills-codex/experiment-plan" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 692e9fa3fea40bbdf614584d461851f8fb968ac2
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/42-wanshuiyin-ARIS/skills/skills-codex/experiment-plan" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/experiment-plan
Scanner static-checks@0.1.0 · commit 692e9fa3fea4. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.