team-setuplisted

Inject this repo's skills into the user level (~/.claude/skills) so they work in every project on this machine. Run once per machine; after that, git pull alone keeps skills in sync. Also sets the TEAM_WORKFLOWS_DIR environment variable. Use on requests like "setup", "machine setup", or "team-setup".
umezy/team-ai-workflows · ★ 1 · AI & Automation · score 72

Install: claude install-skill umezy/team-ai-workflows

# User-level setup for the team AI workflow repo After this runs, every Claude Code session on this machine can use the skills under `skills/`, no matter which directory it starts in. New projects need no per-project setup. ## Path resolution Resolve the repo root (`TEAM_WORKFLOWS_DIR`) with `git rev-parse --show-toplevel`. This skill must be run from a Claude Code session started **inside this repository**. ## Design constraints (do not change) - Use **one link per skill**. Never create a single link over the whole `~/.claude/skills` folder or a grouping subfolder (`~/.claude/skills/<group>/<skill>/`). Nested layouts are not discovered when the session cwd is a git repository. ## Workflow ### Step 1. Sync skill links (always) ```bash bash "<TEAM_WORKFLOWS_DIR>/.claude/skills/team-setup/scripts/sync_user_skills.sh" ``` This links every skill under `skills/` into `~/.claude/skills/<name>` (idempotent — safe to re-run any time): - missing link -> created `[created]` - broken link (skill deleted / repo moved) -> removed `[removed]` (recreated at the new path on the same run if the skill still exists) - existing entry -> left untouched (counted as `kept`) After syncing, list the entries (Windows: `cmd /c "dir %USERPROFILE%\.claude\skills /AL"` / macOS & Linux: `ls -la ~/.claude/skills`). If a skill name from `skills/` is missing from the link list, a **real folder with the same name already exists** (a personal skill conflict). Present the conflicting names and use Ask