ts-testing

```

.

├── skills/ # Skill definitions plus reference docs

├── hooks/ # Bun-powered approval hooks for certain skills

├── settings/ # Claude hook wiring (JSON) and supporting packages

├── mcp/ # MCP server definitions (Chrome DevTools)

└── scripts/ # Helper utilities for selective installs

```

| Skill | Summary | Supporting Files | Notes |

| --- | --- | --- | --- |

| chrome-devtools | Automate Chrome via the DevTools Protocol (navigation, interaction, tracing). | skills/chrome-devtools/**
hooks/hooks.chrome-devtools.ts
settings/settings.chrome-devtools.json
mcp/mcp.chrome-devtools.json | Add Skill(chrome-devtools) to settings.json. Requires bun to execute hooks and launch the MCP server. |

| diagram | Maintain Diagram Driven Development assets and references. | skills/diagram/** | Optionally whitelist with Skill(diagram) in settings.json. |

| github | Manage GitHub issues end-to-end with gh. | skills/github/**
hooks/hooks.github.ts
settings/settings.github.json | Ensure Skill(github) is allowed in settings.json. Requires the GitHub CLI (gh). |

| review | Persona-driven code review orchestrator (Fowler, Torvalds, Carmack, etc.). | skills/review/** | Keep Skill(review) in settings.json so Claude can load reviewer personas. |

• GitHub CLI (gh) authenticated for the attendee.
• bun installed and on PATH for skills that invoke Bun hooks (currently Chrome DevTools and GitHub).
• rsync (or adjust commands to use cp -R) for copying into ~/.claude.

```bash

# Replace with the public repo slug you publish

REPO_SLUG="johnlindquist/claude-workshop-skills"

WORKDIR="$HOME/Downloads/claude-workshop-skills"

# 1. Backup existing Claude config

tar -czf "$HOME/.claude-backup.$(date +%Y%m%d).tgz" -C "$HOME" .claude

# 2. Clone the skills repo

gh repo clone "$REPO_SLUG" "$WORKDIR"

# 3. Copy into ~/.claude (dry run first if desired)

rsync -av --exclude='.git' "$WORKDIR/" "$HOME/.claude/"

# 4. Install hook dependencies

(cd "$HOME/.claude/hooks" && bun install)

(cd "$HOME/.claude/settings" && bun install)

```

Restart Claude (or reload the workspace) so it picks up new skills, hooks, and MCP servers.

After cloning the repository, run the included script to copy everything needed for a single skill:

```bash

REPO_DIR="$HOME/Downloads/claude-workshop-skills"

cd "$REPO_DIR"

# Examples

./scripts/install-skill.sh github

./scripts/install-skill.sh chrome-devtools

```

The script copies the skill folder plus any required hooks, settings, or MCP files into ~/.claude and reminds attendees to update settings.json if needed.

Override the destination with CLAUDE_HOME:

```bash

CLAUDE_HOME="$HOME/.claude-workshop" ./scripts/install-skill.sh diagram

```

Attendees who only want one skill can fetch just the relevant directories using sparse checkout:

```bash

REPO_SLUG="johnlindquist/claude-workshop-skills"

WORKDIR="$(mktemp -d)"

gh repo clone "$REPO_SLUG" "$WORKDIR" -- --filter=blob:none --sparse

cd "$WORKDIR"

# Pull only what the helper script needs

git sparse-checkout set \

scripts/install-skill.sh \

skills/github \

hooks/hooks.github.ts \

settings/settings.github.json

# Install the skill

./scripts/install-skill.sh github

```

Swap skills/github and the supporting files for whichever skill they want (see the Skill Index table for dependencies). This keeps bandwidth low while still using the helper script to wire everything correctly.