Project Onboarding Guide from Knowledge Graph
Egonex-AI/Understand-Anything
Writes an onboarding guide for new team members from a project's existing knowledge graph, after checking that the graph still matches the current commit.
Writes an onboarding document for a new contributor or agent, covering project state, conventions and priorities relevant to a chosen role.
Install Contributor Onboarding Doc
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill onboard -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Donchitos/Claude-Code-Game-Studios onboard --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/onboard .claude/skills/onboard && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "onboard" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/onboard into .claude/skills/onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onboard", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/onboardType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill onboard -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Donchitos/Claude-Code-Game-Studios onboard --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/onboard .agents/skills/onboard && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "onboard" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/onboard into .agents/skills/onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onboard", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill onboard -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Donchitos/Claude-Code-Game-Studios onboard --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/onboard .cursor/skills/onboard && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "onboard" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/onboard into .cursor/skills/onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onboard", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/Donchitos/Claude-Code-Game-Studios.git --path .claude/skills/onboard--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill onboard -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Donchitos/Claude-Code-Game-Studios onboard --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/onboard .gemini/skills/onboard && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "onboard" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/onboard into .gemini/skills/onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onboard", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install Donchitos/Claude-Code-Game-Studios onboardInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill onboard -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/onboard .github/skills/onboard && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "onboard" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/onboard into .github/skills/onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onboard", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add Donchitos/Claude-Code-Game-Studios --skill onboard -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Donchitos/Claude-Code-Game-Studios onboard --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Donchitos/Claude-Code-Game-Studios.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/onboard .opencode/skills/onboard && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "onboard" agent skill from https://github.com/Donchitos/Claude-Code-Game-Studios/tree/main/.claude/skills/onboard into .opencode/skills/onboard/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "onboard", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
onboard- GitHub stars
- 26k
- Token cost
- ~1.4k tokens
- SKILL.md length
- 548 words
- Files
- 1
- Skills in repo
- 73
- Repo updated
- First seen
- Licence
- MIT
At a glance
Writes an onboarding document for a new contributor or agent, covering project state, conventions and priorities relevant to a chosen role.
- Works in 5 steps: Load Project Context → Scan Relevant Area → Generate Onboarding Document → …
- Bringing a new programmer or artist up to speed on a game project's current state
- SKILL.md covers Insufficient input — check…, Phase 1: Load Project Context, Phase 2: Scan Relevant Area and Phase 3: Generate Onboarding…, plus 2 more sections
- Calls bash
What it does
The skill assembles a role-specific onboarding document. It reads `CLAUDE.md` for the project overview and standards and, when you name a role, the matching agent definition under `.claude/agents/`. Both ship with the framework, so if either is missing the skill reports a broken install instead of inventing content.
It then scans the part of the project that matters to that role and writes the document. Before producing anything it lists the inputs it needs, marks each as found or absent and reports sections without data as NOT ASSESSED rather than guessing. A config helper supplies the automation mode, which sets how often it asks before writing.
When your agent uses it
- Bringing a new programmer or artist up to speed on a game project's current state
- Briefing an agent for a specific role on project conventions
- Writing a handover document when a contributor joins mid-project
Example prompts
- “Create an onboarding doc for a new gameplay programmer joining the project.”
- “Onboard the audio director agent with the conventions and current priorities.”
- “Write a role-based onboarding brief for a new level designer.”
Requirements
- `CLAUDE.md` and `.claude/agents/` from the Claude Code Game Studios install
- Pre-approved tools (allowed-tools): Read, Glob, Grep, Write, Bash(bash "*/.claude/skills/onboard/../../hooks/yaml-helper.sh" resolve_config *)
Workflow steps
5 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit b21fa0f. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
ReadGlobGrepWriteBash(bash "*/.claude/skills/onboard/../../hooks/yaml-helper.sh" resolve_config *)
From allowed-tools in the SKILL.md frontmatter.
Runs code
Shell commands in SKILL.md call:
bash
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Contributor Onboarding Doc loads about 1.4k tokens when it runs. Until then it costs about 32 tokens; SKILL.md has 548 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from Donchitos/Claude-Code-Game-Studios at commit b21fa0f, republished under its MIT licence (© Donchitos). 548 words, ~1,370 tokens.
Download SKILL.mdSave it as
.claude/skills/onboard/SKILL.md (or your agent's skills folder).- name
- onboard
- description
- Onboarding doc for a new contributor or agent — project state, conventions, priorities relevant to the specified role.
- allowed-tools
- Read, Glob, Grep, Write, Bash(bash "*/.claude/skills/onboard/../../hooks/yaml-helper.sh" resolve_config *)
- argument-hint
- [role|area]
- user-invocable
- true
- model
- haiku
!bash "${CLAUDE_SKILL_DIR}/../../hooks/yaml-helper.sh" resolve_config --keys automation
Automation mode: Resolve modes.automation (project.local.yaml →
project.yaml → default collaborative). Every AskUserQuestion call and
every file write follows .claude/docs/automation-modes.md
(collaborative asks always · guided major-only · autonomous logs and proceeds;
automation_always_ask categories always prompt).
Insufficient input — check this before producing any report
If the inputs this skill needs do not exist, the answer is "could not run" — not a filled-in report. Check first, and stop if the check fails.
- List the inputs this skill reads (data files, prior reports, profiler output, test results, registries, source code).
- For each, record
FOUNDorABSENT— not "assumed present". - If any input required for a section is ABSENT, that section is
NOT ASSESSED — NO DATA. Do not estimate it, do not infer it from an adjacent artifact, and do not leave a mandated cell to be filled by whoever reads the template next. - If every required input is ABSENT, stop and report
NOT ASSESSED — NO DATAas the whole verdict, naming what was missing and which skill produces it.
A verdict of NOT ASSESSED is a success. It is the correct, useful answer to
"what does the data say?" when there is no data. The failure mode this prevents is
specific and has been observed in practice: report templates whose verdict
enum had no "could not run" state produced false clean passes — an asset audit
returning COMPLIANT on a project with no assets and no standards, and a
performance profile reporting ">99% headroom against a 16.67ms budget" with zero
profiler data and no budget ever set.
Absence of evidence is never evidence of absence. A scan that finds no matches because there are no files to scan has not verified anything. Say which of the two happened — a reader cannot tell from a green result.
Phase 1: Load Project Context
Read CLAUDE.md for project overview and standards.
Read the relevant agent definition from .claude/agents/ if a specific role is specified.
CLAUDE.md and .claude/agents/ ship with the framework — no skill creates them. If either is missing, report it as missing from the install.
Show full SKILL.md (205 more words)Show less
Phase 2: Scan Relevant Area
- For programmers: scan the code root (resolve per
.claude/docs/code-root-resolution.md) for architecture, patterns, key files. An unresolved root means the scan did not run: the sections it feeds readNOT ASSESSED — code root unresolved, never a guess atsrc/ - For designers: scan
design/for existing design documents - For narrative: scan
design/narrative/for world-building and story docs - For QA: scan
tests/for existing test coverage (/test-setupcreates it) - For production: scan
production/for current sprint and milestone - No role or area given: a general orientation — list the top level of
design/,docs/architecture/,production/and the code root, readproduction/session-state/active.mdif it exists, and say that a role would focus the next pass (e.g./onboard programmer)
Read recent changes (git log if available) to understand current momentum.
Phase 3: Generate Onboarding Document
# Onboarding: [Role/Area]
## Project Summary
[2-3 sentence summary of what this game is and its current state]
## Your Role
[What this role does on this project, key responsibilities, who you report to]
## Project Architecture
[Relevant architectural overview for this role]
### Key Directories
| Directory | Contents | Your Interaction |
|-----------|----------|-----------------|
### Key Files
| File | Purpose | Read Priority |
|------|---------|--------------|
## Current Standards and Conventions
[Summary of conventions relevant to this role from CLAUDE.md and agent definition]
## Current State of Your Area
[What has been built, what is in progress, what is planned next. Name what
Phase 2 found by path — for a designer, each existing GDD and design doc — or
say it found none]
## Current Sprint Context
[What the team is working on now and what is expected of this role]
## Key Dependencies
[What other roles/systems this role interacts with most]
## Common Pitfalls
[Things that trip up new contributors in this area]
## First Tasks
[Suggested first tasks to get oriented and productive]
1. [Read these documents first]
2. [Review this code/content]
3. [Start with this small task]
## Questions to Ask
[Questions the new contributor should ask to get fully oriented]Phase 4: Save Document
Present the onboarding document to the user.
Ask: "May I write this to production/onboarding/onboard-[role]-[date].md?"
If yes, write the file, creating the directory if needed.
Phase 5: Next Steps
Verdict: COMPLETE — onboarding document generated.
- Share the onboarding doc with the new contributor before their first session.
- Run
/sprint-statusto show the new contributor current progress. - Run
/helpif the contributor needs guidance on what to work on next.
© Donchitos, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .claude/skills/onboard of Donchitos/Claude-Code-Game-Studios.
Open the folder on GitHubat commit b21fa0f
Compare with similar skills
Contributor Onboarding Doc next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Contributor Onboarding Doc this skillDonchitos/Claude-Code-Game-Studios | 26k | — | ~1.4k | Automated safety check: Pass | MIT | |
| Project Onboarding Guide from Knowledge GraphEgonex-AI/Understand-Anything | 86k | — | ~1.2k | Automated safety check: Pass | MIT | |
| Deepwiki Rssopaco/deepwiki-rs | 3.1k | — | ~748 | Automated safety check: Pass | MIT | |
| Acquire Codebase Knowledgegithub/awesome-copilot | 40k | 1 repos | ~2.3k | Automated safety check: Pass | MIT | |
| Codex Proxy RS Development Guidezyycn/codex-proxy-rs | 750 | — | ~618 | Automated safety check: Pass | Apache-2.0 | |
| Evidence-Grounded ExplainerEveryInc/compound-engineering-plugin | 25k | — | ~2.1k | Automated safety check: Pass | MIT |
Similar skills
Deepwiki Rs
sopaco/deepwiki-rs
AI-powered Rust documentation generation engine for comprehensive codebase analysis, C4 architecture diagrams, and automated technical documentation.
- Official
Acquire Codebase Knowledge
github/awesome-copilot
Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.
Codex Proxy RS Development Guide
zyycn/codex-proxy-rs
Routes development, troubleshooting, review and documentation tasks on the Codex Proxy RS repository to the right section of its docs, instead of loading the whole architecture or contributing guide.
Evidence-Grounded Explainer
EveryInc/compound-engineering-plugin
Produces an evidence-backed explanation of how and why something has its current shape, or what happened over a stretch of work, tuned to its intended reader.
Spec Miner
Jeffallan/claude-skills
Reads an undocumented codebase and writes up what it does: architecture, data flows, observed behavior as EARS requirements, and open questions to confirm.
More from Donchitos/Claude-Code-Game-Studios
All 73 skills in this repoGame Asset Audit
Donchitos/Claude-Code-Game-Studios
Audits game assets against naming conventions, file size budgets and format standards, and finds orphaned assets and missing references.
Game Asset Spec Writer
Donchitos/Claude-Code-Game-Studios
Writes per-asset visual specs and AI image-generation prompts for a game's characters, enemies and screens, driven by the GDD, art bible and an entity inventory.
Game Balance Check
Donchitos/Claude-Code-Game-Studios
Checks game data and formulas for balance outliers, broken progression, degenerate strategies and economy problems, and answers 'could not run' when the data is missing.
Structured Bug Reports
Donchitos/Claude-Code-Game-Studios
Turns a description into a structured bug report, or scans code for likely bugs, then verifies and closes reports through four modes.
Bug Triage
Donchitos/Claude-Code-Game-Studios
Reviews the open bug backlog, separates severity from priority, assigns fixes to sprints and reports systemic trends, writing a dated triage file.
Changelog Generator for Games
Donchitos/Claude-Code-Game-Studios
Generates an internal or player-facing changelog from git commits and sprint data, filtering out framework maintenance commits so that only work on the game itself reaches release copy.
Related
Categories
Questions about Contributor Onboarding Doc
What does Contributor Onboarding Doc do?
Writes an onboarding document for a new contributor or agent, covering project state, conventions and priorities relevant to a chosen role. The skill assembles a role-specific onboarding document.claude/agents/`.
When should I use Contributor Onboarding Doc?
Contributor Onboarding Doc fits situations like: bringing a new programmer or artist up to speed on a game project's current state; briefing an agent for a specific role on project conventions; writing a handover document when a contributor joins mid-project.
How do I install Contributor Onboarding Doc in Claude Code?
Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill onboard -a claude-code`. Or copy the skill folder (.claude/skills/onboard in Donchitos/Claude-Code-Game-Studios) into .claude/skills/onboard in your project. Claude Code loads it when a task matches its description.
How do I install Contributor Onboarding Doc in Codex?
Run `npx skills add Donchitos/Claude-Code-Game-Studios --skill onboard -a codex`. Or copy the skill folder (.claude/skills/onboard in Donchitos/Claude-Code-Game-Studios) into .agents/skills/onboard in your project. Codex loads it when a task matches its description.
Can I use Contributor Onboarding Doc in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Donchitos/Claude-Code-Game-Studios --skill onboard -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/onboard, .gemini/skills/onboard, .github/skills/onboard and .opencode/skills/onboard in your project.
What does Contributor Onboarding Doc need to run?
Going by SKILL.md and its folder, Contributor Onboarding Doc needs the command-line tools its instructions call (bash). Our summary lists: `CLAUDE.md` and `.claude/agents/` from the Claude Code Game Studios install. Its frontmatter pre-approves these tools: Read, Glob, Grep, Write, Bash(bash "*/.claude/skills/onboard/../../hooks/yaml-helper.sh" resolve_config *).
Does Contributor Onboarding Doc access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Contributor Onboarding Doc safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Contributor Onboarding Doc use?
Contributor Onboarding Doc is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Contributor Onboarding Doc use?
About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Contributor Onboarding Doc?
Skills that share tags, products or a category with Contributor Onboarding Doc: Project Onboarding Guide from Knowledge Graph (Egonex-AI/Understand-Anything, 86k stars), Deepwiki Rs (sopaco/deepwiki-rs, 3.1k stars), Acquire Codebase Knowledge (github/awesome-copilot, 40k stars) and Codex Proxy RS Development Guide (zyycn/codex-proxy-rs, 750 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Contributor Onboarding Doc?
Donchitos (a GitHub user) maintains it in Donchitos/Claude-Code-Game-Studios, which has 25,871 GitHub stars. The repository holds 73 skills in this directory. The repository was last updated on September 29, 2026.
Source: Donchitos/Claude-Code-Game-Studios on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.