One line to cowork.

Prerequisites

A typical developer machine already has these.

Pick which tools to install for

The bootstrap accepts a --tool= flag. Leave it off and every detected tool gets configured.

curl -fsSL https://ai.happynguyen.name.vn/install.sh | bash -s -- --tool=cursor

Install for Cursor only.

curl -fsSL https://ai.happynguyen.name.vn/install.sh | bash -s -- --tool=cursor,claude

Install for multiple tools at once.

bin/cowork install --tool=cursor --only=skills,rules

After clone: install only certain categories (skills, rules, hooks, mcp, agents).

Safer: inspect before running

Never pipe a URL into your shell without knowing what it does.

1. 1

   Download the bootstrap

   curl -fsSL https://ai.happynguyen.name.vn/install.sh -o happy-cowork-install.sh

   Copy
2. 2

   Read it

   less happy-cowork-install.sh

   Copy

   It's a thin wrapper: clones nguyenhappy92/happy-cowork into ~/code/happy-cowork and runs the repo's install.sh. Nothing leaves your machine.

3. 3

   Run it

   bash happy-cowork-install.sh

   Copy

Manual clone

Same result, zero curl magic.

1. 1

   Clone

   git clone https://github.com/nguyenhappy92/happy-cowork.git ~/code/happy-cowork

   Copy

   SSH variant: git@github.com:nguyenhappy92/happy-cowork.git. Any path works; ~/code/happy-cowork is just a convention.

2. 2

   Symlink into ~/.cursor/

   cd ~/code/happy-cowork && ./install.sh

   Copy

   Idempotent — safe to re-run. Existing files at the target paths are renamed with a .bak suffix before a symlink replaces them.

3. 3

   Restart Cursor, then verify

   Open Cursor and ask the agent:

   › List the skills you have available.

   You should see create-pr, rebase, review-pr, daily-standup, triage-issues, and release-notes.

What the installer does

No magic. Just symlinks.

• Everything is a symlink. Editing a file in the repo is instantly picked up by Cursor — no reinstall.
• Existing symlinks at the target are replaced. Existing regular files are moved to <path>.bak.
• Scripts under hooks/scripts/ are made executable by the installer.
• Override the Cursor home with CURSOR_HOME=/custom/path.

Install options

Everything below is an environment variable you can prefix to the curl command.

Examples

HAPPY_COWORK_REF=v1.0.0 \
  bash -c "$(curl -fsSL https://ai.happynguyen.name.vn/install.sh)"

Install a pinned version (once you cut a release).

HAPPY_COWORK_DIR=~/dev/happy-cowork \
  bash -c "$(curl -fsSL https://ai.happynguyen.name.vn/install.sh)"

Install into a custom directory.

Platform notes

Updating

Since everything is symlinked, updating is a single git pull:

cd ~/code/happy-cowork && git pull --rebase

Or re-run the one-liner — it's idempotent and will fast-forward to main.

Uninstall

Remove the symlinks. Nothing else is touched — any .bak files stay where they are.

cd ~/code/happy-cowork && \
find ~/.cursor/skills ~/.cursor/rules ~/.cursor/hooks -maxdepth 2 -type l \
  -lname "$(pwd)/*" -print -delete

Troubleshooting

Cursor doesn't see the skills.

Fully quit Cursor (not just close the window) and relaunch. Confirm the symlinks: ls -la ~/.cursor/skills.

~/.cursor/ doesn't exist.

Launch Cursor once so it creates the directory, then re-run the installer.

The installer says "Backing up existing … -> ….bak".

Expected. You had a regular file or directory at the target path; it's safe on disk next to the new symlink.

Permission denied on install.sh.

The bootstrap sets chmod +x automatically. If you cloned manually: chmod +x install.sh.

I use zsh / fish — does that matter?

No. The scripts run under bash regardless of your interactive shell.

Can I install into a custom Cursor home?

Yes: CURSOR_HOME=/some/path bash -c "$(curl -fsSL https://ai.happynguyen.name.vn/install.sh)".

The curl fails with certificate problem.

Your system clock is probably off, or a corporate proxy is intercepting TLS. Fix the clock, or use the manual clone path.

What next