Business operating system for Claude Code — 57 skills, 21 agents, smart daemon. Unified inbox (WhatsApp/Email/Slack/Telegram), autonomous PR merge, full-AWS monitoring, revenue (Stripe+RevenueCat), e-commerce (Shopify), marketing (Klaviyo/Meta/GA4), voice (Bland/ElevenLabs), APM (Datadog/NewRelic/OTEL), YOLO mode.
Shell agent-teamsai-agentai-automationanthropicautonomous-agentawsbusiness-operationsclaudeclaude-codeclaude-code-plugindevopsecommerceinbox-zeroklaviyomarketingmcpmorning-briefingpr-automationshopifyterminal
feat(setup): phase 17 - quick-start profiles, fast path, progress panel, marketplace keywords
auroracapitale046f8d91e11
diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.jsonindex 042ee908..aef1838b 100644--- a/.claude-plugin/marketplace.json+++ b/.claude-plugin/marketplace.json@@ -13,6 +13,23 @@"source": "./claude-ops","version": "1.7.1","category": "productivity",+ "keywords": [+ "ops",+ "operations",+ "business",+ "dashboard",+ "automation",+ "daemon",+ "whatsapp",+ "email",+ "slack",+ "marketing",+ "aws",+ "monitoring",+ "yolo",+ "revenue",+ "gtm"+ ],"screenshots": ["docs/screenshots/dashboard.png","docs/screenshots/briefing.png",diff --git a/claude-ops/skills/ops-status/SKILL.md b/claude-ops/skills/ops-status/SKILL.mdindex 11a5b221..618dfc2f 100644--- a/claude-ops/skills/ops-status/SKILL.md+++ b/claude-ops/skills/ops-status/SKILL.md@@ -103,3 +103,18 @@ ${CLAUDE_PLUGIN_ROOT}/bin/ops-status $ARGUMENTS| The full morning briefing with real data | `/ops:go` || Deep diagnostics + auto-repair | `/ops:doctor` || An interactive dashboard with hotkeys | `/ops:dash` |++## Integration with /ops:setup++`/ops:setup` (and its `--re-setup` flag) queries this skill for a per-section health map and uses it to filter the setup selector to only broken/unconfigured sections. The compact shape expected is:++```json+{+ "telegram": "green",+ "whatsapp": "missing",+ "email": "red",+ "slack": "green"+}+```++Maintain this contract when extending the status output — the setup wizard keys on section names like `telegram`, `whatsapp`, `email`, `slack`, `notion`, `calendar`, `doppler`, `vault`, `ecommerce`, `marketing`, `voice`, `revenue`, `discord`, `notifications`, `github`, `aws`, `sentry`, `linear`. A `--brief` (or equivalent JSON) mode that returns this map is the recommended integration surface.diff --git a/claude-ops/skills/setup/SKILL.md b/claude-ops/skills/setup/SKILL.mdindex 9cd9fb86..41542639 100644--- a/claude-ops/skills/setup/SKILL.md+++ b/claude-ops/skills/setup/SKILL.md@@ -58,6 +58,45 @@ Every Bash tool call MUST include a short `description` parameter (5-10 words, e---+## Arguments++The setup wizard accepts these flags (parsed from `$ARGUMENTS`):++- `--fast` — Zero-prompt fast path. When credentials are found by the Universal Credential Auto-Scan, auto-select "Configure all" / "Set up everything" everywhere without asking. Only fall back to interactive prompts when a section has no credentials at all.+- `--profile <name>` — Pre-select a curated integration subset. Valid names:+ - `developer` — GitHub, AWS, Sentry, Linear, Doppler, Daemon.+ - `founder` — All comms (Telegram, WhatsApp, Email, Slack, Calendar), plus Doppler, Linear, Daemon.+ - `marketer` — Klaviyo, Meta Ads, GA4, Search Console, Shopify, Email (sending), Doppler.+- `--re-setup` — Skip Step 1's "what do you want to configure" prompt and route directly to broken/unconfigured sections based on `/ops:status`. Equivalent to auto-detected incremental mode.++**Precedence:** `--profile` narrows the section set first, `--fast` then auto-confirms within those sections, `--re-setup` further filters to only broken/unconfigured ones.++### Profile → sections mapping++| Profile | Sections enabled |+|---------|------------------|+| developer | 2 (CLIs), 2c (Daemon), 3g (Doppler), 3h (Vault), plus GitHub + AWS + Sentry + Linear integration paths |+| founder | 2, 2c, 3a (Telegram), 3b (WhatsApp), 3c (Email), 3d (Slack), 3f (Calendar), 3g (Doppler), 3n (Notifications) |+| marketer | 2, 2c, 3j (Marketing — Klaviyo/Meta Ads/GA4/GSC), 3i (Shopify), 3c (Email), 3g (Doppler) |++### Incremental re-setup++When Step 0b detects an existing `$PREFS_PATH/preferences.json` with ≥1 configured section AND no explicit arguments were passed, default Step 1's prompt to "Re-setup broken only" (instead of "Set up everything"). Skip every section where `/ops:status` reports green for that section's key integrations.++### Progress panel++After every section completes (or is skipped), print a single line progress panel:++ Progress: {configured}/{total} configured · {working} working · {pending} pending++Where:+- `configured` = sections where credentials are present in `preferences.json`.+- `working` = configured sections whose most recent `/ops:status` smoke test returned green.+- `pending` = sections the user selected but hasn't configured yet.+- `total` = total sections considered for this run (filtered by `--profile` if used).++---+## Agent Teams supportIf `CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS=1` is set, use **Agent Teams** when multiple "Deep hunt" credential agents are needed simultaneously. This enables:@@ -151,10 +190,28 @@ Print a compact status header to the user, one line per category:Use `✓` for present/set, `○` for missing/unset, `✗` for broken.+### Incremental re-setup routing++If Step 0b finds `$PREFS_PATH/preferences.json` with ≥1 configured section and no `--fast`/`--profile` argument was passed:++1. Read `/ops:status` snapshot to build a per-section health map (`green`/`red`/`missing`).+2. Filter the Step 1 selector options to only sections where status is `red` or `missing`.+3. Change the default option label to "Re-setup broken only (Recommended)".+4. Add "Add new section" as a secondary option for users who want to configure a previously-skipped section.++Fresh installs (no `preferences.json` at all) continue to see the full selector with "Set up everything" as the default.+---## Step 1 — Ask which sections to configure+**When `--profile <name>` was passed:** Skip this step entirely. Use the profile → sections mapping from the Arguments section to activate the curated subset and proceed to Step 2.++**When `--re-setup` was passed (or incremental mode auto-detected from Step 0b):** Skip this step. Activate only sections reporting `red`/`missing` and proceed to Step 2.++**Otherwise:** proceed with the standard selector below.++First, offer a quick "set up everything" option:```