repo-onboarding
Skill2 starsChanged 56 days agoMITView on GitHub
Onboard a repo into Codex Workspace with runtime metadata, AGENTS guidance, and agent-tooling conventions
10 other projects use a version of this.
Adopted by
Most recently taken up by
- KhaiTrang1995/nexus-kbtheir own version, first seen Nov 8, 2026
- janghotan/repo-onboardingtheir own version, first seen Oct 25, 2026
- salmandev/everything-geminitheir own version, first seen Oct 17, 2026
- dss-time/repo-doctor-skillstheir own version, first seen Oct 15, 2026
- nhat092005/skillstheir own version, first seen Oct 13, 2026
- exerias21/brainstorm-toolkittheir own version, first seen Oct 4, 2026
Used with
Projects with it also use mcp-maintainer and release-guard.
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.
KhaiTrang1995Skillmcp-maintainer
Operate and maintain the local MCP server for this repository. Use for MCP tool updates, policy-guard changes, host configuration, and MCP runtime troubleshooting.
Also in 3 projects that use this
- KhaiTrang1995Skill
release-guard
Run release-readiness checks for this repository. Use when validating docs, scripts, verification coverage, and operational safety before merge or release.
Also in 3 projects that use this
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- hoangsonww/Claude-Code-Agent-Monitor★ 1.2ksame name
- caiaffa/claude-code-ultimate-engineering-system★ 17same name
- ldilov/harness-forge★ 4same name
- salmandev/everything-gemini★ 2same name
- dss-time/repo-doctor-skills★ 1same name
- janghotan/repo-onboarding★ 1same name
- KhaiTrang1995/nexus-kb★ 1same name
- nhat092005/skills★ 1same name
- exerias21/brainstorm-toolkit★ 0same name
- MrZarrar/Jarvis-Sub-Agent-Dashboard★ 0same name
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 repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- agent-tooling-doctorSkill
- quality-gateSkill
- runtime-triageSkill
- security-checkSkill
- ssh-keychain-accessSkill
- typescript-reviewSkill
- workspace-maintenanceSkill
- workspace-quality-gateSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 2 are distinctive, and 7 are very specific to this project.
0
Common
Most of the 10 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 8
Use this skill when adding a repo under repos/ or making an existing repo workspace-ready.
- Very specific: line 13
Add or refine .workspace/project.json only if runtime behavior is not obvious.
- Very specific: line 14
Ensure README.md exists. If it is missing, start from tools/templates/repo-docs/README.template.md.
- Distinctive: line 15
Make sure the README explains setup, run, preview, and current repo purpose.
- Very specific: line 16
Add a repo-local cover block that points to a PNG path such as docs/cover.png, using the placeholder template until a real capture exists.
- Distinctive: line 17
Add repo-level AGENTS.md only when repo-specific rules are genuinely needed.
- Very specific: line 18
If the repo needs Codex-visible capabilities, use .codex/skills/.
- Very specific: line 19
Add .agents/skills/ only when the repo also benefits from a tracked compatibility mirror.
- Very specific: line 20
If the repo needs broader multi-tool agent hints, use .workspace/agent-stack.json.
“Common” is measured: kept by at least 6 in 10 of the 10 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
Repo Onboarding
Use this skill when adding a repo under repos/ or making an existing repo workspace-ready.
Checklist
- Classify the repo conservatively from files first.
- Add or refine
.workspace/project.jsononly if runtime behavior is not obvious. - Ensure
README.mdexists. If it is missing, start fromtools/templates/repo-docs/README.template.md. - Make sure the README explains setup, run, preview, and current repo purpose.
- Add a repo-local cover block that points to a PNG path such as
docs/cover.png, using the placeholder template until a real capture exists. - Add repo-level
AGENTS.mdonly when repo-specific rules are genuinely needed. - If the repo needs Codex-visible capabilities, use
.codex/skills/. - Add
.agents/skills/only when the repo also benefits from a tracked compatibility mirror. - If the repo needs broader multi-tool agent hints, use
.workspace/agent-stack.json.
Helpful commands
tools/scripts/bootstrap-repo.sh
tools/scripts/init-agents-tree.sh repos/<repo>
tools/scripts/sync-codex-skills.sh repos/<repo>Good defaults
- Frontend-style repos default to
direct. - WordPress repos usually stay
external. - Agent tooling should be scaffolded as tracked files, not hidden state.
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.