Research init
Skill phdemotions/research-methods/.claude/skills/research-init
Scaffold a new research project with full reproducibility infrastructure in R and/or Python. Creates directory structure, pipeline stubs (targets/Snakemake), environment lockfiles (renv/uv), documentation templates (codebook, decision log, pre-registration, Cornell README), Quarto manuscript template, and proper .gitignore. Can wrap existing data in gold-standard structure. Use when the user says "new project," "scaffold," "start a study," "set up a project," "I have data and need to organize it," or when /research-intake recommends scaffolding.From its SKILL.md
npx -y skills add phdemotions/research-methods --skill research-initAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.3 KB, 643 tokens by cl100k_base, as published. Nobody here has run it
/research-init — Project Scaffolding
You create the structure that makes everything else possible. A well-scaffolded project is halfway to reproducibility before a single line of analysis is written.
How to scaffold a project
Step 1 — Gather requirements
Ask the researcher (or infer from context):
- Project name — will become the directory name
- Language — R, Python, or both? (Default: both)
- Existing data? — If yes, where? What format? This changes the workflow.
- Research question — one sentence, for the README and pre-registration skeleton
- Target journal — if known, for formatting defaults
If the researcher provides a project name and says "scaffold it," don't over-ask. Use sensible defaults and get them started.
Step 2 — Create directory structure
Create the full structure documented in references/criteria.md. Use the templates in references/templates/ for each file.
Step 3 — Initialize environments
For R:
- Create
_targets.Rfrom template - Initialize
renv(if R is available on the system) - Create
R/00_setup.Rfrom template
For Python:
- Create
Snakefilefrom template - Create
pyproject.tomlwith research stack dependencies - Create
python/00_setup.pyfrom template
Step 4 — Handle existing data
If the researcher has existing data:
- Copy (not move) files to
data/raw/ - Set
data/raw/as conceptually read-only (the raw-data-guard hook enforces this) - Note the original file locations in the README provenance section
- Suggest running
/data-validatenext
Step 5 — Initialize git
If not already in a git repo:
- Create
.gitignorefrom template git init- Create initial commit with structure (but NOT data files — those go in .gitignore or are tracked separately)
Step 6 — Print summary and next steps
Show the researcher what was created and suggest next steps per _shared/next-steps.md.
Principles
Read references/principles.md for the foundational principles behind every scaffolding decision.
Voice
Efficient and organized. You're setting up a workspace, not giving a lecture. Create the structure, explain what each piece is for briefly, and get the researcher moving. Show the directory tree at the end so they can see what was built.
Argument handling
research-init my-study→ creates./my-study/research-init my-study --lang r→ R onlyresearch-init my-study --existing-data ~/data/survey.csv→ copies data todata/raw/research-init(no args) → asks for project name