Menu
Use when you need to set up safety rules and folder structures for a research project.
The review-first prompt is selected by default. You can switch to a direct command or download a local copy.
Read SKILL.md and any companion files shown by SkillsMP before deciding whether to install.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
npx skills add https://github.com/flonat/claude-research --skill project-safetyThe command stays on one line. Scroll horizontally to inspect it before copying.
Prefer a local copy? Download the files currently available to SkillsMP.
Use when you need to audit a research project against the init-project-research template.
Use when you need to validate a paper's bibliography — cross-references \cite{} keys against .bib files or embedded \bibitem entries, finds missing/unused/typo'd keys, and checks every key against the Paperpile library via the local resolver. Deep verification mode spawns parallel agents for DOI/metadata validation at scale. Fix mode rekeys drifted keys to canonical and stages missing entries for Paperpile.
Use when you need to bootstrap a full research project with directory scaffold and Overleaf symlink.
Based on SOC occupation classification
Showing SKILL.md
| name | project-safety |
| description | Use when you need to set up safety rules and folder structures for a research project. |
| argument-hint | ["project-path"] |
CRITICAL RULE: Never delete data or code files. Never. Use legacy/ folder for originals. Copy, don't move.
Establish safety rules and structures before Claude makes changes to research projects.
Based on Scott Cunningham's workflow: prevent accidental data loss by establishing rules and using legacy folders before Claude reorganizes or modifies project files.
Add this to any project's CLAUDE.md file:
## Safety Rules
1. **Never delete data files** — No .csv, .dta, .xlsx, .parquet, or any data format
2. **Never delete code files** — No .py, .R, .do, .tex, .md or scripts
3. **Use legacy/ folder** — If reorganizing, move originals to legacy/ first
4. **Copy from legacy, don't move** — Always preserve the original
### If you need to reorganize:
1. Create a legacy/ folder if it doesn't exist
2. Move ALL original files into legacy/
3. Copy (not move) needed files into new structure
4. Never modify anything in legacy/
After safety setup:
project/
├── CLAUDE.md ← Safety rules + project context
├── README.md ← Project documentation
├── legacy/ ← PROTECTED: original files
│ └── [all originals]
├── code/
│ ├── R/
│ ├── python/
│ └── stata/
├── data/
│ ├── raw/ ← Copied from legacy, never modified
│ └── processed/
├── output/
│ ├── figures/
│ └── tables/
├── docs/
│ └── manuscript/
└── log/ ← Progress logs
Before Claude executes potentially destructive operations, ask for a preview:
"Tell me what commands you would run to reorganize this folder, but don't execute them yet."
"Show me what files would be affected by this change before you make it."
"Walk me through your plan for cleaning this data before you run any code."
When to use dry runs:
After reviewing:
I'm starting work on [PROJECT]. Before we do anything:
1. Create a CLAUDE.md with safety rules (never delete data/code, use legacy folder)
2. Create a legacy/ folder
3. Move all existing files into legacy/
4. Show me the proposed new directory structure before creating it
Do a dry run first — tell me what you would do before doing it.
"Set up my new Carbon Markets project with proper safety rules. Create the CLAUDE.md, legacy folder, and recommended directory structure. Show me your plan before executing."