setup-connectorslisted
Install: claude install-skill skowalskidev/dotclaude
# Set up / doctor the connectors for this project
The premise: connectors + credentials are declared per project in `~/.claude/connectors/<project>.json`
and driven by a generic engine (`~/.claude/bin/connectors-provision.sh` + the guard + the SessionStart
hook). This skill is the guided front door. On a plain `/sk:setup-connectors` (no args) it AUTOMATICALLY takes
care of the whole setup for the current project — provisions what it can, diagnoses the rest
green/yellow/red (like `flutter doctor`), AND audits for insecure local approaches to migrate — then
proposes everything (auth steps + migrations) in ONE consolidated pass and waits for Simon's decisions.
He never needs to remember a sub-command; figure out what's needed and propose it. Always follow the
auth-gate protocol in `rules/connectors.md`: ask FIRST, numbered steps, then wait; never grind around a
missing connector.
The default (no arg) already does **setup + doctor + migration audit**. The named modes are optional
focused shortcuts: `add` = register a new connector; `migrate` = run ONLY the audit + migration proposal;
`enable-prod-write <platform>` = turn on a separate, temporary prod-write pathway.
## Mode: setup + doctor (default)
1. **Resolve the project.** `~/.claude/bin/connectors-provision.sh --manifest` prints this project's
manifest. If empty, tell Simon no manifest matches this repo, show its `git remote get-url origin`,
and offer to create one (`add` mode seeds it) — then stop.
2. **Provision w