setuplisted

# Setup - First-time Onboarding & Environment Check A skill that verifies all LeadAce connections (cloud MCP, Gmail SaaS, local tools), surfaces what is and is not available, picks or creates a project, and stores the environment status so that subsequent skills (`/strategy`, `/build-list`, `/outbound`, `/daily-cycle`, etc.) can rely on it without re-asking. Run this skill the first time you use LeadAce, and re-run it whenever your local tools or Gmail connection status change. **Before starting:** `Read` `${CLAUDE_PLUGIN_ROOT}/references/workspace-conventions.md` and follow the cross-cutting conventions there (data storage, MCP error handling, document writes, output discipline). ## Procedure ### 1. Run the shared environment-check procedure `Read` `${CLAUDE_PLUGIN_ROOT}/references/onboarding/env_check.md` and execute its full procedure (Steps 1-5). Pass: - `$0` (the project name argument from the user; may be empty) - No `$URL` (this skill does not use URL-driven naming) The shared procedure: - Verifies MCP version + auth - Detects Gmail SaaS, asks about Gmail MCP and Claude in Chrome - Picks or creates the project - Saves the `env_status` document When the procedure finishes, you have `PROJECT_NAME` and a 4-line capability summary. ### 2. Completion Report Print a short, scannable summary: - Project in use (`PROJECT_NAME`) - The capability table from the saved `env_status` doc - An explicit list of any missing capabilities and what each blocks - A one-line note t