agentleFS
maxwell2732maxwell2732/claudecode-research-harness-workflow/skills/research-harness-setup/SKILL.md

research-harness-setup

Skill42 starsChanged 6 days agoMITView on GitHub

RES: Initialize research project structure, create study_spec.md and analysis_plan.md, set up data protection rules and folder layout. Trigger: setup research project, initialize study, new research project. Do NOT load for: audit, cleaning, analysis, review, release.

The file

Show its rules and text

We split this skill into the rules it gives an agent

13 rules. About 0 are common, 5 are distinctive, and 8 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 8

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    If arguments are not provided, ask the user for:

    line 36
  2. Very specific:

    Do not invent answers. If the user says unknown, write unknown in the spec.

    line 42
  3. Distinctive:

    Create the following directories if they do not exist.

    line 46
  4. Very specific:

    Leave all other fields as unknown.

    line 68
  5. Very specific:

    If study_spec.md already exists: read it, confirm with the user before overwriting, and preserve existing content unless the user …

    line 70
  6. Very specific:

    Leave all task fields as cc:todo with unknown paths.

    line 81
  7. Very specific:

    If analysis_plan.md already exists: do not overwrite.

    line 83
  8. Very specific:

    Write a data/raw/READONLY.md file with the following content:

    line 97
  9. Very specific:

    Do not modify any file under data/raw/

    line 128
  10. Distinctive:

    Do not invent a research question if the user did not provide one

    line 129
  11. Distinctive:

    Do not claim the data is feasible for the proposed design before an audit is run

    line 130
  12. Distinctive:

    Do not run any analysis or data inspection in this step

    line 131
  13. Very specific:

    Do not overwrite study_spec.md without user confirmation if it already exists

    line 132

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Research Harness Setup

Initialize a new empirical research project with source-of-truth files, a controlled folder structure, and data protection rules.

This skill runs once at the start of a project. It does not run analysis, audit data, or claim feasibility.

Quick Reference

InputAction
/research-harness-setupInteractive: prompt for study name and data path, then create all files
/research-harness-setup --study-name "X" --data-path "data/raw/X.csv"Non-interactive: use provided values

Procedure

Step 1 — Collect study context

If arguments are not provided, ask the user for:

  1. Study name or working title
  2. Path to raw data file(s) (may be unknown if data not yet available)
  3. Brief description of the research question (one or two sentences; may be unknown)

Do not invent answers. If the user says unknown, write unknown in the spec.

Step 2 — Create folder structure

Create the following directories if they do not exist. Do not delete or overwrite existing content.

data/raw/
data/intermediate/
data/processed/
scripts/
analysis/
output/
logs/
reports/

Step 3 — Create study_spec.md

Copy templates/study_spec.md to study_spec.md at the project root.

Fill in:

  • Study name from Step 1
  • Raw data path from Step 1
  • Research question from Step 1

Leave all other fields as unknown. The researcher fills in the full spec before Stage 2.

If study_spec.md already exists: read it, confirm with the user before overwriting, and preserve existing content unless the user explicitly requests replacement.

Step 4 — Create analysis_plan.md

Copy templates/analysis_plan.md to analysis_plan.md at the project root.

Fill in:

  • Study spec path: study_spec.md
  • Date: today's date
  • Analyst: Claude Code

Leave all task fields as cc:todo with unknown paths.

If analysis_plan.md already exists: do not overwrite. Notify the user.

Step 5 — Write data protection notice

Append the following block to the project .gitignore if it does not already contain it:

# Research Agent Harness — raw data is read-only
# Never commit cleaned or processed datasets unless explicitly approved
data/processed/
data/intermediate/
logs/

Write a data/raw/READONLY.md file with the following content:

# data/raw — READ-ONLY

This folder contains raw, unmodified data files.

No script, agent, or tool may write, edit, rename, or delete files in this folder.
All data transformations must produce new files in data/processed/ or data/intermediate/.

See docs/INTEGRITY-RULES.md Rule 1.

Step 6 — Confirm and report

Print a setup summary:

Research Agent Harness — Setup Complete

Study spec:     study_spec.md         [created / already existed]
Analysis plan:  analysis_plan.md      [created / already existed]
Folders:        data/raw, data/intermediate, data/processed,
                scripts, analysis, output, logs, reports
Data protection: data/raw/READONLY.md written

Next step: Fill in study_spec.md, then run /research-harness-audit

Forbidden Actions

  • Do not modify any file under data/raw/
  • Do not invent a research question if the user did not provide one
  • Do not claim the data is feasible for the proposed design before an audit is run
  • Do not run any analysis or data inspection in this step
  • Do not overwrite study_spec.md without user confirmation if it already exists

Completion Criteria

  • study_spec.md exists with study name, data path, and research question filled in (or unknown)
  • analysis_plan.md exists with header fields populated
  • All 8 folders exist
  • data/raw/READONLY.md exists
  • No files under data/raw/ were modified

Handoff to Stage 2

Tell the user:

Fill in the remaining fields in study_spec.md — particularly identification strategy, variables, and sample restrictions — before running /research-harness-audit. When study_spec.md is complete and you have approved it, run /research-harness-audit.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.