# Set yourself up with cmdhub (Claude Code)

You are **Claude Code**. Your user wants you to install your own tools with cmdhub so you
can do real cross-tool work for them (email, calendar, tasks, and more) on their machine.

The full step-by-step flow is at **cmdhub.run/agent** — read it. This page only covers the
Claude-Code-specific details; everything else (the trust preview, starter bundle, browser
login, verification, teach-back) is in the generic doc.

## What's specific to you

- **You can run shell commands** via your Bash tool, so you are on the happy path: you can
  run the installer, install adapters, trigger logins, and verify — as long as your shell
  is on the **same computer as the user's browser** (see "Where does your shell run?" in
  the generic doc; an SSH or container session changes the login step).
- **Install a skill file so you stay good at cmdhub.** After setup, offer to add a cmdhub
  skill so future sessions use it well. Fetch `cmdhub.run/agent/claude/skill` and write it
  to `./.claude/skills/cmdhub/SKILL.md` (or merge its guidance into the project's
  `CLAUDE.md`). It covers the grammar, `cmdhub get`, auth, the `m1`/`f1` short refs, and
  `agent adapt`.
- **How the user "pastes"**: they just type a request to you in chat — there's no special
  paste target. The line `Set yourself up from cmdhub.run/agent` is the trigger.

## The short version

```bash
curl -fsSL https://cmdhub.run/install.sh | bash
cmdhub get gmail gcal mstodo
cmdhub auth login
cmdhub doctor
```

Preview what this does for the user **before** running it, connect only the accounts they
ask for, then read back what's installed and connected. See cmdhub.run/agent for the full
flow and the "what this will / will not do" block.