setup
Interactive setup wizard for the claude-ops plugin. Installs missing CLIs, configures env vars for each channel (Telegram, WhatsApp, Email, Slack, Notion, Linear, Sentry, Vercel), builds the project registry, and saves user preferences. Run once after installing the plugin or any time to reconfigure.
npx skills add davepoon/buildwithclaude --skill setup --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
An interactive configuration wizard that walks the user through installing missing CLIs, configuring environment variables for multiple channels (Telegram, WhatsApp, Email, Slack, Notion, Linear, Sentry, Vercel), building a per-user project registry, and saving user preferences. It is designed to run once after plugin installation or any time reconfiguration is needed.
How it works
- Operates as an interactive wizard for the claude-ops plugin setup.
- Steps include: Step 0 preflight and state detection, Step 1 choosing which sections to configure, Step 2 installing CLIs if needed, Step 2b optional companion plugins, Step 2c early background daemon install, and subsequent steps for channels, MCPs, registry, and preferences.
- Uses multiple Bash tool invocations with a policy that every Bash call includes a short description for the user. All writes target designated paths for prefs, registry, and shell profile. Steps are batched into groups (Batch 1: core setup; Batch 2: channels/plugins/prefs/env; Batch 3: extras).
- Prompts the user with AskUserQuestion for decisions (set up everything, pick sections, or re-run specific sections), and limits options to four per prompt, batching when needed.
- Performs parallel probes and installations where possible and returns results for each action (install success/failure, configuration state).
- Maintains and updates a per-user preferences file at PREFS_PATH, and a per-user registry at ${CLAUDE_PLUGIN_ROOT}/scripts/registry.json; updates to the shell profile are append-only.
When to use it
- After installing the claude-ops plugin or whenever reconfiguration is required.
- When you want to ensure all channels and MCPs are configured, the registry is built, and user preferences are saved in one guided session.
What it can touch
- Bash-based commands to install CLIs, set environment variables, configure channels, build registry, and save preferences.
- Writes to PREFS_PATH (preferences.json) and to ${CLAUDE_PLUGIN_ROOT}/scripts/registry.json. Also appends to the user shell profile.
Caveats
- The wizard enforces that every Bash call uses run_in_background: true for background tasks. It requires user prompts via AskUserQuestion for decisions and may batch prompts to stay within a four-option limit.
- It specifies platform-specific behavior for the background daemon (macOS launchd vs. Linux/WSL handling).
- License is MIT.
# OPS ► SETUP WIZARD You are running an **interactive configuration wizard** for the `claude-ops` plugin. The user wants you to walk them through every step needed to get the plugin working: installing CLIs, setting env vars, configuring channels, populating the project registry, and saving preferences. --- **RULE ZERO — EVERY BASH CALL USES `run_in_background: true`** This is non-negotiable. EVER
What does the setup skill do?
Interactive setup wizard for the claude-ops plugin. Installs missing CLIs, configures env vars for each channel (Telegram, WhatsApp, Email, Slack, Notion, Linear, Sentry, Vercel), builds the project registry, and saves user preferences. Run once after installing the plugin or any time to reconfigure.
How do I install it?
Run `npx skills add davepoon/buildwithclaude --skill setup --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From davepoon/buildwithclaude, a repository with 3,251 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.