Onboard

Before you start: read this whole install prompt, tell me in a few lines what this skill does and what installing it involves, and wait for my go-ahead before you do anything else. Prerequisites — INTEGRATED SYSTEM FIRST: this skill is one piece of the complete "Claude Code Game Studios" template (49 agents, 74 skills, studio templates and a studio CLAUDE.md, per the repository README). Each skill assumes that template is installed, with its conventions, its project.yaml / project.local.yaml configuration, its .claude/docs/ mode documents, its hooks (for example hooks/yaml-helper.sh, outside this skill's folder) and its .claude/scripts/ helpers. Installing this listing alone copies only this skill's folder, without the rest of the system: the skill may reference template agents, files, hooks or scripts that are absent outside the full template, and it may not run as designed on its own. No account, no key and no payment are needed to copy the files, and nothing is run during installation. Install "Onboard" for me. It generates an onboarding document for a new contributor or agent, tailored to a role or area given as its argument. It reads the project CLAUDE.md and the relevant agent definition under .claude/agents/ (both ship with the framework; if either is missing it reports it as missing from the install), scans the area relevant to the role — the code root for programmers, design/ for designers, design/narrative/ for narrative, tests/ for QA, production/ for production — reads recent changes via git log when available, and marks any section whose inputs are absent NOT ASSESSED — NO DATA rather than filling it in. It presents the document and asks before writing it to production/onboarding/onboard-[role]-[date].md. Its frontmatter pins model: haiku. Repository: https://github.com/Donchitos/Claude-Code-Game-Studios (the skill is the whole .claude/skills/onboard/ folder at the pinned commit: 1 file in total) Pinned version: install the code at commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418 exactly. Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Clone https://github.com/Donchitos/Claude-Code-Game-Studios into a temporary folder, check out commit 05ad7c8a5b8aa2aa86bbd3439ae7cf7295cac418, and copy the .claude/skills/onboard/ folder from that checkout. Then compare every file in the folder with the fingerprints recorded for this listing on 2026-10-22: [FINGERPRINTS] - SKILL.md: SHA-256 e10acba4b4cac6b95471b3b5b11c524dfea578e030029b87a55407ac129c756c If a file does not match, it changed since the listing was prepared: do not install it yet, tell me what you found and let me decide. 2. Read SKILL.md in full, and tell me in plain words: what the skill does when used, what it connects to, whether it reads or sends any personal information or credentials, and anything that seems unusual. Stop on any red flag and tell me before going further. Confirm these points from the files: - The skill folder holds 1 file: SKILL.md only. Nothing in the folder is a program; it is instructions the agent follows at use time. - Nothing is sent anywhere during installation itself; the only download at install time is the skill folder from GitHub at the pinned commit, and no project of mine is read or modified. - Integrated-system reality, from the file: at use time the skill resolves its automation mode by running the template's hooks/yaml-helper.sh (key automation), follows .claude/docs/automation-modes.md and .claude/docs/code-root-resolution.md, and reads my project's CLAUDE.md, .claude/agents/, code root, design/, tests/, production/ and recent git log — the CLAUDE.md and agent definitions are framework files that live outside this skill's folder and are absent in a standalone install, so it cannot run as designed on its own. - At use time it writes only after asking: its one persistent output is the onboarding document at production/onboarding/onboard-[role]-[date].md in my project. No third-party service, account or credential is named in the file; the git log it reads stays local. - Do not onboard anyone, do not run any template hook, and do not use the skill in any way during this install: using it is a separate step that only starts when I ask for it later. 3. When I say "yes, install", install it as a skill: copy the whole onboard folder into the agent's skills directory, in a folder named exactly "onboard", keeping its 1 file in their original relative layout (SKILL.md at its root). 4. Verify with no network calls: frontmatter valid (name: onboard), the 1 file in place with matching fingerprints. Do not run anything from the folder and do not use the skill to verify. 5. Report what was installed, where, and what I still need to do myself (for example: that it belongs to the full Claude Code Game Studios template and may not run standalone (it reads the framework's CLAUDE.md and .claude/agents/ definitions and resolves its settings through the template's yaml-helper hook), and that it writes its onboarding document only after asking). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.