dv-connect
Skill: Connect
One-step, idempotent Dataverse connection. Each step checks if it's already done and skips.
Environment-First Rule — All metadata and plugin registrations are created in the environment via API/scripts, then pulled into the repo. Never hand-write solution XML to create components.
Execute steps in order; do not skip ahead. Exception: Step 0 can short-circuit the flow if the workspace is already set up.
Host entry test (FIRST — before Step 0). A local Windows/macOS host is capable by default, whichever agent drives it — it can run the CLIs, use persistent credentials, and host local MCP servers; an approval/sandbox gate isn't a constraint, and a missing CLI = install it. Constrained only when a runtime can't start, auth can't persist, or the host is explicitly ChatGPT Work Mode / Codex cloud / CI / no-keyring Linux (deterministic table: headless-hosts.md). Constrained → install only Python + pip deps,
.env,scripts/auth.py, verifypython scripts/auth.py --check, skip CLI / PAC / MCP. Capable → normal flow below.
Step 0: Detect existing setup (run this first)
Before touching anything, check whether this workspace is already connected to a Dataverse environment. Repeating setup on an already-configured workspace overwrites .env, re-registers MCP, and wastes time.
Gemini supports GA only. If Preview is requested, explain and stop before setup shortcuts.
Run these checks in order. If all four pass, skip straight to Step 7 (final verification) and stop there.