# Jobber

> Use this skill whenever you need to inspect or operate Jobber through the local jobber CLI. Covers auth checks, current user and account identity, discovered operation browsing, and raw GraphQL against Jobber's private web API.

- Skill: `danielgwilson/jobber` (Agent Skill, multi-file: 4 files)
- Install (CLI): `npx skillmds@latest add danielgwilson/jobber`
- Raw SKILL.md: https://api.skillmd.com/api/skills/danielgwilson/jobber/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: danielgwilson (https://skillmd.com/u/danielgwilson)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/danielgwilson/jobber

---


# Jobber CLI Skill

Use this skill when you need to inspect or operate Jobber through the local
`jobber` CLI.

## Command

Important naming detail:

- npm package name: `jobber-cli`
- CLI binary name: `jobber`

Prefer an installed binary:

```bash
jobber --help
```

For one-off package use after publication:

```bash
npx -y jobber-cli --help
```

For a source checkout:

```bash
npm install
npm run build
node dist/cli.js --help
```

Do not guess alternate package names unless they are explicitly published later.

## Safety Rules

- This is an unofficial private-surface adapter and is fragile by definition.
- Prefer read operations before mutations.
- Prefer `--json` for machine-readable output.
- Do not print, paste, store in repo, or commit Jobber cookie headers.
- Keep raw browser captures, traces, cookies, storage state, and full upstream
  JSON exports out of the repo.
- `operations list` is a discovered inventory, not a guarantee that every
  operation has a recovered query document.
- Use `graphql run` to prototype unsupported workflows before adding typed
  commands.

## First Checks

```bash
jobber auth status --json
jobber doctor --json
jobber whoami --json
```

If auth is missing, import from a live logged-in `agent-browser` session or
attached browser on the same machine:

```bash
jobber auth import-agent-browser
```

Manual cookie-header auth is supported, but avoid putting cookie values in
shell history, logs, or chat:

```bash
printf '%s' "$JOBBER_COOKIE_HEADER" | jobber auth set-cookie-header --stdin
```

## Common Reads

```bash
jobber operations list --json
jobber operations list --search client --json
jobber operations inspect ClientDefaults --json
jobber graphql run --operation-name CurrentAccount --query 'query CurrentAccount { account { id name inTrial industry } }' --json
jobber graphql run --query-file ./query.graphql --variables-file ./vars.json --json
```