init-project
Skill150 starsChanged 9 days agoMITView on GitHub
Bootstrap a new research project. Interview for details, scaffold directory structure, create Overleaf symlink, initialise git, and create project context files.
49 other projects use a version of this.
Adopted by
Most recently taken up by
- itsryanarmani/skillstheir own version, first seen Nov 8, 2026
- ryanportfolio/winuse-mcptheir own version, first seen Nov 8, 2026
- eugenelim/agent-ready-repotheir own version, first seen Nov 8, 2026
- pooriaarab/skillstheir own version, first seen Nov 7, 2026
- ice-lfernandes/claude-spring-architecttheir own version, first seen Nov 7, 2026
- nerviz-ai/nerviztheir own version, first seen Nov 7, 2026
Used with
Projects with it also use addskill, apply-firmware and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
ryanportfolioSkilladdskill
Create, import, update, or install repo or personal skills: runtime ownership, resources, discovery checks.
Also in 6 projects that use this
ryanportfolioSkillapply-firmware
Bring current folder (plain folder, existing repo, old or partial firmware copy) up to full Harness Firmware in place. Mirror external repo → adopt-repo.
Also in 6 projects that use this
- +10 more from ryanportfolio
Other versions49 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 49
- southliu/south-admin-react★ 582same name
- wataru-maeda/react-native-boilerplate★ 521same name
- huangwb8/skills★ 50same name
- jiahao-shao1/sjh-skills★ 43same name
- eugenelim/agent-ready-repo★ 28same name
- freemty/labmate★ 25same name
- ice-lfernandes/claude-spring-architect★ 11same name
- nerviz-ai/nerviz★ 11same name
- eranw2000/multi-phase-skills-framework★ 10same name
- luiseiman/dotforge★ 8same name
39 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository89 other files it gives its agents.
- AGENTS.mdAGENTS.md
- docs/agents.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- beamer-deckSkill
- bib-coverageSkill
- bib-filterSkill
- bib-parseSkill
- brief-compliance-checkSkill
- camera-readySkill
- causal-designSkill
- checkpointSkill
- code-archaeologySkill
- compile-knowledgeSkill
- computational-experimentsSkill
- cross-language-checkSkill
- data-analysisSkill
- devils-advocateSkill
- docs-consistencySkill
- docxSkill
- experiment-designSkill
- grill-meSkill
- handoffSkill
- ideasSkill
- init-project-courseSkill
- init-project-lightSkill
- init-project-orchestrationSkill
- insights-deckSkill
- interview-meSkill
- knowledge-lintSkill
- latex-diffSkill
- latex-health-checkSkill
- latex-polishSkill
- latex-postersSkill
- latex-scaffoldSkill
- latexSkill
- latex-templateSkill
- lean-checkSkill
- math-proofSkill
- mcp-builderSkill
- method-auditSkill
- multi-perspectiveSkill
- numerical-checkSkill
- pdfSkill
- pipeline-manifestSkill
- playwright-cliSkill
- postmortemSkill
- pre-commit-auditSkill
- pre-submission-reportSkill
- project-deckSkill
- project-safetySkill
- proof-readabilitySkill
- proofreadSkill
- python-envSkill
- quarto-deckSkill
- reorgSkill
- replication-auditSkill
- replication-packageSkill
- retarget-journalSkill
- review-clusterSkill
- review-responseSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 42 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 16
Ask the user these questions using AskUserQuestion (adapt based on what's already known):
- Distinctive: line 29
Create the directory structure:
- Distinctive: line 96
Update the central context library:
- Very specific: line 97
Add the project to .context/projects/_index.md
- Very specific: line 98
Create .context/projects/papers/<project-name>.md with metadata
“Common” is measured: kept by at least 6 in 10 of the 42 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Init Project — Research Project Scaffolder
Interactive project setup: answer questions, get a ready-to-use research project directory.
Protocol
Phase 1: Interview
Ask the user these questions using AskUserQuestion (adapt based on what's already known):
- Project name — short name for the directory (e.g.,
nudge-experiment) - Paper title — working title for the paper
- Research question — one sentence
- Target journal/venue — where you plan to submit
- Co-authors — names and affiliations (if any)
- Parent directory — where to create the project (default:
~/Research/) - Overleaf path — path to Overleaf-synced directory for symlink (optional)
- Methodology — experimental, observational, theoretical, simulation, mixed
Phase 2: Scaffold
Create the directory structure:
<project-name>/
├── CLAUDE.md # Project-specific Claude instructions
├── README.md # Project overview
├── MEMORY.md # Knowledge base (seeded with template)
├── paper/ # → Overleaf symlink (or empty dir)
├── code/
│ ├── python/ # Python scripts
│ └── R/ # R scripts
├── data/
│ ├── raw/ # Original data (never modified)
│ └── processed/ # Cleaned/transformed data
├── results/ # Analysis outputs
├── figures/ # Generated figures
├── docs/ # Project documentation
├── correspondence/ # Referee reports, cover letters
│ └── referee2/ # Referee 2 agent reports
├── log/ # Session logs
│ └── plans/ # Saved plans
└── .gitignorePhase 3: Populate Files
CLAUDE.md — project-specific instructions:
- Paper title and research question
- Co-authors and target venue
- Methodology and key conventions
- Pointer to project context files
README.md — human-readable overview:
- Project title and description
- Directory structure explanation
- How to compile the paper
- Co-author information
MEMORY.md — seeded with research project template:
- Notation Registry (empty)
- Estimand Registry (empty)
- Key Decisions (empty)
- Citations (empty)
- Anti-Patterns (empty)
- Code Pitfalls (empty)
.gitignore — standard research project ignores:
- Build artifacts (
out/,*.aux,*.log) - Data files (
data/raw/*.csv,data/raw/*.xlsx) - Python/R artifacts (
__pycache__/,.Rhistory) - OS files (
.DS_Store)
Phase 4: Git & Symlinks
- Overleaf symlink — if a path was provided:
ln -s /path/to/overleaf/dir paper - Git init — initialise the repository:
git init git add . git commit -m "Initial project scaffold"
Phase 5: Context Update
Update the central context library:
- Add the project to
.context/projects/_index.md - Create
.context/projects/papers/<project-name>.mdwith metadata
Output
Print a summary of what was created:
Project created: ~/Research/<project-name>/
Directories: 12
Files: 4 (CLAUDE.md, README.md, MEMORY.md, .gitignore)
Overleaf: linked / not configured
Git: initialised with initial commit
Next steps:
1. Start writing in paper/ (or link Overleaf)
2. Add code to code/python/ or code/R/
3. Run session-log when you finish workingDoes 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
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.

