Run an end-to-end workflow that chains `research-refine` and `experiment-plan`. Use when the user wants a one-shot pipeline from vague research direction to focused final proposal plus detailed experiment roadmap, or asks to "串起来", build a pipeline, do it end-to-end, or generate both the method and experiment plan together.
Research Refine Pipeline: End to End Method and Experiment Planning Refine and concretize: $ARGUMENTS Overview Use this skill when the user does not want to stop at a refined method. The goal is to produce a coherent package that includes: a problem anchored, elegant final proposal the review history explaining why the method is focused a detailed experiment roadmap tied to the paper's claims a compact pipeline summary that says what to run next This skill composes two existing workflows: 1.…
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/research-refine-pipeline · pinned to the source commit
git clone https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git
cd Auto-Empirical-Research-Skills
git checkout 692e9fa3fea40bbdf614584d461851f8fb968ac2
mkdir -p ".claude/skills/research-refine-pipeline"
cp -r "skills/42-wanshuiyin-ARIS/skills/research-refine-pipeline" ".claude/skills/research-refine-pipeline"Review the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
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.
References parent-directory traversal, which can escape a target directory.
Evidence: ../· fingerprint fa08499e14d0113b