init-project
Skill25 starsChanged 2 months agoMITView on GitHub
Use when the user requests adding LabMate to a project or setting up its research skeleton. Triggers on "init project", "初始化项目", "set up labmate", "first time setup", "initialize".
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
- ryanportfolioSkill
apply-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
- flonat/flonat-research★ 150same name
- huangwb8/skills★ 50same name
- jiahao-shao1/sjh-skills★ 43same name
- eugenelim/agent-ready-repo★ 28same 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- project-skillSkill
- project-skillSkill
- analyze-experimentSkill
- commit-changelogSkill
- monitorSkill
- new-experimentSkill
- read-paperSkill
- survey-literatureSkill
- todoSkill
- update-docsSkill
- update-knowhowSkill
- update-project-skillSkill
- visualizeSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 1 is distinctive, and 3 are very specific to this project.
0
Common
Most of the 42 edited versions we read keep these.
1
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 9
Create an idempotent LabMate skeleton through the bundled interface.
- Very specific: line 26
If the plan would overwrite or semantically conflict with existing project instructions, stop and explain.
- Distinctive: line 34
When both hosts are selected, project-skill mirrors must match.
- Very specific: line 37
Do not initialize LabMate merely because a session hook mentions it.
“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
Create an idempotent LabMate skeleton through the bundled interface. The model infers project metadata; the script owns filesystem layout and parity.
Workflow
- Inspect the repository and infer project name, description, domain,
generalorresearch, compute environment, and host target. - Show the inferred values once. Ask only about a value that would materially change the generated project.
Resolve
<plugin-root>from this file and preview:python3 <plugin-root>/scripts/init_project.py plan \ --type <general|research> --target <codex|claude|both> \ --project-name <name> --description <description> --domain <domain>- If the plan would overwrite or semantically conflict with existing project
instructions, stop and explain. Otherwise rerun with
apply, thencheck. - Report created, updated, skipped, and missing paths from the JSON results.
Contract
- Existing project files are never replaced. Missing instruction sections may be appended; existing sections remain authoritative.
- When both hosts are selected, project-skill mirrors must match.
- A dirty worktree is not an automatic blocker. Preserve unrelated changes and call out overlapping target files before applying.
- Do not initialize LabMate merely because a session hook mentions it.
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
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.