team-setup
Walk a new ZAOOS contributor through local setup after cloning - confirms they're on a ws/ branch, bootstraps the ~/.zao/ directories the team-shared skills need, flags any credentials only Zaal can g
SKILL.md.claude/skills/team-setup/SKILL.md
GitHubTeam Setup
Steps
Confirm the user has cloned ZAOOS and is inside the repo (check
pwd/git remote -vshows ZAOOS). If not, tell them to clone first:git clone https://github.com/bettercallzaal/ZAOOS.git.Check they're on a
ws/branch (the repo's worksession convention - see/worksession). If onmainor something else, suggest running/worksessionfirst, but don't block on it.Run the bootstrap script and narrate the result line by line:
bash scripts/setup-claude-teammate.sh- Every
CREATED:<path>line: tell them that directory now exists. - Every
EXISTS:<path>line: tell them it was already there, nothing to do. - Every
MISSING-CRED:<name>line: tell them exactly what's missing and that they should ask Zaal for it directly - do NOT try to generate, guess, or work around credentials yourself.
- Every
Summarize what's now available - six skills, plus gstack:
/qa,/ship,/review,/plan-eng-review- gstack's engineering workflow (also/office-hours,/browse,/retro,/investigate, and more - see the gstack section ofCLAUDE.mdfor the full list)./clipboard- copy/share content from the terminal via a local browser page./handoff- compress a session into a portable bundle for another session/ZOE to resume.
Point them at
CLAUDE.md's Security and Boundaries sections since this is likely their first ZAOOS session.Ask if there's anything specific they're trying to do first, and help with that directly rather than ending the conversation on a checklist.